| 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
| ||
|
Date: Tue, 05 Dec 2006 12:20:30 -0500 From: "Marty Leisner" <linux@...hester.rr.com> To: linux-kernel@...r.kernel.org, bug-cpio@....org cc: martin.leisner@...ox.com Subject: ownership/permissions of cpio initrd I'm working on an embedded system with the 2.6 kernel -- cpio initrd was a new feature I'm looking at (and very welcome). The major advantage I see is you don't have MAKE a filesystem on the build host (doing cross development). So you don't have to be root. But its "useful" to change permissions/ownership of the initrd files at times... Since a cpio is just a userspace created string of bits, I suppose you can apply a set of ownership/permissions to files IN the archive by playing with the bits... Does such a tool exist? Comments? Seems very useful in order to avoid being root... marty - 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