On Sun, 14 Mar 2021 14:32, Christoph Biedl said: > Point is, the legacy file ~/.gnupg/options is still being used in > surprisingly many applications, also in documentation:
Then please file a bug against such documentation. And maybe even against any application which read the option filre directly, that is without using gpgconf. > https://codesearch.debian.net/search?q=.gnupg%2Foptions&literal=1 Look at the code shown tehre: Almost everywhere it is used as a fallback from gpg.conf. > In Debian, revert that commit, and emit a deprecation warning if the > legacy file is parsed. Sysadmins will kill you if you do that. The global conf file has been a long standing request from many parties. It comes very hadny for large installations because it can be used to enforce options on users. That is why I took the trouble to actually backported this from master. Supporting the legacy option file would be a Bad Idea. In particular for a new major release it should be not a problem to add release notes mention that after 18 years the deprecated legacy option file is not anymore supported. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
signature.asc
Description: PGP signature
