Update pfSense packages to protect against NGINX, libzmq4, and curl vulnerabilities

Networking & Firewalls
1

Recent news from Netgate blog…

2 Likes
2
2 Likes
3

Tom, regarding the block rule on the IOT interface. You used port 443…you must also be using/assuming HTTPS to access PfSense. However, for users that are using the default PfSense setting of HTTP, shouldn’t your block rule be on port 80 instead??

1 Like
4

pfsense defaults to 443, but as I said in the video, block whatever port you have it on.

5

You said in the video you shouldn’t have the pfsense interface public facing but I presume it’s ok to use a VPN to access pfsense remotely.

6

Yes, you could access it via OpenVPN or SSH tunneling.