Sorry for the barrage of posts but ipsec filtering on windows XP pro
sp1 exhibits the same "feature" of allowing all traffic from a remote
port 88.
On a computer pc1 (windows 2000/xp) Create a new ipsec filter rule
blocking ALL traffic from a specific ip address belonging to say pc2.
From pc2 bind a port scanner to local port 88 and scan pc1. My tests
show that the scan is successful, bind it to any other local port and it
fails.
I have not had the opportunity to look at a .Net sever but I would
guess that it has the same problem. If anyone knows for sure, would they
share?
Sorry for the barrage of posts but ipsec filtering on windows XP pro
sp1 exhibits the same "feature" of allowing all traffic from a remote
port 88.
On a computer pc1 (windows 2000/xp) Create a new ipsec filter rule
blocking ALL traffic from a specific ip address belonging to say pc2.
From pc2 bind a port scanner to local port 88 and scan pc1. My tests
show that the scan is successful, bind it to any other local port and it
fails.
I have not had the opportunity to look at a .Net sever but I would
guess that it has the same problem. If anyone knows for sure, would they
share?
Thanks
Fred
[ reply ]