Re: Terminal parameters patch

Peter Gutmann wrote:
> Stephen Hurd <[email protected]> writes:
>
>> Hrm... how about the env variables TERM, COLUMNS and LINE as specified by
>> SUSv2 here:
>>
>> http://pubs.opengroup.org/onlinepubs/7908799/xbd/envvar.html
> This still has the issue that it solves one particular problem for one user,
> leading to the same variable-explosion problem I mentioned before when
> everyone wants their own set of SSH parameters.  

Looking at the pty-req specification in RFC-4254, there are only six
parameters in it, and currently they are all hardcoded in cryptlib.  At
least two of them are hardcoded to values that are always wrong in my
usage along with one that is occasionally wrong.  Since this request
appears to always be sent by the client when a session is activated, I'm
not sure this is really a case of parameter explosion.

Regardless, my patch seems to be working fine enough for my needs, so I
won't bother pushing for this any harder.  Thanks for looking into it,
and thanks for the excellent product.

_______________________________________________
Cryptlib mailing list
[email protected] via Mail: [email protected]
Archive: ftp://ftp.franken.de/pub/crypt/cryptlib/archives/
http://news.gmane.org/gmane.comp.encryption.cryptlib
Posts from non-subscribed addresses are blocked to prevent spam, please
subscribe in order to post messages.