On 12/21/2015 09:28 AM, perillamint wrote:
> I'm having trouble setting up ssh auth using Ed25519 key.
When you configure your gpg-agent properly (for your key), you can use
the SSH tool of ssh-add with option -L to show your public key in SSH
format.
Thank you for using new feature. I know
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
Hello,
I'm having trouble setting up ssh auth using Ed25519 key.
I tries to convert it using gpgkey2ssh and it returns
Unsupported algorithm: 22
Is there any version of gpgkey2ssh or other tool which allows converting
ed25519 pubkey for ssh use?
___
Hi,
On Mon, 21 Dec 2015 10:28:47 +0100,
perillamint wrote:
> I'm having trouble setting up ssh auth using Ed25519 key.
>
> I tries to convert it using gpgkey2ssh and it returns
>
> Unsupported algorithm: 22
>
> Is there any version of gpgkey2ssh or other tool which allows converting
> ed25519
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
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 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
