Re: Tool: Sherpa: (Re: Import keys from .gnupg folder)

2018-01-09 Thread Daniel Kahn Gillmor 
On Tue 2018-01-09 08:36:25 +0100, Bernhard Reiter wrote:
> Am Montag 08 Januar 2018 17:38:33 schrieb Daniel Kahn Gillmor:
>> debian's GnuPG packaging supplies
>> /usr/bin/migrate-pubring-from-classic-gpg which should handle the full
>> migration in a safe way and leave the user without any legacy
>> pubring.gpg.
>
> Feel free to add it to the wiki.gnupg.org. :)
> (Where is the source code for the tool if I would want to use it outside of 
> the Debian package?)

it's a shell script -- the tool is the source :)

at the moment, you can find it at
https://anonscm.debian.org/git/pkg-gnupg/gnupg2.git/tree/debian/migrate-pubring-from-classic-gpg

though that's likely to migrate to salsa.debian.org soon, as alioth (the
machine that hosts anonscm.debian.org) is going away this year.

--dkg


signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Tool: Sherpa: (Re: Import keys from .gnupg folder)

2018-01-08 Thread Bernhard Reiter 
Am Montag 08 Januar 2018 17:38:33 schrieb Daniel Kahn Gillmor:
> debian's GnuPG packaging supplies
> /usr/bin/migrate-pubring-from-classic-gpg which should handle the full
> migration in a safe way and leave the user without any legacy
> pubring.gpg.

Feel free to add it to the wiki.gnupg.org. :)
(Where is the source code for the tool if I would want to use it outside of 
the Debian package?)

Bernhard


-- 
www.intevation.de/~bernhard   +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


signature.asc
Description: This is a digitally signed message part.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Tool: Sherpa: (Re: Import keys from .gnupg folder)

2018-01-08 Thread Daniel Kahn Gillmor 
On Mon 2018-01-08 11:35:33 +0100, Bernhard Reiter wrote:
> Am Sonntag 07 Januar 2018 17:39:39 schrieb Robert J. Hansen:
>> Obligatory drum beating: I wrote a tool, Sherpa, to help ease migration
>> between different GnuPG versions.
>>
>> https://rjhansen.github.io/sherpa/
>
> Mentioned in the wiki now, at
>   https://wiki.gnupg.org/Tools
>
> Would be interesting to know what the experiences of other people are
> (and why sherpa is not considered ready for regular users yet.)

note that there are two things that could/should be migrated when moving
to 2.1.x or later (the "modern" development branch of GnuPG):

 * secret keys (from secring.gpg to private-keys-v1.d/*.key --should
   happen automatically)
   
 * public keys (from pubring.gpg to pubring.kbx)

public key migration currently does not happen automatically because the
"modern" branch can use both pubring.gpg and pubring.kbx, and there is
an (i believe misguided) desire to facilitate co-installation of the
"classic" branch with the "modern" branch.

debian's GnuPG packaging supplies
/usr/bin/migrate-pubring-from-classic-gpg which should handle the full
migration in a safe way and leave the user without any legacy
pubring.gpg.

Regards,

  --dkg

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Tool: Sherpa: (Re: Import keys from .gnupg folder)

2018-01-08 Thread Robert J. Hansen 
> Would be interesting to know what the experiences of other people are
> (and why sherpa is not considered ready for regular users yet.)

Inadequate testing.  It's in a "it works for the core dev and two other
people" stage, which to me screams not ready for the real world.



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Tool: Sherpa: (Re: Import keys from .gnupg folder)

2018-01-08 Thread Bernhard Reiter 


Am Sonntag 07 Januar 2018 17:39:39 schrieb Robert J. Hansen:
> Obligatory drum beating: I wrote a tool, Sherpa, to help ease migration
> between different GnuPG versions.
>
> https://rjhansen.github.io/sherpa/

Mentioned in the wiki now, at
  https://wiki.gnupg.org/Tools

Would be interesting to know what the experiences of other people are
(and why sherpa is not considered ready for regular users yet.)

(Adding info to the wiki is always appreciated, we are a community with a lot 
of people and spread out knowledge.)

Best Regards,
Bernhard

-- 
www.intevation.de/~bernhard   +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


signature.asc
Description: This is a digitally signed message part.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Import keys from .gnupg folder

2018-01-07 Thread Robert J. Hansen 
> Yes, that is possible. However, you could also just copy the directory
> in your new home directory. Upgrading from 2.0 to 2.2 will do the right
> thing.

Obligatory drum beating: I wrote a tool, Sherpa, to help ease migration
between different GnuPG versions.

https://rjhansen.github.io/sherpa/



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Import keys from .gnupg folder

2018-01-07 Thread Teemu Likonen 
Michael Singh [2018-01-05 22:39:42-08] wrote:

> I was a bit ignorant to the nuances of importing/exporting GPG keys, and
> as a result I simply copied the.gnupg folder from my home directory and
> wiped my hard drive. Is it possible to import these keys on another
> installation from this folder? The public key is on a public key-server,
> and I have the private keys in the folder.
>
> The version of GPG on RHEL7.4 is 2.0.22, while Arch happens to be on
> 2.2.4-1. Would this be problematic?

Gpg 2.0 uses secring.gpg file for its secret keyring. Gpg 2.1 uses
private-keys-v1.d directory for secret keyring but 2.1 automatically
converts the old secring.gpg to the new format.

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Import keys from .gnupg folder

2018-01-07 Thread Peter Lebbing 
On 06/01/18 07:39, Michael Singh wrote:
> Is it possible to import these keys on another
> installation from this folder?

Yes, that is possible. However, you could also just copy the directory
in your new home directory. Upgrading from 2.0 to 2.2 will do the right
thing.

If you already have a .gnupg dir there, but you didn't do anything
worthwhile with GnuPG yet, you can just move that to a backup location,
and throw away the backup once you're confident everything works.

However, it is good practice to remove the file "random_seed". This file
should be specific to a single location and not shared.

HTH,

Peter.

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Import keys from .gnupg folder

2018-01-07 Thread Michael Singh 

Hi all,

I was a bit ignorant to the nuances of importing/exporting GPG keys, and 
as a result I simply copied the.gnupg folder from my home directory and 
wiped my hard drive. Is it possible to import these keys on another 
installation from this folder? The public key is on a public key-server, 
and I have the private keys in the folder.


The version of GPG on RHEL7.4 is 2.0.22, while Arch happens to be on 
2.2.4-1. Would this be problematic?


--
Michael Singh

M: 914-266-0601
W: www.wadadli.me
F: 5E0E FD46 4592 1682 A4B6 5F62 761E 4940 A177 3B38


Sent via Migadu.com, world's easiest email hosting

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users