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-next>] [day] [month] [year] [list]

Message-ID: <871080DEC5874D41B4E3AFC5C400611E03F60580@UTDEVS02.campus.ad.utdallas.edu>
From: pauls at utdallas.edu (Schmehl, Paul L)
Subject: Odd Behavior - Windows Messenger Service

> -----Original Message-----
> From: morning_wood [mailto:se_cur_ity@...mail.com] 
> Sent: Wednesday, July 16, 2003 5:17 PM
> To: dos cerveza; full-disclosure@...ts.netsys.com
> Subject: Re: [Full-Disclosure] Odd Behavior - Windows 
> Messenger Service
> 
> imho it is iresponsible default behaivor for a workstation OS 
> to allow remote resources / services / enumeration before any 
> interactive user or administrative login.
> 
I guess you'd better dump Unix then.  Have you ever watched the screen
on a Unix box while it's booting?  Have you not noticed things like
sendmail, sshd, crond, etc. starting up?

It'll be a sad day when someone has to login to the console before a
server can start doing its work. :-)

Paul Schmehl (pauls@...allas.edu)
Adjunct Information Security Officer
The University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/~pauls/