| Summary: | It is useful to transfer locale-related environment variables acros the conection | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | jchadima | ||||
| Component: | Miscellaneous | Assignee: | Assigned to nobody <unassigned-bugs> | ||||
| Status: | CLOSED WONTFIX | ||||||
| Severity: | normal | CC: | djm, jfch | ||||
| Priority: | P2 | ||||||
| Version: | 5.2p1 | ||||||
| Hardware: | Other | ||||||
| OS: | Linux | ||||||
| Attachments: |
|
||||||
|
Description
jchadima
2009-08-28 15:22:07 AEST
Created attachment 1679 [details]
Patch solvin the problem
That patch seems completely unrelated, it is something to do with passing locale-related environment variables. oops, wrong bug! Not all platforms support these environment variables, some may not be entirely safe to pass. Worse, as far as I know, there is no standardisation in locale names between operating systems. The SSH protocol doesn't really have a locale negotiation mechanism (it does have a "language" negotiation, but it is unclear how that should be interpreted). If you want to add locale-passing to SSH, I think it would be best to take it up on the IETF secsh working group mailing list, but naively passing environment variables is not sufficient. Mass move of RESOLVED bugs to CLOSED now that 5.3 is out. |