Re: Exporting/ importing changes expiration date of subkeys...
On Mon 2018-11-12 18:27:59 +0100, gnupgpacker wrote:
>> the "classic" version of GnuPG (the 1.4.x series) not only does not
>> ...
>> If you upgrade to the modern version of GnuPG on your windows machine,
>> and then try to re-import, i think you'll find the merge issue resolved.
>
> GnuPG 1.4.23 is part of GnuPG-Pack with old but convincing GPGrelay
> included, which needs older version 1.4x.
> http://www.rose-indorf.de/gnupgpack/
>
> Exporting (older) RSA keys should be independent from GnuPG version 1.4x or
> 2.2x, isn't it?
It's difficult for me to tell what you're asking about.
For each import/export operation you're asking about (both successes and
failures), could you give the following information clearly:
* Are you exporting secret keys?
or exporting public keys?
* where were the secret keys originally created? (on what program does
the original export happen?)
* which program is doing the import?
* does the program doing the import modify the OpenPGP certificate in
any way?
* does it re-export the OpenPGP certificate? if so, is that
re-exported certificate loaded back into the original program?
> Importing those keys are working faultless with:
> Flipdog CryptoPlugin/ Android-8.1:
> https://i.imgur.com/TmR3oiz.png
> and
> OpenKeychain/ Android-8.1 too:
> https://i.imgur.com/vYa1pUl.png
> Expiration dates of key and 3 subkeys are correct set to 31.12.2019!
If possible, please include these screenshots as decently-sized (small)
attachments, rather than linking to a potentially ephemeral site like
imgur! we want these archives to be ueful even after imgur dies or gets
bought :)
> Only importing with R2mail2/ Android-8.1 causes described expiration error.
> In my opinion it depends on key structure (1 main key, 3 subkeys for
> S/A/E)!?
> If using a 'normal' key with 1 main key S/C/A and 1 subkey for E, importing
> to R2mail2 works, even if expiration date has been enhanced.
it is not normal for the primary key to be marked as
authentication-capable ("A"). If you have a tool that is doing that,
please report back what tool that is, on what platform and what version!
Regards,
--dkg
signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Exporting/ importing changes expiration date of subkeys...
Hello, and thanks for reply! > the "classic" version of GnuPG (the 1.4.x series) not only does not > ... > If you upgrade to the modern version of GnuPG on your windows machine, > and then try to re-import, i think you'll find the merge issue resolved. GnuPG 1.4.23 is part of GnuPG-Pack with old but convincing GPGrelay included, which needs older version 1.4x. http://www.rose-indorf.de/gnupgpack/ Exporting (older) RSA keys should be independent from GnuPG version 1.4x or 2.2x, isn't it? Importing those keys are working faultless with: Flipdog CryptoPlugin/ Android-8.1: https://i.imgur.com/TmR3oiz.png and OpenKeychain/ Android-8.1 too: https://i.imgur.com/vYa1pUl.png Expiration dates of key and 3 subkeys are correct set to 31.12.2019! Only importing with R2mail2/ Android-8.1 causes described expiration error. In my opinion it depends on key structure (1 main key, 3 subkeys for S/A/E)!? If using a 'normal' key with 1 main key S/C/A and 1 subkey for E, importing to R2mail2 works, even if expiration date has been enhanced. Any hint how to bypass this issue? Thx + regards. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Exporting/ importing changes expiration date of subkeys...
Hi there-- On Mon 2018-11-12 11:04:09 +0100, gnupgpac...@on.yourweb.de wrote: > there occurs an issue while exporting/ importing keypair from > Windows-7/GPG-1.423 to Android-8.1/R2mail2. 1.423 is not a valid GnuPG version, so i assume you meant GnuPG 1.4.23. the "classic" version of GnuPG (the 1.4.x series) not only does not support merging secret keys effectively, it does not support modern asymmetric cryptographic mechanisms like curve25519 and ed25519. If you upgrade to the modern version of GnuPG on your windows machine, and then try to re-import, i think you'll find the merge issue resolved. You'll also get better support going forward. --dkg ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Update FAQ about revocation certificates?
fwiw, i agree with Damien that the existing text in the FAQ about generating a revocation certificate should be removed. I think that there should be some text like "where can i find my key's revocation certificate?" which could be added to the FAQ. However, situations like these: On Sat 2018-11-10 15:20:41 +, MFPA wrote: > Not immediately after generating a new GnuPG certificate. But it > probably still belongs under "some common best practices". A user > might find they have deleted the auto-generated revocation > certificate, or the disk where it is stored may have died. Or maybe a > user is revoking a key and wants to generate a revocation certificate > that gives a reason for the revocation. Sound like corner cases to me, and they will clutter the FAQ. The FAQ is not designed to answer all possible situations (and certainly not general file system management questions, etc). It will be better (clearer, simpler) if it is targeted on the truly frequently-asked questions. For the corner cases, there is the man page, and there is DETAILS.gz, and there is the mailing list, and there is the source. I salute Damien's effort to get the FAQ into a more maintainable and accessible state. --dkg signature.asc Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Exporting/ importing changes expiration date of subkeys...
Hello, there occurs an issue while exporting/ importing keypair from Windows-7/GPG-1.423 to Android-8.1/R2mail2. Private/public key contains one main key and three subkeys, all valid til 31.12.2019: pub xDDDC C sub x5B9E A sub x493D S sub x2BE6 E But if exporting and importing whole key, subkey x493D and subkey x2BE6 shows a (wrong) validity til 31.12.2017 only... Key xDDDC and subkey x5B9E show correct expiration date 31.12.2019. Additional hint: Expiration date of all (sub)keys has been extended end of year 2017, two additional years have been added til 31.12.2019. Former expiration date had been 31.12.2017. *Confused* How to solve this issue? Please refer to red marked dates! Export GPG (Windows): https://i.imgur.com/rgw1ZZ9.png Import R2mail2 (Android): https://i.imgur.com/lAR0vgq.png Thx + best regards, Chris ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
