Package: lxc Version: 1:1.0.6-3 Severity: minor Recently I started a container via « sudo lxc-start … » without configuring sudo to reset the umask first. I subsequently found SSHing into the container was slightly broken and user sessions were hanging in weird ways. This turned out to be because /dev had been created with mode 0750 instead of the proper 0755; the problem went away when I explicitly reset the umask from 0027 to 0022. It would be nice if LXC programs that deal with files in the container either reset the umask themselves or explicitly chmodded created files to avoid causing problems when so invoked.
---> Drake Wilson -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lxc depends on: ii init-system-helpers 1.21 ii libapparmor1 2.9.0-2 ii libc6 2.19-13 ii libcap2 1:2.24-6 ii libseccomp2 2.1.1-1 ii libselinux1 2.3-2 ii multiarch-support 2.19-13 ii python3 3.4.2-1 Versions of packages lxc recommends: ii debootstrap 1.0.64 ii openssl 1.0.1j-1 ii rsync 3.1.1-2+b1 Versions of packages lxc suggests: pn lua5.2 <none> -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
