From: Daiki Ueno <ueno@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: ding@gnus.org
Subject: Re: gpgsm: smime, various secret keys, mml2015-sign-with-sender for smime
Date: Mon, 07 Jan 2013 13:06:05 +0900 [thread overview]
Message-ID: <87lic58wnm.fsf-ueno@gnu.org> (raw)
In-Reply-To: <878v87hffx.fsf@mat.ucm.es> (Uwe Brauer's message of "Sat, 05 Jan 2013 15:28:34 +0100")
Uwe Brauer <oub@mat.ucm.es> writes:
> 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.
I've added mml-smime-sign-with-sender:
http://bzr.savannah.gnu.org/lh/emacs/trunk/revision/111432?start_revid=111432
Could you test if it works? I don't have multiple S/MIME keys.
Regards,
--
Daiki Ueno
next prev parent reply other threads:[~2013-01-07 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 14:28 Uwe Brauer
2013-01-07 4:06 ` Daiki Ueno [this message]
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=87lic58wnm.fsf-ueno@gnu.org \
--to=ueno@gnu.org \
--cc=ding@gnus.org \
--cc=oub@mat.ucm.es \
/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).