Hi! On Tue, 2013-03-05 at 12:23:25 +0100, Javier Barroso wrote: > package: dpkg > version: 1.16.9 > severity: wishlist
> This morning after booting my computer, I couldn't login into my desktop. > > In .xsession-errors file appeared: > openConnection: connect: No existe el fichero o el directorio > cannot connect to brltty at :0 > mkdtemp: private socket dir: Permission denied > After review the problem, I found the problem, that is that I executed : > > dpkg-deb -x package.deb /tmp/ > > So /tmp/ was changed from 1777 to 755. I read in manpage about this > change is wanted. This is the same that will happen if either root unpacks a tarball (containing directories) on an existing directory using tar, or if a user uses «tar -p» on a directory the user can change. > But I'm asking you if it is possible to add a warning / error to > dpkg-deb output, so you don't broke your system without any clue (If > you use dpkg-deb wrongly) Well, this is only an issue if «dpkg-deb -x» is used on such directories if run as root, otherwise the perms will not be changed, and then there's the usual advice of not playing as root for unneeded actions. This would also affect other directories such as /var/tmp, etc. And as such I'm reluctant to add a warning for something that the user might do on purpose, knowing the possible consequences, or start hardcoding a list of possible problematic extraction directories. Warning only when the directory already exists, or when run as root, might also trigger on valid scenarios, where the user has created the directory beforehand, for example. I can sympathize with trying to avoid this kind of problem, but I'm not sure there's a solution that will not annoy current users, or make things more difficult for people that expect the current behaviour. Thanks, Guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
