Your message dated Sat, 12 Apr 2025 14:43:08 +0200
with message-id <[email protected]>
and subject line Re: Bug#427703: Please support an encrypt-to-self option in
~/.gnupg/gpg.conf
has caused the Debian Bug report #427703,
regarding [gnupg/806,807] gnupg: please support an encrypt-to-self option in
/home/dl/.gnupg/gpg.conf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
427703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427703
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg
Version: 1.4.6-2
Severity: wishlist
Similar to default-recipient-self, please support an encrypt-to-self option,
to avoid the need to specify your key ID. This would allow a non-key-specific
~/.gnupg/gpg.conf , for use as an example or as a configuration file shared
between machines (such as via a version control system).
Thanks,
Josh Triplett
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-rc1 (PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gnupg depends on:
ii gpgv 1.4.6-2 GNU privacy guard - signature veri
ii libbz2-1.0 1.0.3-7 high-quality block-sorting file co
ii libc6 2.5-10 GNU C Library: Shared libraries
ii libldap2 2.1.30-13.4 OpenLDAP libraries
ii libreadline5 5.2-3 GNU readline and history libraries
ii libusb-0.1-4 2:0.1.12-7 userspace USB programming library
ii makedev 2.3.1-83 creates device files in /dev
ii zlib1g 1:1.2.3-15 compression library - runtime
gnupg recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.1.10-1
On 2007-06-09 Josh Triplett <[email protected]> wrote:
[...]
> One other, somewhat more elegant possibility: how about allowing a
> list of key IDs for default-key, and selecting as the default key the
> first one with a private key available? That would allow a single
> configuration that said "If I have my secure private key, use that,
> otherwise use my somewhat-secure work key."
[...]
This was implemented in e16d7168c54e5f7bc2f0037806ee4f730930eaf0
followed by de9b2340153d70b083494d1a277a384dcf43bff0
Add --encrypt-to-default-key.
cu Andreas
--- End Message ---
