From: Efraim Flashner <efraim@flashner.co.il>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: guix-devel@gnu.org
Subject: Re: Signing emails with mu4e (was Re: Hello, new committer here!)
Date: Tue, 1 Sep 2020 16:06:06 +0300 [thread overview]
Message-ID: <20200901130606.GD856@E5400> (raw)
In-Reply-To: <87lfht8ytb.fsf@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 3970 bytes --]
On Tue, Sep 01, 2020 at 01:29:52PM +0100, Pierre Langlois wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
>
> Pierre Langlois writes:
>
> > Pierre Langlois writes:
> >
> >> Hello Guix,
> >>
> >> So, as indicated in our contributing process on the manual, I'm happy to
> >> announce maintainers have agreed to give me commit access, thank you
> >> everybody!
> >>
> >> I believe I need somebody to add my GPG keys to the Guix keyring before
> >> I can push my first commit. Which I think is going to be
> >> https://issues.guix.gnu.org/43138 (although, if this one is urgent,
> >> don't hesitate to push it for me!).
> >>
> >> If I'm not mistaken, since I'm using a subkey as a signing key, it
> >> should be this way (that's what I've had to do sign a personal channel):
> >>
> >> (;; primary: "41CA 12EA DE0C F33F 6885 A58F 5719 6E37 E00B 77FD"
> >> "72D5 3D81 8CB6 F4A1 7258 374C A8FC 9E44 7F4F 7D54"
> >> (name "planglois")
> >
> > Huh, it looks like the email signature got messed up. I'm using mu4e but
> > it wasn't finding my key as it used to. I rolled-back to emacs 26 and
> > that seemed to have worked, except the email sent wasn't signed
> > properly.
> >
> > So, with this email, if I do `M-x mml-secure-message-sign-pgpmime' and
> > try and send, I get a backtrace:
> >
> > ```
> > Debugger entered--Lisp error: (error "Couldn’t find any signer names; try setting `mml-s...")
> > signal(error ("Couldn’t find any signer names; try setting `mml-s..."))
> > error("Couldn't find any signer names%s" "; try setting `mml-secure-smime-sign-with-sender'.")
> > mml-secure-epg-sign(OpenPGP t)
> > mml2015-epg-sign((part (sign . "pgpmime") (tag-location . 477) (contents . "Pierre Langlois writes:\n\n> Hello Guix,\n>\n> So, as ...")))
> > mml2015-sign((part (sign . "pgpmime") (tag-location . 477) (contents . "Pierre Langlois writes:\n\n> Hello Guix,\n>\n> So, as ...")))
> > mml-pgpmime-sign-buffer((part (sign . "pgpmime") (tag-location . 477) (contents . "Pierre Langlois writes:\n\n> Hello Guix,\n>\n> So, as ...")))
> > mml-generate-mime-1((part (sign . "pgpmime") (tag-location . 477) (contents . "Pierre Langlois writes:\n\n> Hello Guix,\n>\n> So, as ...")))
> > mml-generate-mime(nil nil)
> > message-encode-message-body()
> > message-send-mail(nil)
> > message-send-via-mail(nil)
> > message-send(nil)
> > message-send-and-exit(nil)
> > ```
> >
> > I've tried setting `mml-secure-smime-sign-with-sender' to `t' that's not
> > helping. I'm not sure what's going on, are there any mu4e users here
> > that can sign emails? I wonder if it's do to with the recent gnupg
> > update instead of emacs.
>
> Right, it works with these variables set:
>
> (setq mml-secure-openpgp-signers '("KEYID"))
> (setq mml-secure-opengpg-sign-with-sender t)
>
> And using '<#secure method=gpg mode=sign>'
>
> I'm not sure what's broken, this used to "just work" by default without
> having to tell emacs where to find the signer key. mmm
> -----BEGIN PGP SIGNATURE-----
>
> iQEzBAEBCgAdFiEEctU9gYy29KFyWDdMqPyeRH9PfVQFAl9OPsAACgkQqPyeRH9P
> fVRc5wgAyc0kPz83JHW2hel9lxD5t7ejhtjjUdGwVtHEF0kWcyt4vkfnKPL4RlwA
> raZR9jGZ9siy/L6eizwhqhXs8obxOKgetiXrVhpOGBmMfKmeyjiJ1/SrgryIDoXc
> 826K1jzlTMcxKvF80YDrT5btmZkPHuOgDir/AMh9mCZB5nJtY75qGJzimzXHrOmN
> KZiIEe0QZdB9zY+k4LSjI80QBGi8Wyj8OxlpFyr4U3dIUdyN6OVKutD6ezfP/xXY
> U+HcU8KizXhiAwZxJ/9MOvL9ZPZT1T73xScTOaiUFe9i78i9bFvF/brAOGINUK/s
> 1TDhhRKZAys+d1t94IS5NDQgmvmqcg==
> =lha/
> -----END PGP SIGNATURE-----
>
Not sure what's up with the inline signing of the message. I had to pipe
the whole message from mutt into 'gpg --verify' for it to check the
signature.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-01 13:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 10:52 Hello, new committer here! Pierre Langlois
2020-09-01 12:11 ` Signing emails with mu4e (was Re: Hello, new committer here!) Pierre Langlois
2020-09-01 12:29 ` Pierre Langlois
2020-09-01 13:06 ` Efraim Flashner [this message]
2020-09-01 13:35 ` Pierre Neidhardt
2020-09-01 23:00 ` Amin Bandali
2020-09-02 10:15 ` Pierre Langlois
2020-09-04 17:16 ` Signing emails with Emacs 27.1 Giovanni Biscuolo
2020-09-04 17:47 ` Pierre Langlois
2020-09-07 9:19 ` Hello, new committer here! Ludovic Courtès
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=20200901130606.GD856@E5400 \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=pierre.langlois@gmx.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.