Hi, On Monday 15 March 2021 08:56:36 CET Christoph Biedl wrote: > > > Point is, the legacy file ~/.gnupg/options is still being used in > > > surprisingly many applications, also in documentation:
Sorry, but a quick look at the codesearch you linked shows it is not used anywhere except in some outdated documentation or syntax highlighting. Even https://sources.debian.org/src/samhain/4.1.4-2/scripts/samhainadmin.pl.in/? hl=66#L66 which looked from the codesearch as the most promising candidate uses gpg.conf preferredly. > For *after* the release, everything will be possible. My intent is to > keep impact for the current release low. I am using GnuPG since 2006 and I was not even aware that .gnupg/options was a thing before this thread. > My preferred solution was to restore the old behaviour for a limited > time, i.e. parsing the legacy config file, plus emitting that warning. > This will give everybody a chance to adjust their configuration. I think this is an overraction. I cannot imagine that more then a handful of users are affected by this change of ignoring such an historic file. Also those are options, this is nothing security critical in my opinion. Options and option defaults change regularly from one debian release the next. Best Regards, Andre -- GnuPG.com - a brand of g10 Code, the GnuPG experts. g10 Code GmbH, Erkrath/Germany, AG Wuppertal HRB14459 GF Werner Koch, USt-Id DE215605608, www.g10code.com. GnuPG e.V., Rochusstr. 44, D-40479 Düsseldorf. VR 11482 Düsseldorf Vorstand: W.Koch, B.Reiter, A.Heinecke Mail: bo...@gnupg.org Finanzamt D-Altstadt, St-Nr: 103/5923/1779. Tel: +49-211-28010702
signature.asc
Description: This is a digitally signed message part.
