full-disclosure - RE: UPDATE! Jamming communication [COM] ports in windows...

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: <28915501A44DBA4587FE1019D675F983093D4A@grfint.intern.adiscon.com>
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Subject: RE: UPDATE! Jamming communication [COM] ports in windows...

> Well, as mentioned earlier in another email... LOT OF PRANKS 
> COULD BE PLAYED EVEN BY A UNATHORISED PERSON! well, atlest M$ 
> should filter these things... in some ways!

Yes, that's the point. /dev/xxx in *nix is not an issue - there are
permissions. I have done a quick search, but I think there is no easy
way to place ACLs on devices in Windows. I hope I am wrong. Does
somebody know how to do this?

Rainer