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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <001e01c34dcb$5f6d3c00$0100a8c0@p3600>
From: chows at ozemail.com.au (gregh)
Subject: Odd Behavior - Windows Messenger Service

>----- Original Message ----- 
>From: Bojan Zdrnja 
>To: full-disclosure@...ts.netsys.com 
>Sent: Saturday, July 19, 2003 4:10 PM
>Subject: RE: [Full-Disclosure] Odd Behavior - Windows Messenger Service

> I'm sorry, but what does that have to do with different OSes starting
> services automatically (before an user logs in), what was the original
> message?

Sigh.... if they are started, the lan is open. Say a sensitive machine that has data on it that only those with passwords can see when touching it's keyboard. The machine is turned off for the day and someone wanting that sensitive data who doesnt know the password to logon locally, an employee, wants in. Supposing he can get into the office to turn the machine on, that is all he has to do in order to access the data.

Dont tell me you dont see anything wrong with that?

Greg.