PAM_AUTH_ERR messages
Darren Tucker
dtucker at zip.com.au
Sun May 1 17:52:42 EST 2005
Sean wrote:
> On Sat, April 30, 2005 10:04 pm, Darren Tucker said:
>>You can hack a fflush and sleep into session.c but I don't think it
>>should be yet another sshd option. If the user has configured the
>>client to close immediately, taking any useful information with it then
>>that's their problem.
>
> There is a setting in Putty that says to auto-close window only on "clean
> exit". Any idea how we would send a "this is not a clean exit" message
> in protocol 2 along with our failure text so that the window isn't closed
> on the user?
The code in session.c that returns the error message also sets an exit
code of 254. If PuTTY checks the exit code then it'll detect this,
however if it's just looking for connection breaks and the like then it
probably won't. I don't know which it does.
--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
More information about the openssh-unix-dev
mailing list