Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use utf-8 for client config file #168

Merged
merged 1 commit into from
Aug 14, 2023
Merged

use utf-8 for client config file #168

merged 1 commit into from
Aug 14, 2023

Conversation

Perfect5th
Copy link
Contributor

See https://bugs.launchpad.net/landscape-client/+bug/2028516 for background:

There's actually no good reason not to accept valid utf-8 as the computer-title. Our message schema declares the title as unicode, and it is stored on the server side as unicode.

This bug exists because when we write the provided config to /etc/landscape/client.conf we assume the encoding of that file is ASCII. We shouldn't need to make this assumption, and should instead enforce ASCII-ness on a per-field basis (as we do for other types, such as fields that must be integers, etc).

Copy link
Contributor

@silverdrake11 silverdrake11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Perfect5th Perfect5th merged commit f701bed into canonical:master Aug 14, 2023
5 checks passed
@Perfect5th Perfect5th deleted the 2028516-allow-unicode-settings branch August 14, 2023 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants