- Szycy
- 27 września 2026 21:21 UTC
- Autor
- Kamo
- Pochęt się
- ea061cb
Guacamole 1.5.5's client reads the #/client/<id> fragment with atob (one character per byte) and btoa's every connection name it lists, so a name outside Latin-1 never opens. The AI workstation's connections were named '… — Watch' / '… — Take over' (an em dash) and the fragment carried UTF-8 bytes: the client asked for 'Workstation â Watch' (404), then threw on btoa, and every Watch and Take over tab stayed blank (SP11 Task 30). The name sealed into a token now goes through **************** (Latin-1 kept, curly quotes and dashes to ASCII, compatibility decomposition or '?' for the rest, controls to spaces), the VNC suffix is ' · Watch' / ' · Take over', and clientId writes those Latin-1 bytes URL-safe and unpadded, exactly as the client's own ClientIdentifier.toString does (a '/' in standard base64 ended the Angular route early). clientId refuses a name the client cannot read. The same fix opens a member's computer named 'José’s PC'.