Jump to content

pipes

Members
  • Posts

    37
  • Joined

  • Last visited

Everything posted by pipes

  1. What a disappointment when I find that Waterfox cant work with online banking!
  2. All that matters is whats under the hood. When it gets pretty on the outside that's when to worry. Just fine for me.
  3. when i make an inbound block rule it will not connect to VPN (protocol any) what would you suggest short of not using a VPN? thanks Sorry about the mess above.
  4. When i make an inbound block rule it will not connect to VPN (protocol any) what would you suggest short of not using a VPN? thanks
  5. I know this is about ESET , but i wanted to show what i was talking about
  6. Really i don't use chrome for the reason. Just to show how WFC10 works,
  7. It needs UDP port 443. It will fall back to UDP port 443 when QUIC is blocked. It will use QUIC when a firewall does not recognize it, to me that's not good. That is the million dollar question! Thanks.😉
  8. When I was using Windows Firewall Control 10 (Sphinx) and Windscribe VPN, I would see Windscribe was trying to use QUIC UDP-443, Sphinx has the option of blocking QUIC in-out. Also of course, has the option regular TCP-UPD. Windscribe VPN did not like it at first but after a couple re-starts it was normal. Gave me a more secure feeling. QUIC can do pretty much what it wants to do behind the firewalls back since it is not recognized. I do like the option, wish ESET had it.
  9. Does ESET recognize this protocol can I block it I do not use Google chrome so no need for it? Here is a link about QUIC Protocol: https://nordvpn.com/blog/what-is-quic-protocol/ "There are few downsides to the QUIC protocol. It improves web communications and reduces latency, but it’s still in its experimental stages. It’s not widely adopted by other websites or web servers, nor is it supported by cybersecurity tools such as firewalls. Because of this, experimental QUIC protocol can currently open a security loophole."
×
×
  • Create New...