Author Topic: Worrying Avast Firewall bug  (Read 3183 times)

0 Members and 1 Guest are viewing this topic.

Offline bob3160

  • Avast √úberevangelist
  • Probably Bot
  • *****
  • Posts: 45152
  • 61 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: Worrying Avast Firewall bug
« Reply #15 on: February 04, 2019, 04:35:09 PM »
By "NLA", do you mean Network Level Authentication? I thought that was just for use with RDP?

Alternatively, are you referring to the list of previously connected networks that Win10 stores in HKLM\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\NetworkList\Profiles\[...]? Embarrassed to admit I hadn't thought to check that, but I will. I suppose it's possible that the "BN16.com" connection could be a hangover from the configuration process that my laptop's manufacturer might have run on it. I will take a look a post my findings here.

In terms of tweaking the behaviour or presentation of these Avast Firewall settings in future: it was quite alarming to see a set of new networks appear in the firewall settings menu. It may help reassure Avast users who are a little too security-conscious (such as myself) if the firewall only displayed networks that it was involved in managing. For most users this would mean that Avast only listed the network they were using at the time Avast was installed, and any network that the "toaster"/pop-up prompted them to set to private or public afterward.
That sounds like ignorance is bliss. I've always opted for more information not less just because less would make me feel better.

Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 10 Pro v20H2 64bit, 24 Gig Ram, 1TB SSD, AvastOmni 20.7.xxx, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq