From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Cc: Daniel Kahn Gillmor <dkg@fifthhorseaman.net>
Subject: Re: T355-smime.sh is flaky
Date: Sat, 11 Sep 2021 21:38:05 -0300 [thread overview]
Message-ID: <87czper5le.fsf@tethera.net> (raw)
In-Reply-To: <87h7pxiek3.fsf@tethera.net>
[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]
David Bremner <david@tethera.net> writes:
> After digging through mml-secure for a while, I realized that the
> problem is not actually in emacs, but in our test harness for gpgsm. I
> added the gpgsm -K to the script, and you can see that the
> test_suite@notmuchmail.org key is not being added.
>
> I think that means there is some kind of intermittent failure with the
> following pipeline
>
> openssl pkcs12 -export -passout pass: -inkey "$NOTMUCH_SRCDIR/test/smime/key+cert.pem" \
> < "$NOTMUCH_SRCDIR/test/smime/test.crt" | \
> gpgsm --batch --no-tty --no-common-certs-import --pinentry-mode=loopback --passphrase-fd 3 \
> --disable-dirmngr --import >"$GNUPGHOME"/import.log 2>&1 3<<<''
>
I wrote the output from openssl to a temporary file, and it appears that
sometimes (like the case I attached), this cannot be imported by "gpgsm
--import". It might be related to the existing bug report [1] from dkg.
One thing I noticed is that the debugging output has broken looking
offset in it.
gpgsm: 872 bytes of RC2 encrypted text
gpgsm: processing certBag
gpgsm: 1224 bytes of 3DES encrypted text
gpgsm: decryption failed; trying charset 'ISO-8859-1'
gpgsm: decryption failed; trying charset 'ISO-8859-15'
gpgsm: decryption failed; trying charset 'ISO-8859-2'
gpgsm: decryption failed; trying charset 'ISO-8859-3'
gpgsm: decryption failed; trying charset 'ISO-8859-4'
gpgsm: decryption failed; trying charset 'ISO-8859-5'
gpgsm: decryption failed; trying charset 'ISO-8859-6'
gpgsm: decryption failed; trying charset 'ISO-8859-7'
gpgsm: decryption failed; trying charset 'ISO-8859-8'
gpgsm: decryption failed; trying charset 'ISO-8859-9'
gpgsm: decryption failed; trying charset 'KOI8-R'
gpgsm: decryption failed; trying charset 'IBM437'
gpgsm: decryption failed; trying charset 'IBM850'
gpgsm: decryption failed; trying charset 'EUC-JP'
gpgsm: decryption failed; trying charset 'BIG5'
gpgsm: data error at "decrypted-text", offset 2646783990
gpgsm: error at "bag-sequence", offset 996
gpgsm: error parsing or decrypting the PKCS#12 file
gpgsm: total number processed: 1
gpgsm: imported: 1
[1]: https://dev.gnupg.org/T4751
[-- Attachment #2: bad.p12 --]
[-- Type: application/pkcs12, Size: 2381 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2021-09-12 0:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 12:25 T355-smime.sh is flaky David Bremner
2021-09-12 0:38 ` David Bremner [this message]
2021-10-02 11:44 ` David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czper5le.fsf@tethera.net \
--to=david@tethera.net \
--cc=dkg@fifthhorseaman.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).