Date: Wed, 15 Mar 1995 23:10:48 -0700 From: Nate Williams <nate@trout.sri.MT.net> To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>, phk@ref.tfs.com (Poul-Henning Kamp) Cc: hackers@FreeBSD.org Subject: Re: cpio bug ? Message-ID: <199503160610.XAA29803@trout.sri.MT.net> In-Reply-To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> "Re: cpio bug ?" (Mar 15, 8:46pm)
next in thread | previous in thread | raw e-mail | index | archive | help
> > I think I have found one of the things which have troubled us in the > > install procedure, and would like to hear people opinions: > > > > In a cpio file I have: > > file usr/bin/passwd (root,bin, setuid+0555) > > symlink usr/bin/yppasswd (bin,bin,0755) -> passwd > > > > Now, cpio will do a chown(bin) on usr/bin/yppasswd, and this will > > make usr/bin/passwd owned by bin instead of root. > > > > Obviously wrong. > > > > How to fix this ? > > CPIO should stop doing chown/chmod's on symlinks since symlinks no longer > have there own protection. > > > Who will do it for me ? > > I am digging through the cpio source code now... looks like several > things will need to be tweaked :-(. Have we looked at PAX? It's a 4.4 thing, and it's supposed to do both cpio and tar like functions. (I think it can also do cpio and tar formats, which means that it could replace both of them) Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503160610.XAA29803>