This is trivially reproducible without the need for configuration files.
We should not be wasting bug reporters' time asking them for unnecessary
information ...
This is a long-standing problem, but I would rather not give the
unprivileged network monitor direct access to syslog. Instead, any
logging it does should be directed through the privsep protocol. Not
trivial work.
** Changed in: openssh (Ubuntu)
Importance: Undecided => Medium
** Changed in: openssh (Ubuntu)
Status: Incomplete => Triaged
--
Syslog socket missing from chroot.
https://bugs.launchpad.net/bugs/582443
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
