Hi,

is this correct to reflect syslog_r(3) change?

I tested chrooted internal-sftp without /dev/log in the chroot
and it was logging fine.

j.

Index: sftp-server.8
===================================================================
RCS file: /cvs/src/usr.bin/ssh/sftp-server.8,v
retrieving revision 1.25
diff -u -p -r1.25 sftp-server.8
--- sftp-server.8       14 Oct 2013 14:18:56 -0000      1.25
+++ sftp-server.8       18 Jul 2014 20:58:23 -0000
@@ -139,16 +139,6 @@ Sets an explicit
 to be applied to newly-created files and directories, instead of the
 user's default mask.
 .El
-.Pp
-For logging to work,
-.Nm
-must be able to access
-.Pa /dev/log .
-Use of
-.Nm
-in a chroot configuration therefore requires that
-.Xr syslogd 8
-establish a logging socket inside the chroot directory.
 .Sh SEE ALSO
 .Xr sftp 1 ,
 .Xr ssh 1 ,
Index: sshd_config.5
===================================================================
RCS file: /cvs/src/usr.bin/ssh/sshd_config.5,v
retrieving revision 1.175
diff -u -p -r1.175 sshd_config.5
--- sshd_config.5       15 Jul 2014 15:54:14 -0000      1.175
+++ sshd_config.5       18 Jul 2014 20:58:24 -0000
@@ -344,12 +344,7 @@ devices.
 For file transfer sessions using
 .Dq sftp ,
 no additional configuration of the environment is necessary if the
-in-process sftp server is used,
-though sessions which use logging do require
-.Pa /dev/log
-inside the chroot directory (see
-.Xr sftp-server 8
-for details).
+in-process sftp server is used.
 .Pp
 The default is not to
 .Xr chroot 2 .

Reply via email to