From: Leo <sdl.web@gmail.com>
Subject: A few questions on signing/encrypting emails
Date: Tue, 12 Dec 2006 16:27:02 +0000 [thread overview]
Message-ID: <m2y7pdyt9l.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
Hi all,
I lately received some signed emails and I don't know how to properly
handle them. So I started learning to use signing/encrypting
facilities in Gnus by reading the security section in message info.
I have few questions:
o When signing an email, my private key will be used, right?
And I could encrypt an email with just the recipient's pub
key. But when I send an encrypted email, I will also be
prompted to input passphrase. Does this mean signing is
automatically done?
o What is the simplest way to handle multiple personal keys? I
created two keys. One for work and one for anything
else. But when I signed an email, only the one indicated by
pgg-default-user-id is used.
I am somehow stuck with Gnus 5.11 but I have easypg
installed. As I understood, for Gnus 5.11 to sign/encrypt
emails using epg, I need to use pgg-epg.el which is also
installed.
o When I try to encrypt an email to a recipient whose pub key
is not in my pub-key-ring, I will get an error
(wrong-type-argument epg-key-p nil) (full backtrace
attached). How to set up gnus to import the pubkey from
key-server?
If you have any suggestions on signing and encrypting emails, I am
very happy to hear them. Thank you in advance for your help.
[-- Attachment #2: epg-bt.log --]
[-- Type: text/plain, Size: 4049 bytes --]
Debugger entered--Lisp error: (wrong-type-argument epg-key-p nil)
signal(wrong-type-argument (epg-key-p nil))
(condition-case error (setq cipher (epg-encrypt-string context ... ... sign t) pgg-epg-secret-key-id-list nil) (error (while pgg-epg-secret-key-id-list ... ...) (signal ... ...)))
(let ((context ...) (inhibit-redisplay t) cipher) (epg-context-set-armor context t) (epg-context-set-textmode context pgg-text-mode) (epg-context-set-passphrase-callback context (function pgg-epg-passphrase-callback)) (save-excursion (set-buffer ...) (erase-buffer) (set-buffer ...) (erase-buffer)) (condition-case error (setq cipher ... pgg-epg-secret-key-id-list nil) (error ... ...)) (save-excursion (set-buffer ...) (insert cipher)) t)
pgg-epg-encrypt-region(1 637 ("steve@sxemacs.org") t nil)
funcall(pgg-epg-encrypt-region 1 637 ("steve@sxemacs.org") t nil)
apply(funcall pgg-epg-encrypt-region (1 637 ("steve@sxemacs.org") t nil))
pgg-invoke("encrypt-region" epg 1 637 ("steve@sxemacs.org") t nil)
pgg-encrypt-region(1 637 ("steve@sxemacs.org") t)
mml2015-pgg-encrypt((part (sign . "pgpmime") (encrypt . "pgpmime") (tag-location . 1286) (contents . "\nHi Steve,\n\n* [2006.12.11 01:35 +1000] Steve Youngs wrote:\n ^^^^^^^^^^^^\n> * Sebastian Freundt <hroptatyr@sxemacs.org> writes:\n>\n> > Hm, now that I've seen all the goals, it would have been wise to\n> > put 22.1.7 in steve@sxemacs.org--2008, would it not? :)\n>\n> Well, the thought did cross my mind, but then I realised that I'd miss\n> all those annual events that involve beer consumption. You know,\n> birthdays, anniversaries, Octoberfest, any day ending in a `y'. :-)\n\n\nregards,\n-- \nLeo <sdl.web AT gmail.com> (GPG Key: 9283AA3F)\n")) t)
mml2015-encrypt((part (sign . "pgpmime") (encrypt . "pgpmime") (tag-location . 1286) (contents . "\nHi Steve,\n\n* [2006.12.11 01:35 +1000] Steve Youngs wrote:\n ^^^^^^^^^^^^\n> * Sebastian Freundt <hroptatyr@sxemacs.org> writes:\n>\n> > Hm, now that I've seen all the goals, it would have been wise to\n> > put 22.1.7 in steve@sxemacs.org--2008, would it not? :)\n>\n> Well, the thought did cross my mind, but then I realised that I'd miss\n> all those annual events that involve beer consumption. You know,\n> birthdays, anniversaries, Octoberfest, any day ending in a `y'. :-)\n\n\nregards,\n-- \nLeo <sdl.web AT gmail.com> (GPG Key: 9283AA3F)\n")) t)
mml-pgpmime-encrypt-buffer((part (sign . "pgpmime") (encrypt . "pgpmime") (tag-location . 1286) (contents . "\nHi Steve,\n\n* [2006.12.11 01:35 +1000] Steve Youngs wrote:\n ^^^^^^^^^^^^\n> * Sebastian Freundt <hroptatyr@sxemacs.org> writes:\n>\n> > Hm, now that I've seen all the goals, it would have been wise to\n> > put 22.1.7 in steve@sxemacs.org--2008, would it not? :)\n>\n> Well, the thought did cross my mind, but then I realised that I'd miss\n> all those annual events that involve beer consumption. You know,\n> birthdays, anniversaries, Octoberfest, any day ending in a `y'. :-)\n\n\nregards,\n-- \nLeo <sdl.web AT gmail.com> (GPG Key: 9283AA3F)\n")) t)
mml-generate-mime-1((part (sign . "pgpmime") (encrypt . "pgpmime") (tag-location . 1286) (contents . "\nHi Steve,\n\n* [2006.12.11 01:35 +1000] Steve Youngs wrote:\n ^^^^^^^^^^^^\n> * Sebastian Freundt <hroptatyr@sxemacs.org> writes:\n>\n> > Hm, now that I've seen all the goals, it would have been wise to\n> > put 22.1.7 in steve@sxemacs.org--2008, would it not? :)\n>\n> Well, the thought did cross my mind, but then I realised that I'd miss\n> all those annual events that involve beer consumption. You know,\n> birthdays, anniversaries, Octoberfest, any day ending in a `y'. :-)\n\n\nregards,\n-- \nLeo <sdl.web AT gmail.com> (GPG Key: 9283AA3F)\n")))
mml-generate-mime()
message-encode-message-body()
mml-to-mime()
mml-preview(nil)
call-interactively(mml-preview)
[-- Attachment #3: Type: text/plain, Size: 76 bytes --]
--
Leo <sdl.web AT gmail.com> (GPG Key: 9283AA3F)
[-- Attachment #4: Type: text/plain, Size: 161 bytes --]
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
http://lists.gnu.org/mailman/listinfo/info-gnus-english
next reply other threads:[~2006-12-12 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 16:27 Leo [this message]
2007-01-05 6:01 ` Daiki Ueno
2007-01-05 6:08 ` Leo
2007-01-10 17:33 ` Leo
2007-01-11 1:01 ` Daiki Ueno
2007-01-11 2:33 ` Leo
2007-01-11 3:53 ` Daiki Ueno
2007-01-11 9:15 ` Leo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2y7pdyt9l.fsf@sl392.st-edmunds.cam.ac.uk \
--to=sdl.web@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).