Bugzilla – Full Text Bug Listing
|Summary:||Windows registry parameters are limited to 255 characters or less|
|Product:||ThinLinc||Reporter:||Peter Åstrand <firstname.lastname@example.org>|
|Component:||Client||Assignee:||Peter Åstrand <email@example.com>|
|Status:||CLOSED FIXED||QA Contact:||Bugzilla mail exporter <firstname.lastname@example.org>|
* The client should correctly handle registry values which are longer than 255 characters * Non-ASCII characters should still be handled correctly
Currently, the ThinLinc client on Windows uses buffers when interacting with the registry which are limited to 255 UCS-2 and UTF-8 characters. If the retrieved value is longer than this, the parameter is silently ignored, and the client fallbacks to the hardcoded default.
> * The client should correctly handle registry values which are longer than 255 characters Yes, tested with reading long (255<x<834 characters) HOST_ALIASES from registry and writing long NFS_EXPORTS to registry. (thinlinc-client-4.9.0post-5897) > * Non-ASCII characters should still be handled correctly Looks like they're still read and written okay. Nitpick: I don't like having "correctly handle" in acceptance criteria, and this one used it in two out of two.