Enigmail / Bugs / #810 getMinimalPubKey requires gnupg 2.1.10

#810 getMinimalPubKey requires gnupg 2.1.10

Status: fixed

Owner: nobody

Labels: None

Found in Version: 2.0.2

Severity: Minor

Thunderbird version: 52.7.0

GnuPG version: 2.0.24

Operating System: Linux

Fixed in version: 2.0.3

Cc: nobody

Updated: 2018-05-05

Created: 2018-04-15

Creator: Adam Mizerski

Private: No

Enigmail changelog states that "The minimum GnuPG version supported is now 2.0.16". But getMinimalPubKey function in keyRing.jsm expects that 'gpg2 --export' prints "[GNUPG:] EXPORTED" to status output. This output is available since gnupg 2.1.10. With earlier version of gnupg, enigmail treats the result of 'gpg2 --export' as failure.

Patrick Brunschwig - 2018-04-16

status: open --> fixed

Fixed in version: --- --> 2.1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Patrick Brunschwig - 2018-04-16

yes indeed. Fixed on master.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

bam80 - 2018-04-21

Is it OK to rely on "[GNUPG:] EXPORTED" string, which may also change in future gpg2 versions?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Patrick Brunschwig - 2018-04-21

Yes. That's how the GnuPG "API" is designed.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Patrick Brunschwig - 2018-05-05

Fixed in version: 2.1 --> 2.0.3
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

getMinimalPubKey requires gnupg 2.1.10

OpenPGP addon for Mozilla Thunderbird

Searches

Help

#810 getMinimalPubKey requires gnupg 2.1.10

Related

Discussion