Werner Koch wrote... > Right, that should not have happened. Fixing this i[s] complicated and > thus I would suggest to use a symlink or way better to get rename the > file.
Can you elaborate *how* complicated that would be?
Point is, the legacy file ~/.gnupg/options is still being used in
surprisingly many applications, also in documentation:
https://codesearch.debian.net/search?q=.gnupg%2Foptions&literal=1
It will not be possible to fix all this in time before the Debian 11
("bullseye") release. Breaking applications and providing wrong
information is bad, and worse when it's done in a cryptographic context.
So for Debian 11 I consider supporting the legacy location a must. The
question was rather how to achieve that:
In Debian, revert that commit, and emit a deprecation warning if the
legacy file is parsed.
Or:
Upstream: Re-Enable legacy file support for a limited time, and emit a
deprecation warning as above.
The latter is way more appealing as it allows best of both worlds, and
also other distributions would benefit from that. Hence my initial
question.
Christoph
signature.asc
Description: PGP signature
