![]() |
|
|||||||
|
|
Thread Tools | Search this Thread |
|
#1
|
|||
|
|||
|
-http://blog.beefproject.com/2012/07/opening-closed-ports-on-nat-device-and.html-
Quote:
__________________
http://tools.ietf.org/html/rfc3514 |
|
#2
|
|||
|
|||
|
Eww, nasty. I cannot wait until malicious sites start using remote exploits, instead of tired old drive-by downloads.
Anyway... How would UFW's default configuration for iptables fair against such an attack? And what about Windows software firewalls? Would I be wrong in suspecting an interactive firewall might be safer in this case? |
|
#3
|
||||
|
||||
|
Quote:
An outbound Firewall would prevent this as well by locking the program to specific ports.
__________________
|
|
#4
|
||||
|
||||
|
Merged Threads, Eliminating Redundant Posts.
__________________
JR "You don't have to win every argument. Agree to disagree." Regina Brett |
|
#5
|
|||
|
|||
|
Quote:
http://samy.pl/natpin/ |
|
#6
|
||||
|
||||
|
Quote:
I'd probably want to make sure 135-139 and 445 were closed as well. I've found internet accessible shares that were meant to be private because those ports were open. |
|
#7
|
|||
|
|||
|
Quote:
Doesn't Windows, by default, keep ports open beneath its firewall though? |
|
#8
|
||||
|
||||
|
There are at least 3 open ports on Windows by default for the NetBIOS or something else.
__________________
|
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|