Mailing List Archive: gpgsm: decrypting session key failed: Invalid session key

gpgsm: decrypting session key failed: Invalid session key

Jul 18, 2019, 7:58 AM

Post #1 of 6 (1342 views)

Hi,

this is a bug report email, at least i expect it is a bug.

An increasing amount of x509 encrypted email i receive can not be
decrypted with gpgsm anymore. At first i assumed that the senders keys
would be somehow different and trigger the bug in gpgsm. Later i found
that it could also be their mail client, but whatever it is on the remote
end i expect it to be a bug in gpgsm.
The same files can be decrypted with openssl just fine.

Affected versions: gpgsm <= latest master (gnupg-2.2.7-609-g4195ce15f)
Platform Linux: x86_64

Expected result:
Mail can be decrypted and read.

Actual result:
Decryption fails with "gpgsm: decrypting session key failed: Invalid
session key"

Details: (from latest git build)
$ /foo/gnupg/sm/gpgsm --debug-level guru --decrypt smime_bad.p7m
...
gpgsm: DBG: chan_5 -> PKDECRYPT
gpgsm: DBG: chan_5 <- S INQUIRE_MAXLEN 4096
gpgsm: DBG: chan_5 <- INQUIRE CIPHERTEXT
gpgsm: DBG: chan_5 -> [. 44 20 28 37 3a 65 6e 63 2d 76 61 6c 28 33 3a 72 ...(273 byte(s) skipped) ]
gpgsm: DBG: chan_5 -> END
Vim: Reading from stdin...
gpgsm: DBG: chan_5 <- S PADDING 0
gpgsm: DBG: chan_5 <- [. 44 20 28 35 3a 76 61 6c 75 65 33 32 3a e5 ff cd ...(31 byte(s) skipped) ]
gpgsm: DBG: chan_5 <- OK
gpgsm: DBG: pkcs1 encoded session key: e5ffcd51107897682fc0d805173d85ce7088fddabda33ac74da73b0813c04593
gpgsm: decrypting session key failed: Invalid session key
gpgsm: message decryption failed: Invalid session key <GpgSM>

Hope that helps. I would be happy to provide more information. I have
many of those _bad.p7m files.

regards,
Henning

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

Re: gpgsm: decrypting session key failed: Invalid session key [ In reply to ]

gnupg-devel at gnupg

Jul 24, 2019, 1:46 AM

Post #2 of 6 (1340 views)

Permalink

Should i rather open an issue on https://dev.gnupg.org/. I think i read
somewhere that this list can be/is used for reporting bugs.

regards,
Henning

Am Thu, 18 Jul 2019 16:58:20 +0200
schrieb Henning Schild via Gnupg-devel <gnupg-devel@gnupg.org>:

> Hi,
>
> this is a bug report email, at least i expect it is a bug.
>
> An increasing amount of x509 encrypted email i receive can not be
> decrypted with gpgsm anymore. At first i assumed that the senders keys
> would be somehow different and trigger the bug in gpgsm. Later i found
> that it could also be their mail client, but whatever it is on the
> remote end i expect it to be a bug in gpgsm.
> The same files can be decrypted with openssl just fine.
>
> Affected versions: gpgsm <= latest master (gnupg-2.2.7-609-g4195ce15f)
> Platform Linux: x86_64
>
> Expected result:
> Mail can be decrypted and read.
>
> Actual result:
> Decryption fails with "gpgsm: decrypting session key failed: Invalid
> session key"
>
> Details: (from latest git build)
> $ /foo/gnupg/sm/gpgsm --debug-level guru --decrypt smime_bad.p7m
> ...
> gpgsm: DBG: chan_5 -> PKDECRYPT
> gpgsm: DBG: chan_5 <- S INQUIRE_MAXLEN 4096
> gpgsm: DBG: chan_5 <- INQUIRE CIPHERTEXT
> gpgsm: DBG: chan_5 -> [. 44 20 28 37 3a 65 6e 63 2d 76 61 6c 28 33 3a
> 72 ...(273 byte(s) skipped) ] gpgsm: DBG: chan_5 -> END
> Vim: Reading from stdin...
> gpgsm: DBG: chan_5 <- S PADDING 0
> gpgsm: DBG: chan_5 <- [. 44 20 28 35 3a 76 61 6c 75 65 33 32 3a e5 ff
> cd ...(31 byte(s) skipped) ] gpgsm: DBG: chan_5 <- OK
> gpgsm: DBG: pkcs1 encoded session key:
> e5ffcd51107897682fc0d805173d85ce7088fddabda33ac74da73b0813c04593
> gpgsm: decrypting session key failed: Invalid session key gpgsm:
> message decryption failed: Invalid session key <GpgSM>
>
>
> Hope that helps. I would be happy to provide more information. I have
> many of those _bad.p7m files.
>
> regards,
> Henning
>
> _______________________________________________
> Gnupg-devel mailing list
> Gnupg-devel@gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-devel

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

Re: gpgsm: decrypting session key failed: Invalid session key [ In reply to ]

gniibe at fsij

Jul 25, 2019, 7:43 PM

Post #3 of 6 (1340 views)

Permalink

Henning Schild via Gnupg-devel <gnupg-devel@gnupg.org> wrote:
> An increasing amount of x509 encrypted email i receive can not be
> decrypted with gpgsm anymore.

Is there any change of cipher used?

> Details: (from latest git build)
> $ /foo/gnupg/sm/gpgsm --debug-level guru --decrypt smime_bad.p7m
> ...
> gpgsm: DBG: chan_5 -> PKDECRYPT
> gpgsm: DBG: chan_5 <- S INQUIRE_MAXLEN 4096
> gpgsm: DBG: chan_5 <- INQUIRE CIPHERTEXT
> gpgsm: DBG: chan_5 -> [. 44 20 28 37 3a 65 6e 63 2d 76 61 6c 28 33 3a 72 ...(273 byte(s) skipped) ]
> gpgsm: DBG: chan_5 -> END
> Vim: Reading from stdin...
> gpgsm: DBG: chan_5 <- S PADDING 0
> gpgsm: DBG: chan_5 <- [. 44 20 28 35 3a 76 61 6c 75 65 33 32 3a e5 ff cd ...(31 byte(s) skipped) ]
> gpgsm: DBG: chan_5 <- OK
> gpgsm: DBG: pkcs1 encoded session key: e5ffcd51107897682fc0d805173d85ce7088fddabda33ac74da73b0813c04593
> gpgsm: decrypting session key failed: Invalid session key
> gpgsm: message decryption failed: Invalid session key <GpgSM>

The encoded session key is 32-byte, which looks like a key of AES-256.

My guess is, this is the point where we need a fix:

diff --git a/sm/decrypt.c b/sm/decrypt.c
index ec9800840..af509fea1 100644
--- a/sm/decrypt.c
+++ b/sm/decrypt.c
@@ -75,7 +75,7 @@ prepare_decryption (ctrl_t ctrl, const char *hexkeygrip, const char *desc,
log_printhex (seskey, seskeylen, "pkcs1 encoded session key:");

n=0;
- if (seskeylen == 24 || seskeylen == 16)
+ if (seskeylen == 32 || seskeylen == 24 || seskeylen == 16)
{
/* Smells like a 3-DES or AES-128 key. This might happen
* because a SC has already done the unpacking. A better
--

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

Re: gpgsm: decrypting session key failed: Invalid session key [ In reply to ]

gnupg-devel at gnupg

Jul 26, 2019, 2:28 AM

Post #4 of 6 (1340 views)

Permalink

Am Fri, 26 Jul 2019 11:43:38 +0900
schrieb NIIBE Yutaka <gniibe@fsij.org>:

> Henning Schild via Gnupg-devel <gnupg-devel@gnupg.org> wrote:
> > An increasing amount of x509 encrypted email i receive can not be
> > decrypted with gpgsm anymore.
>
> Is there any change of cipher used?

I did not analyze further. It seems to be newer versions of Outlook
that produce mail i can not decrypt anymore.

> > Details: (from latest git build)
> > $ /foo/gnupg/sm/gpgsm --debug-level guru --decrypt smime_bad.p7m
> > ...
> > gpgsm: DBG: chan_5 -> PKDECRYPT
> > gpgsm: DBG: chan_5 <- S INQUIRE_MAXLEN 4096
> > gpgsm: DBG: chan_5 <- INQUIRE CIPHERTEXT
> > gpgsm: DBG: chan_5 -> [. 44 20 28 37 3a 65 6e 63 2d 76 61 6c 28 33
> > 3a 72 ...(273 byte(s) skipped) ] gpgsm: DBG: chan_5 -> END
> > Vim: Reading from stdin...
> > gpgsm: DBG: chan_5 <- S PADDING 0
> > gpgsm: DBG: chan_5 <- [. 44 20 28 35 3a 76 61 6c 75 65 33 32 3a e5
> > ff cd ...(31 byte(s) skipped) ] gpgsm: DBG: chan_5 <- OK
> > gpgsm: DBG: pkcs1 encoded session key:
> > e5ffcd51107897682fc0d805173d85ce7088fddabda33ac74da73b0813c04593
> > gpgsm: decrypting session key failed: Invalid session key gpgsm:
> > message decryption failed: Invalid session key <GpgSM>
>
> The encoded session key is 32-byte, which looks like a key of AES-256.
>
> My guess is, this is the point where we need a fix:

Sweet, that simple change did the trick! Do you know how to turn that
into an upstream patch. My guess is that we are still talking about a
dirty hack here and some documentation, test-cases need to updated.
Maybe even more code to deal with AES-256 will be required?

regards,
Henning

> diff --git a/sm/decrypt.c b/sm/decrypt.c
> index ec9800840..af509fea1 100644
> --- a/sm/decrypt.c
> +++ b/sm/decrypt.c
> @@ -75,7 +75,7 @@ prepare_decryption (ctrl_t ctrl, const char
> *hexkeygrip, const char *desc, log_printhex (seskey, seskeylen,
> "pkcs1 encoded session key:");
> n=0;
> - if (seskeylen == 24 || seskeylen == 16)
> + if (seskeylen == 32 || seskeylen == 24 || seskeylen == 16)
> {
> /* Smells like a 3-DES or AES-128 key. This might happen
> * because a SC has already done the unpacking. A better

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

Re: gpgsm: decrypting session key failed: Invalid session key [ In reply to ]

gnupg-devel at gnupg

Sep 30, 2019, 1:42 PM

Post #5 of 6 (1295 views)

Permalink

On Fri 2019-07-26 11:43:38 +0900, NIIBE Yutaka wrote:
> Henning Schild via Gnupg-devel <gnupg-devel@gnupg.org> wrote:
>> An increasing amount of x509 encrypted email i receive can not be
>> decrypted with gpgsm anymore.
>
> Is there any change of cipher used?
>
>> Details: (from latest git build)
>> $ /foo/gnupg/sm/gpgsm --debug-level guru --decrypt smime_bad.p7m
>> ...
>> gpgsm: DBG: chan_5 -> PKDECRYPT
>> gpgsm: DBG: chan_5 <- S INQUIRE_MAXLEN 4096
>> gpgsm: DBG: chan_5 <- INQUIRE CIPHERTEXT
>> gpgsm: DBG: chan_5 -> [. 44 20 28 37 3a 65 6e 63 2d 76 61 6c 28 33 3a 72 ...(273 byte(s) skipped) ]
>> gpgsm: DBG: chan_5 -> END
>> Vim: Reading from stdin...
>> gpgsm: DBG: chan_5 <- S PADDING 0
>> gpgsm: DBG: chan_5 <- [. 44 20 28 35 3a 76 61 6c 75 65 33 32 3a e5 ff cd ...(31 byte(s) skipped) ]
>> gpgsm: DBG: chan_5 <- OK
>> gpgsm: DBG: pkcs1 encoded session key: e5ffcd51107897682fc0d805173d85ce7088fddabda33ac74da73b0813c04593
>> gpgsm: decrypting session key failed: Invalid session key
>> gpgsm: message decryption failed: Invalid session key <GpgSM>
>
> The encoded session key is 32-byte, which looks like a key of AES-256.
>
> My guess is, this is the point where we need a fix:
>
> diff --git a/sm/decrypt.c b/sm/decrypt.c
> index ec9800840..af509fea1 100644
> --- a/sm/decrypt.c
> +++ b/sm/decrypt.c
> @@ -75,7 +75,7 @@ prepare_decryption (ctrl_t ctrl, const char *hexkeygrip, const char *desc,
> log_printhex (seskey, seskeylen, "pkcs1 encoded session key:");
>
> n=0;
> - if (seskeylen == 24 || seskeylen == 16)
> + if (seskeylen == 32 || seskeylen == 24 || seskeylen == 16)
> {
> /* Smells like a 3-DES or AES-128 key. This might happen
> * because a SC has already done the unpacking. A better

It looks like this change was adopted in GnuPG master as
ef2424144a070c9199e40424ec8d9b5a9919aa72. Should this be backported to
the 2.2 stable branch?

--dkg

Re: gpgsm: decrypting session key failed: Invalid session key [ In reply to ]

gnupg-devel at gnupg

Sep 30, 2019, 10:58 PM

Post #6 of 6 (1295 views)

Permalink

> It looks like this change was adopted in GnuPG master as
> ef2424144a070c9199e40424ec8d9b5a9919aa72. Should this be backported to
> the 2.2 stable branch?

Already happened in the repo (a9816d5fb13edb30c5d12cf85ae3e1a114fcc2c1)
will go into 2.2.18 - tracked at https://dev.gnupg.org/T4684

Salam-Shalom,

Werner

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.

Mailing List Archive

Attached Files:

Attached Files: