Hi everyone, I am trying to add a Fortigate VM eval, generated via the
FortiCloud account to the FortiManager VM eval, also generated via the
FortiCloud account. So, both units are "self-generated" evals. I am not
talking about evals obtained through...
I have not worked with Fortigate for quite some time, but I had to come
back to it because of a project I am currently working on. In the past
it was more like better not to have a demo version of FG at all, because
it was full of bugs to that level ...
Hi Nur, Hm... I can confirm the CN for the "Fortinet_Factory" and the SN
do not match. The CN for the "Fortinet_Factory" is "FortiGate". I wonder
if this is a bug. It would be great if anyone else could confirm that on
version 7.6.2 (but have also tr...
Unfortunately, it does not. Basically, "Fortinet_Factory" certificate
comes signed by "fortinet-subca2001", which actually means in order to
be able to re-generate it we would need to have "fortinet-subca2001"
private-key installed in each and every ...
Another interesting thing to note is the default certificates that comes
with the Fortigate VM eval and the licensed ones. Within the System >
Certificates the non-eval FG contains a local certificate named
"Fortinet_Factory" issued by the fortinet-s...
@AEK - I tried this, no luck :) It is actually saying "hey, don't use
any TLS version below this configured", but if both units support and
can negotiate higher version of TLS, they will do it. In this case, both
devices will just negotiate TLS v1.3,...