Menu

Join the Conversation

To sign in, use your existing MySonicWall account. To create a free MySonicWall account click "Register".

Sign In Register

Bug found in 7.1.3-7015: Certificate chosen for mangement

jst3751jst3751 Newbie ✭
in Mid Range Firewalls

I have been trying to resolve a problem with applying a non-self-signed certificate for the management interface since installing 7.1.3-7015 on a HA pair of NSA2700 firewalls.

I even obtained a new SSL Certificate specifically for the firewall's FQDN.

What happens is that if any certificate is chosen OTHER THAN the self-signed certificate and left at the default name of 192.168.168.168, upon reboot, a different self-signed certificate is being used. In my case, it is the IP of interface XO.

I have been communicating with Sonicwall support, and they are now escalating to engineering as a bug that needs a hotfix.

Again, this is on a HA pair of NSA2700.

I will be testing this on TZ270 not part of any HA tonight as well.

NOTE: This does not affect the certificate chosen for SSLVPN.

Category: Mid Range Firewalls
Reply
Tagged:
Sign In or Register to comment.