| 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
| ||
|
Message-Id: <200706212114.25705.hpj@urpla.net> Date: Thu, 21 Jun 2007 21:14:24 +0200 From: Hans-Peter Jansen <hpj@...la.net> To: linux-kernel@...r.kernel.org Cc: "H. Peter Anvin" <hpa@...or.com>, "Dr. David Alan Gilbert" <linux@...blig.org>, Karel Zak <kzak@...hat.com>, linux-fsdevel@...r.kernel.org, util-linux-ng@...r.kernel.org Subject: Re: Adding subroot information to /proc/mounts, or obtaining that through other means Am Donnerstag, 21. Juni 2007 00:46 schrieb H. Peter Anvin: > Dr. David Alan Gilbert wrote: > > What happens with the (sick) case of spaces in directory names? > > Also is it really nicely defined that there is no way to put a space > > in an option in any of the filesystems? I suppose someone > > particularly sick could have a device node in a directory with a space > > in it. It would be nice if new formats for this are being defined > > to make it cover everything. > > That's already handled just fine: > > bash-3.1$ mkdir /tmp/'Jag är: \ > en liten mask' > bash-3.1$ sudo mount -t tmpfs none '/tmp/Jag är: \ > en liten mask'/ > bash-3.1$ tail -1 /proc/mounts > none /tmp/Jag\040är:\040\134\012en\040liten\040mask tmpfs rw 0 0 > bash-3.1$ Hmm, and what about the even sicker case: /tmp/\040, parse as /tmp/\\040? Do userspace cope with this? Happy parsingly y'rs, Pete - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists