full-disclosure - M$ - so what should they do?

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 for Android: free password hash cracker in your pocket

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

Message-ID: <011901c45822$8e246a20$0100007f@c5>
From: aditya.deshmukh at online.gateway.technolabs.net (Aditya, ALD [ Aditya Lalit Deshmukh ])
Subject: M$ - so what should they do?

> > Also, the magic file names, like "CON" and "AUX" should go away.
> 
> No way!  Am I the only person who still uses "copy con filename.txt" to
> create scripts and such at the command line?  Please tell me I'm not?

CON and NULL should stay but COM, AUX and LPT should go away. i had a server in which the script kiddes got into the ftp server and made a COM1 folder on ntfs. had been a pain in neck to rename that folder - had to use linux with ntfs support!

-aditya
??????????????????????????????????????????????????????
?b???v?"?.axZ?x??????Gb?*'??.?[kj???.?j)m???r??