New answers tagged

0

Opening it to static public IP in firewall or MySQL settings does not mean that only packets from that IP can access it. It means that only packets claiming to be from that IP can access it. See: IP Address Spoofing I understand UDP packets have another angle on this. I would also only use SSL, for obvious reasons if going this route. Disclaimer: I am not ...


0

If the host that is trying to connect to your port 4444 on your Kali is on the Internet, you'll need to configure port forwarding on the router you use to access the Internet - that is, your router needs to redirect connections from 4444 coming from the Internet to your internal VM (this process varies according to the router, so just Google a guide for more ...


0

In your case,You use bridge connection in VMware which means that your windows machine ip like 192.168.1.11 then your kali Linux ip would be 192.168.1.x you could see your ip address just type in terminal ifconfig and use namp to know how many port on your system is open. for that Here is command: sudo nmap yourip now you could see that what process ...


0

I agree with Steffan that QUIC is no more dangerous than TCP or UDP or HTTP or any other communication protocol. I think for your use case what really matter is the data being transferred through the protocol. Like Steffan said, it really depends on the firewall and the concerns you are trying to address using that firewall. Doing an informal threat ...


1

QUIC by itself is no more dangerous than TCP, UDP, HTTP ... . What matters is the content transferred with the protocol. If you use your firewall only as a simple packet filter and don't do any content inspection (i.e. malware, URL filter etc) then it does not matter much if you allow QUIC or not. If instead your firewall is used to analyse HTTP(s) traffic ...



Top 50 recent answers are included