View Single Post
Old 07-02-2015, 09:22 AM   #36
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by frostschutz View Post
It does change permissions and ownerships of the files according to what's in the tar. Technically all tar should have root as owner and group but so far I've been too lazy to add the necessary --owner --group options to tar.
Your right, tar should be handling it. But, I had something like this a while ago. Maybe it was zip, or the permissions of the user I was logged in as.
Quote:
In practice it makes no difference. Everything on the Kobo runs as root anyway, and root does not care about wrong owners. So the only thing that really matters is the executable flag needed for binaries/scripts.

Of course, if you DO set the suid flag and the owner is wrong, then it really bites you as suddenly you execute stuff as nobody instead of root. Here suid causes problems instead of solving them.

suid on busybox is a bad idea. It would suid _everything_, not just passwd. So nobodies can overwrite files etc. etc. etc.
And yes, that sounds right.
davidfor is offline   Reply With Quote