From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: gpgsm: smime, various secret keys, mml2015-sign-with-sender for smime
Date: Sat, 05 Jan 2013 15:28:34 +0100 [thread overview]
Message-ID: <878v87hffx.fsf@mat.ucm.es> (raw)
Hello
I started to use smime, via xemacs, gnus, epg and gpgsm. [1]
I have 3 accounts, one for work two private ones. I obtained free
certificates from www.comodo.com.
Now gpgsm chooses the secret key for signing, either as
- the first which is listed by gpsm -list-secret-keys
- a default one, which can be configured in gpsm.conf
- the one specified by the senders address via the command.
gpgsm -su oub.oub.oub@gmail.com --armor < test > ciphertext4
However it seems not to be possible to configure gpgsm (via the
gpgsm.con file) such that it chooses the relevant secret keys according
to the email address of the sender.
(user-mail-address)
And that is why it should be implemented in lisp. Daiko Ueno, the author
of epg, also referred to the mml2015-sign-with-sender function, but this
function is, as I understand it correctly, only for gpg.
So can such a function be implemented for smime please?[2]
Thanks
Uwe Brauer
Footnotes:
[1] I used gpg, but most of the people I correspondence considered it
as to user unfriendly.
[2] like
(defvar gpgsm-signing-command "/usr/bin/gpgsm -su %s --armor < %s > %s")
(let ((secret-key-id user-mail-address)
(cleartext some-mail-text)
(cipertext (make-temp-file (expand-file-name "cipertext" temporary-file-directory) nil ".asc")))
(shell-command
(format gpgsm-signing-command
secret-key-id
cleartext
cipertext)))
next reply other threads:[~2013-01-05 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 14:28 Uwe Brauer [this message]
2013-01-07 4:06 ` Daiki Ueno
2013-01-07 19:57 ` Uwe Brauer
2013-01-07 22:01 ` Daiki Ueno
2013-01-07 22:16 ` Uwe Brauer
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=878v87hffx.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.org \
/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).