On Thu, 30 Jan 2014, Damien Miller wrote: > Fortunately, working around this in the test is easy: here's a better patch that doesn't break login-timeout Index: regress/login-timeout.sh =================================================================== RCS file: /var/cvs/openssh/regress/login-timeout.sh,v retrieving revision 1.7 diff -u -p -r1.7 login-timeout.sh --- regress/login-timeout.sh 17 May 2013 10:41:07 -0000 1.7 +++ regress/login-timeout.sh 29 Jan 2014 23:55:26 -0000 @@ -4,6 +4,8 @@ tid="connect after login grace timeout" trace "test login grace with privsep" +cp $OBJ/sshd_config $OBJ/sshd_config.orig +grep -vi LoginGraceTime $OBJ/sshd_config.orig > $OBJ/sshd_config echo "LoginGraceTime 10s" >> $OBJ/sshd_config echo "MaxStartups 1" >> $OBJ/sshd_config start_sshd Index: regress/test-exec.sh =================================================================== RCS file: /var/cvs/openssh/regress/test-exec.sh,v retrieving revision 1.61 diff -u -p -r1.61 test-exec.sh --- regress/test-exec.sh 9 Nov 2013 05:55:03 -0000 1.61 +++ regress/test-exec.sh 29 Jan 2014 23:55:26 -0000 @@ -328,6 +328,7 @@ cat << EOF > $OBJ/sshd_config StrictModes no Port $PORT Protocol 2,1 + LoginGraceTime 15m AddressFamily inet ListenAddress 127.0.0.1 #ListenAddress ::1 _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
