Re: putty's telnet.c fix
From: dwalin (dwalin_at_dwalin.ru)
Date: 08/23/05
- Next message: elwinter: "SCP via SSH tunnel works, then not, then works again"
- Previous message: Richard E. Silverman: "Re: Forcing new password at login (w/o requiring an old password) (sudo related)"
- In reply to: Ben Harris: "Re: putty's telnet.c fix"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 23 Aug 2005 04:47:19 -0700
Ben Harris wrote:
> That's mad. Sending WON'T for an option that's already disabled (as
> LINEMODE must be, since PuTTY doesn't support it) is pointless. PuTTY is
> correct in not replying to it, since doing so is banned by RFC 854, and has
> caused negotiation loops in the past. Even if PuTTY were to reply, the only
> reasonable reply would be DON'T, not WON'T.
tried to send DON'T, it works. i don't insist on being big expert in
telnet protocol, just made a quick patch to get it working again.
stumbled over this issue just yesterday trying to apply my own code
changes to the 0.58 release. whew.
> option that was already disabled. We fixed that bug, and we're not likely
> to take the fix out again to please your server.
*shrug* maybe make this another configurable option? i always thought
you're trying to be compatible to everyone, and in this case there's no
point in trying to fix server side, it's practically impossible. if you
won't :) fix this, fine. i'll just include it in my own patch set,
along with other fixes for at&t 513 terminal. one line more or less...
always at your service,
dwalin.
- Next message: elwinter: "SCP via SSH tunnel works, then not, then works again"
- Previous message: Richard E. Silverman: "Re: Forcing new password at login (w/o requiring an old password) (sudo related)"
- In reply to: Ben Harris: "Re: putty's telnet.c fix"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|