full-disclosure - Odd Behavior - Windows Messenger Service

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 for Android: free password hash cracker in your pocket

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

From: jays at panix.com (Jay Sulzberger)
Subject: Odd Behavior - Windows Messenger Service


On Thu, 17 Jul 2003, morning_wood wrote:

> once again Jay, Bravo Bravo Bravo

Thanks, and I blush ;)

oo--JS.


> damn, you just may be the only one who gets the point of my post
> or do we need to wade through 20 more ppl telling me how to secure a system
> or how services act or initialize.
> ( and at that they have no concept of my particular topology..  and
> furthermore can only see fit to blast away completly missing the target and
> shooting themselves in the foot thats squarley stuck in thier mouths..
> hint: take off the white hat so you can see 2 feet beyond your certs and
> books)
>
> > Out of the box, the default should be that no network services are
> started
> > at boot without human command transmitted via local hardware.  This may
> be
> > seen from even the first, even the most crude and blunt, cost benefit
> > analysis.
> >
> > oo--JS.
>
> Donnie Werner
> http://exploitlabs.com
>