Export as GPG file

Gpg4win help-en
1

using Kleopatra for the first time so please bear with me. I was able to import my .asc key pair but I need to be able to export it as .gpg, not .asc. When I choose export in the beta, I don’t have the option to make it be binary - there is no checkbox. Does giving it just the .gpg file name cause it to export in the correct format? It needs to be in binary to make sure we can import it into the application that needs it specifically to be .gpg not .asc

2

kleopatra should determine the format by the chosen extension. if you export as an .asc file, it will be ascii armored, if you use the .gpg extension, you will get the binary format.

since you were already suspecting this behavour yourself, i wonder why you haven’t just tried and examined the output :wink:

3

I did try but the output on both still looked like ASCII, not binary, even when using the gpg extension. I need binary specifically for a work application and didn’t want to waste time if the output was still ASCII. Thanks for answering my question.

4

Which version did you use?

5

changing the ending for the public key export manully fro asc to gpg works for me both in Gpg4win 4.4.1 and in the current 5.0 beta. The exported file with the ending .gpg is definitively in binary.

6

5.0.0 beta 395

We can’t use software with expired certificates - it will be blocked as not time valid, So I had to use one of the betas.

7

That’s the one I checked because of your remark, it works like @m.eik described it.

We can’t use software with expired certificates - it will be blocked as not time valid, So I had to use one of the betas.

All our release signatures are valid at the time of the release.

I quote from the mailing list gnupg-users on that subject:

We can’t simply resign old releases because this would require to entirely unpack
everything, resign the binaries, create a new installer and sign that
new installer. That is a different software then and requires a new
version.

Further: Authenticode signatures have a timestamp and thus you have assurance when they were issued.

But you can use the 5.0 beta versions, too. The branch is close to loosing the beta status.