Jean-Pierre <[EMAIL PROTECTED]> writes:
> >Do you have their list? I'm curious about what all these the 250
> >algorithms are...
>
> Here you are:
Ah, it's the "language list" that has exploded.
> lsh: DEBUG: Received KEXINIT lsh: (size 5793 = 0x16a1)
> 00000000: 14bae9186587bea2dc0dd2dc433e2638 ....e.......C>&8
...
> 000000d0: 00000ae2432c67656f2c6c6374746162 ....C,geo,lcttab
> 000000e0: 2c69736f5f383835395f31332c69736f ,iso_8859_13,iso
> 000000f0: 5f383835395f31352c69736f5f383835 _8859_15,iso_885
> 00000100: 395f322c69736f5f383835395f352c69 9_2,iso_8859_5,i
> 00000110: 736f5f383835395f372c69736f5f3838 so_8859_7,iso_88
> 00000120: 35395f392c68695f494e2e5554462d38 59_9,hi_IN.UTF-8
...
This is in the language list, as defined by
languages
This is a comma-separated list of language tags in order of
preference [RFC-1766]. Both parties MAY ignore this list. If there
are no language preferences, this list SHOULD be empty.
Appearantly, Sun (SSH-2.0-Sun_SSH_1.0 must be some Sun product?) has
dumped a list of available locales into the KEXINIT message. That's
broken, locale names and RFC-1766 "language tags" are different
things. And besides, it makes absolutely no sense to include charset
information like "iso_8859_9" here. The language preferences apply to
some some protocol messages atat are intended for human readers e.g.
in like SSH_MSG_DISCONNECT. But such messages are *always* encoded
using utf-8, no matter what the language is.
Do you think you can find the right place for sending a bug report to
Sun? (I'm not a Sun customer, and I'm not aware of any general
bug-report address).
I'd prefer not to increase the algorithm limit for silliness such as
this.
Regards,
/Niels
_______________________________________________
lsh-bugs mailing list
[EMAIL PROTECTED]
http://lists.lysator.liu.se/mailman/listinfo/lsh-bugs
