As I'm sure you hear all too often: I doubt I'll have the time to work on this.
However I did some research. I noticed that PUTTY only sends the
following Pty codes:
{TTY_OP_OSPEED=38400, VERASE=127, TTY_OP_ISPEED=38400}
RFC 4254 page 19 says:
the server leaves all unspecified mode bits in their default values,
and only some combinations make sense.
If SSHD already has support for ECHO, ECHOE, ECHOK, ECHONL the patch
can be as easy as assigning reasonable defaults. I could not find a
standard for the defaults.
-Todor
On Thu, Aug 26, 2010 at 3:58 PM, Guillaume Nodet <[email protected]> wrote:
> I don't think any progress has been done in this area, but if you have
> any thoughts, you're welcome to try something.
> This is an area where I still don't understand how things are supposed
> to work (i.e. which part is responsible for what) ...
>
> On Thu, Aug 26, 2010 at 14:39, Todor Boev <[email protected]> wrote:
>> Hi,
>>
>> I need a way to make the SSHD server negotiate the echo support with
>> the client. Some clients require every char to be echoed while others
>> have local echo. I found this discussion on this mailing list but it
>> is open ended:
>>
>> http://www.mail-archive.com/[email protected]/msg13827.html
>>
>> Has this issue been resolved?
>>
>> Cheers,
>> Todor
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
