full-disclosure - TCP Port 42 port scans? What the heck over...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: dufresne at winternet.com (Ron DuFresne)
Subject: TCP Port 42 port scans? What the heck over...

	[SNIP]

>
> 3. I can't think of a good reason to open WINS through a firewall.
> Generally one would expect places with multiple sites to use site to
> site connections, IPSec tunnels, and end user VPN tunnels, all of
> which would negate the need to open it through the firewall.
>

I know of at least one state network, and perhaps all it's agencies, most
colleges, the k-12 schools, etc that let it pass, let it pass, let it
pass...

Being there are so many consultants setting up and "fixing" small nets
these days of outsourcing america and the jobless recovery, I'm betting
more and more small and medium shops are getting more bang for their
bucks.

Then consider, how does Redmond tout their protocols?  What are the
mighty words out of the great northwest?  Many M$ based shops
take the word of Redmond and Gartner as words of the gawds and make them
site policies...

Thanks,

Ron DuFresne
-- 
"Sometimes you get the blues because your baby leaves you. Sometimes you get'em
'cause she comes back." --B.B. King
        ***testing, only testing, and damn good at it too!***

OK, so you're a Ph.D.  Just don't touch anything.