On Sun, Apr 14, 2013 at 02:22:47PM +0200, Bill Allombert wrote: > Why files in ca-certificates are configuration files in the first place ? > I doubt users are expected to edit PEM certificate.
Correction of what I said before: ca-certificates does not ship them as conffiles, but as configuration files. Actually they are symbolic links to the actual certificates shipped within /usr/share. The purpose of the links is to allow the user to remove particular certificates, that she does not trust. As such those symbolic links express configuration choices. As it stands I see ca-certificates as a valid use case of UTF-8 characters in configuration file names. I strongly suggest to talk to the ca-certificates maintainers before changing the policy in a way this way. The reason for reporting this bug was to get a way to interpret filenames *now*. The proposed wording (by Charles Plessy) enables us to do so. I would like to see further restrictions on filenames deferred to another issue, because it has less of a perceived benefit and there is not the broad consensus and support for further restrictions. Clearly further discussion is required for these. Helmut -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130414124726.GA26069@localhost.localdomain
