Bug#661627: init script x11-common creates directories in insecure manners

2012-02-29 Thread vladz
CVE-2012-1093 has been assigned for this issue. On Tue, Feb 28, 2012 at 08:21:39PM +0100, Julien Cristau wrote: > Right, makes sense. I can drop the -p, I guess. Not sure what impact > that would have on things assuming they can use /tmp/.X11-unix (I > wouldn't really like to fix this just to ha

mesa: Changes to 'ubuntu'

2012-02-29 Thread Timo Aaltonen
debian/changelog |6 ++ debian/libegl1-mesa-dev.install.in |2 +- debian/libegl1-mesa-dev.install.linux.in |4 ++-- 3 files changed, 9 insertions(+), 3 deletions(-) New commits: commit d8ef6d2069eb300401a6b9c5a38c715a5e90d70d Author: Timo Aaltonen Da

mesa: Changes to 'debian-experimental'

2012-02-29 Thread Timo Aaltonen
debian/libegl1-mesa-dev.install.linux.in |1 - 1 file changed, 1 deletion(-) New commits: commit a017c9334cb9203de20faccb2c9aa18f40e22545 Author: Timo Aaltonen Date: Wed Feb 29 14:50:40 2012 +0200 libegl1-mesa-dev.install.linux.in: drop duplicate pkgconfig line diff --git a/debian/li

Bug#661627: init script x11-common creates directories in insecure manners

2012-02-29 Thread Julien Cristau
On Tue, Feb 28, 2012 at 20:21:39 +0100, Julien Cristau wrote: > On Tue, Feb 28, 2012 at 19:05:23 +0100, vladz wrote: > > > On Tue, Feb 28, 2012 at 06:42:59PM +0100, Julien Cristau wrote: > > > > As a solution, I would suggest to take care of the "mkdir" return codes > > > > (line 36 and 50). To

Bug#661627: Avoid /tmp ?

2012-02-29 Thread Tim
This appears to be a pretty serious problem. I agree, just dropping '-p' won't work for functional reasons. As a better long-term solution, have you considered just moving those directories out of /tmp? There's almost always a safer place to put temporary files/directories. For instance, under

Bug#661627: init script x11-common creates directories in insecure manners

2012-02-29 Thread Julien Cristau
On Wed, Feb 29, 2012 at 21:29:37 +0100, Julien Cristau wrote: > On Tue, Feb 28, 2012 at 20:21:39 +0100, Julien Cristau wrote: > > > On Tue, Feb 28, 2012 at 19:05:23 +0100, vladz wrote: > > > > > On Tue, Feb 28, 2012 at 06:42:59PM +0100, Julien Cristau wrote: > > > > > As a solution, I would sugg

Bug#661627: Avoid /tmp ?

2012-02-29 Thread Bernhard R. Link
* Tim [120229 23:00]: > As a better long-term solution, have you considered just moving those > directories out of /tmp? Those are for sockets whose name is part of the interface to access them. So you cannot move them. And the directory itself needs to be world-writeable, so it is best placed wi

Bug#661627: Avoid /tmp ?

2012-02-29 Thread Tim
Hi Bernhard, > > As a better long-term solution, have you considered just moving those > > directories out of /tmp? > > Those are for sockets whose name is part of the interface to access > them. So you cannot move them. And the directory itself needs to be > world-writeable, so it is best place

Bug#661754: x11-xkb-utils: setxkbmap and xkbcomp settings do not apply to new keyboards

2012-02-29 Thread Stefan Monnier
Package: x11-xkb-utils Version: 7.6+4 Severity: important Dear Maintainer, My desktop can finally suspend and resume properly, which makes me very happy, but let me discover a new obstacle: upon resume my keybard settings are lost and I have to re-apply my xkbcomp setting every time. The same ca

Bug#661754: x11-xkb-utils: setxkbmap and xkbcomp settings do not apply to new keyboards

2012-02-29 Thread Cyril Brulebois
Stefan Monnier (29/02/2012): > It seems that setxkbmap only affects the current InputDevice, whereas > I'd like to affect a whole InputClass, but I don't know how/where > to specify which inputs devices should be affected. > Where are the equivalent of xorg.conf's MatchIsKeyboard/MatchProduct/...?