Adam Funk wrote: > On 2006-05-15, Ingo Klöcker <[EMAIL PROTECTED]> wrote: > <snip> >>> I'm running the Debian kmail 3.3.2-3 package and gpg 1.4.3 compiled >>> from the source. >>> >>> As far as I can tell, it flatly refuses to let me encrypt a message >>> to any key that doesn't have a signature chain back to a trusted key. >>> I can see the usefulness of a warning about doing this, but I've >>> accidentally sent a message unencrypted while trying to find a way >>> around the problem. >>> >>> Is there any way to override this restriction? >>> >> >> No, but there's a corresponding (and already very old) wish in KDE's bug=20 >> tracking system (bugs.kde.org). > > Would lsign-ing the key circumvent the problem?
Yes. > Would it cause any other problems? > You will be asked to set an ownertrust value... It might be worth trying to find an actual trust path using Wotsap (http://www.lysator.liu.se/~jc/wotsap/) or similar as well as lsigning the key, but YMMV. -- Alphax Death to all fanatics! Down with categorical imperative! OpenPGP key: http://tinyurl.com/lvq4g
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
