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: <Law11-OE67U9BekWo7600008055@hotmail.com>
From: se_cur_ity at hotmail.com (morning_wood)
Subject: Odd Behavior - Windows Messenger Service

> regular app.  What do you suggest they do with the login service?
>
i dont think i would have a issue with a login service running as
accessable via localhost, as that is only what is genuinly needed...
HUH??????  I bet 99% of the general computing public find that my scenario
is quite ODD ( but not experts as yourselves )
why does everone insist on pointing out the smallest techinicalities out of
the greater message in my posts??????
try as i may, it is aparent that MOST of you think I am realy dense in my
understading of services and the operation of personal computers in general
. I was simply pointing out something in a default behavior that IMHO
should not be able to occur... is this too hard to grasp? or do MOST of you
only want to eek out your tidbitish egotistical tech comments to someone
who has been in the computer field over 13 years to point out your
wonderfully and I am wrong?

this gets old, real fast.

Donnie Werner
http://nothackers.org/about.php