Page MenuHome GnuPG

mark-antony (Mark Antony)
User

Projects

User does not belong to any projects.

User Details

User Since
Apr 22 2017, 4:32 PM (361 w, 5 d)
Availability
Available

Recent Activity

Nov 5 2017

mark-antony added a comment to T3101: GnuPG 2.2 cannot import secret keys from 1.4/2.0's secring.gpg directly (if it is expired by original expiration date).

What I use to force the old keyring format is to export a public key to a file and rename that to pubring.gpg. And of course delete the pubring.kbx.

Nov 5 2017, 4:15 PM · workaround, gnupg, Bug Report

Sep 25 2017

mark-antony added a comment to T3101: GnuPG 2.2 cannot import secret keys from 1.4/2.0's secring.gpg directly (if it is expired by original expiration date).

Hi gniibe

Sep 25 2017, 6:39 PM · workaround, gnupg, Bug Report

Jun 17 2017

mark-antony removed a project from T3101: GnuPG 2.2 cannot import secret keys from 1.4/2.0's secring.gpg directly (if it is expired by original expiration date): Info Needed.
Jun 17 2017, 8:05 AM · workaround, gnupg, Bug Report

Apr 29 2017

mark-antony added a comment to T3101: GnuPG 2.2 cannot import secret keys from 1.4/2.0's secring.gpg directly (if it is expired by original expiration date).

Thanks, gniibe, for the quick reply.

Apr 29 2017, 6:02 PM · workaround, gnupg, Bug Report

Apr 28 2017

mark-antony added a comment to T3101: GnuPG 2.2 cannot import secret keys from 1.4/2.0's secring.gpg directly (if it is expired by original expiration date).

Thank you for reporting. Sorry, I couldn't understand some part of your report. Perhaps, due to some terminology.

There are four things: primary key public, subkey public, primary key private, and subkey private.

Apr 28 2017, 9:55 PM · workaround, gnupg, Bug Report

Apr 22 2017

mark-antony created T3101: GnuPG 2.2 cannot import secret keys from 1.4/2.0's secring.gpg directly (if it is expired by original expiration date) in the S1 Public space.
Apr 22 2017, 4:37 PM · workaround, gnupg, Bug Report