Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- Logingrace time and debug mode
May 31, 2005, 12:14 pm
rate this thread
I am using OpenSSH on hp-ux 11.23 box. For testing I started sshd with
following options in debug mode
sshd -o'logingracetime 1m' -ddd
I conneted my client and waited over the gracetime, but the client
still could successfully connect to the server
time ssh -l mit localhost -vvv date
Tue May 31 18:56:58 IST 2005
debug3: channel 0: will not send data after close
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> closed
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
#0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cfd -1)
debug3: channel 0: close_fds r -1 w -1 e 9 c -1
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.2 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 0
But the SSHD works perfectly when it is started in normal mode.
Is this a correct behaviour?
Re: Logingrace time and debug mode
Well, it's intended behavior anyway. One of the benefits of free
software, is that you can obtain and read the source code:
* We don't want to listen forever unless the other side
* successfully authenticates itself. So we set up an alarm which is
* cleared after successful authentication. A limit of zero
* indicates no limit. Note that we don't set the alarm in debugging
* mode; it is just annoying to have the server exit just when you
* are about to discover the bug.
- » Brute force attack, exponential delay for reconnect?
- — Previous thread in » Secure Shell Forum
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — Newest thread in » Secure Shell Forum