#1801 INI parser doesn't work with non-ASCII characters
Closed: Duplicate None Opened 11 years ago by jhrozek.

I defined a domain called foĆ³ in the SSSD config file, but the SSD wouldn't start now. It seems the error is coming from the INI parser:

[sssd] [confdb_init_db] (0x0010): Parse error reading configuration file [/etc/sssd/sssd.conf]
[sssd] [ldb] (0x4000): cancel ldb transaction (nesting: 0)
[sssd] [load_configuration] (0x0010): ConfDB initialization has failed [Invalid argument]
[sssd] [main] (0x0020): Error loading configuration database: [22]: Invalid argument

The "Parse error" message comes from calling config_from_fd which is INI parser's function.


Fields changed

milestone: NEEDS_TRIAGE => Tools 1.0

I did some investigation. It is not the ini but the underlying collection. Collection does not allow the keys to be non ASCII. It does not care about the value. The value can be non ASCII. However in this specific case the domain name is the value and the name of the section in the INI file at the same time. The section name is the name of the collection's subtree.
IMO this is fine as is. We can do either of three things:
a. Keep things as is and close this bug as FAD
b. Close the bug and open an RFE for collection to support non ASCII characters and defer it as we decided that we would just document the fact that domains should be named in ASCII characters and there is no other use case for non ASCII characters in keys so far.
c. Actually fix the issue. It would probably not be a huge change but would affect some of the basic assumptions of the collection and thus the impact is a bit unknown. Unit tests will cover a goods deal but I suspect there might be some implications that are yet not predicted or observed.

milestone: Tools 1.0 => NEEDS_TRIAGE

There is already a bug about UTF8 support for collection - https://fedorahosted.org/sssd/ticket/1263

Closing as duplicate.

Given that the domain names are a special case, I agree this is a non-issue really

resolution: => duplicate
status: new => closed

Metadata Update from @jhrozek:
- Issue set to the milestone: NEEDS_TRIAGE

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2843

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata