Hello,
> Matthias:
> Maybe it will become a bit more complicated if it is necessary to
> keep the keyrings syncronized in both directions. This will happen at
> least if you let GPGRelay "Learn aliases from POP3"
Switch off! ;)
Serious answer:
Latest known version of GPGrelay ist 0.962, e
On 12/02/16 10:28, Matthias Mansfeld wrote:
> Maybe it will become a bit more complicated if it is necessary to
> keep the keyrings syncronized in both directions.
Hehe :). Okay, I'll humour you :).
I'd probably extract all known keys from both installations, and
propagate deletions. You also st
On 12 Feb 2016 at 9:35, gnupgpacker wrote:
> Wowh, what a comprehensive answer... :)
> THANKS!
>
> > Furthermore, pipes do generally work on Windows.
> > Wouldn't this work?
> > gpg2\gpg2.exe --export | gpg14\gpg.exe --import
>
> Similar pipes are working in Windows.
>
> > gpg2\gpg2.exe --exp
Wowh, what a comprehensive answer... :)
THANKS!
> Furthermore, pipes do generally work on Windows.
> Wouldn't this work?
> gpg2\gpg2.exe --export | gpg14\gpg.exe --import
Similar pipes are working in Windows.
> gpg2\gpg2.exe --export-ownertrust >C:\temp\exported.trust
> gpg2\gpg2.exe --output
First of all... it was established in this thread that you could not
share the key store between GnuPG 2.1 and 1.4. Why is that the case? I
can happily do that here on Linux. The only gotcha is that you don't
profit from the speed gains GnuPG 2.1 gets from the new format of the
key store. Oh, and t
Thanks for hint!
> From: Peter Lebbing [mailto:pe...@digitalbrains.com]
> Install GnuPG 1.4 alongside 2.1 and manually sync all keys from GnuPG
> 2.1 to 1.4, with for instance:
> $ gpg2 --export | gpg --import
I did get it running even on Windows:
gpg2\gpg2.exe --export --output C:\temp\exported.
On Monday 21 December 2015 11:53:13 gnupgpacker wrote:
> Thanks for hint, that would be a distress way.
> But it seems to be limited to v1.4x supported keys only.
> What will happen, if v1.4x tries to import gpg-2.x keys with elevated
> features?
The features are part of GnuPG 2.x and not part of
Thanks for hint, that would be a distress way.
But it seems to be limited to v1.4x supported keys only.
What will happen, if v1.4x tries to import gpg-2.x keys with elevated
features?
Regards, Chris
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
On 21/12/15 11:33, gnupgpacker wrote:
> So, how to work around and supply keys to GPGrelay even if using gpg version
> 2 and up?
Install GnuPG 1.4 alongside 2.1 and manually sync all keys from GnuPG
2.1 to 1.4, with for instance:
$ gpg2 --export | gpg --import
I'm not sure how large the overhead
Thanks for answer. It seems GPGrelay is not longer maintained by its
developers but is still working with a charme if gpg.exe 1.4x is used.
So, how to work around and supply keys to GPGrelay even if using gpg version
2 and up?
Regards, Chris
http://sites.inka.de/tesla/gpgrelay.html
http://is.g
On Sunday 20 December 2015 10:44:58 gnupgpacker wrote:
> But if using GPGrelay 0.9.6, while starting it displays attached error
> message. There seems to be a different key storing location or key format
> between 1.4x and 2.1x versions, isn't it?
This is not about the key format.
It appears that
11 matches
Mail list logo
