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: <Pine.NEB.4.55.0307161958100.14118@panix2.panix.com>
From: jays at panix.com (Jay Sulzberger)
Subject: Odd Behavior - Windows Messenger Service


On Wed, 16 Jul 2003, Blue Boar wrote:

> morning_wood wrote:
>
> > imho it is iresponsible default behaivor for a workstation OS to allow
> > remote resources / services / enumeration
> > before any interactive user or administrative login.
>
> That's what services do.  If you don't want it to do that, run it as a
> regular app.  What do you suggest they do with the login service?
>
> 					BB

Step 1: Protect it from possible spoofs by not running uncontrolled
channels at startup.

oo--JS.