[Bug 582443] Re: Syslog socket missing from chroot.

[Mike Mestnik]

I've discovered that a chroot can be escaped by chrooting to any file.
I'm interested on how this plays on attempting to protect /dev/log?
>From what I can gather is that chroots should not be used as a security
measure(as they are in this case), but only as a device to run multiple
distributions at the same time.

Am I wrong?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/582443

Title:
  Syslog socket missing from chroot.

Status in “openssh” package in Ubuntu:
  Triaged

Bug description:
  Hello,
    sshd attempts to open /var/run/sshd/dev/log in order to log events, but this file did not exist.

  I ran "mkdir /var/run/sshd/dev" and added "$AddUnixListenSocket
  /var/run/sshd/dev/log" to "/etc/rsyslog.d/75-ssh.conf".  That should
  fix things up.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: openssh-server 1:5.3p1-3ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic-pae 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic-pae i686
  Architecture: i386
  Date: Tue May 18 13:44:27 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SSHDConfig:
   Error: command ['gksu', '-D', 'Apport', '--', '/usr/sbin/sshd', '-T'] failed with exit code 1: GNOME_SUDO_PASSSorry, try again.
   sudo: 3 incorrect password attempts
  SourcePackage: openssh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/582443/+subscriptions