| 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: <E1Grvi0-0002f9-9K@mogwai.local> Date: Wed, 06 Dec 2006 13:17:08 +0100 From: rainer@...ibm.com (Rainer Bawidamann) To: linux-kernel@...r.kernel.org Cc: "Marty Leisner" <linux@...hester.rr.com> Subject: Re: ownership/permissions of cpio initrd In article <200612051720.kB5HKU4i001616@...l2.home>, "Marty Leisner" <linux@...hester.rr.com> writes: > 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... The kernel sources provide a program that should do what you want in linux/usr/gen_init_cpio.c Documentation is available in the source or from the command line. Rainer - 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