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] [day] [month] [year] [list]
Message-ID: <200605012029.k41KTFPR005955@turing-police.cc.vt.edu>
Date: Mon May  1 21:29:23 2006
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: Re: DOS device name handling 

On Mon, 01 May 2006 21:58:22 +0200, Klaudiusz Kulik said:
> 
>     Thanks ZARAZA for enlightenment. But... don't You think that it's
> stupid? If name is not allowed, why it is when '/' is appended?
> In fact these names are the same, effects of using these names are the
> same [with or without '/']. And if name is not allowed, why I may create
> that prohibited directory? Really, I don't understand. According to MSDN -
> - it's feature, but I have doubt. Anyway - thanks again for reply.

http://www.catb.org/~esr/jargon/html/B/BAD.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20060501/867a1eb6/attachment.bin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ