Files
webssh/webssh
Kyle Larose dfea8a1624 handle invalid characeters in encoding
When establishing a connection to an SSH server, WebSSH tries to guess
at its encoding using a command sent prior to opening the terminal.
Unfortunately, sometimes this can return data which does not form proper
input for the `encode` function used by `is_valid_encoding` to test
whether the encoding is known.

In particular, we ran in to a case where the server was returning a
string which had a \0 in it when converted to ascii. That raised a
`ValueError` (as opposed to `LookupError`), which was uncaught.

Handle the `ValueError` case as well, treating it as an unknown encoding
so that we fall back on the default.
2023-03-30 10:52:53 -04:00
..
2022-03-09 18:25:09 +01:00
2020-01-23 19:20:43 +08:00
2020-10-02 13:55:56 +08:00
2022-11-21 17:12:05 +08:00
2018-04-23 18:14:42 +08:00