Hi All,
I am using the following command
gpg --batch --passphrase-fd n and it stops popup which asks for the
passphrase. but when I run this command on window server 12 it's not
working its always show popup for the passphrase. can someone please help
me how can I stop popup on window server 12.
On 26/03/2019 09:16, Werner Koch wrote:
> This lists all keys allowed for ssh with its keygrip (1234. and the
> corresponding ssh fingerprint (SHA256:PTJI). Details as usual by using
> 'help keyinfo'.
Right, yes, the comment lines in sshcontrol are also really helpful for
keys in sshcontrol.
I
On Mon, 25 Mar 2019 16:02, pe...@digitalbrains.com said:
> But something more user friendly to match SSH fingerprint and keygrip
> could be beneficial. I'm not sure what that would look like and neither
You can build a script based on this:
$ gpg-connect-agent 'keyinfo --ssh-list --ssh-fpr'
On 25/03/2019 15:45, Werner Koch wrote:
> That is on purpose: gpg-agent stores the key permanently and thus it
> makes no sense to add and remove it regularly.
It might also be "slightly annoying" to remove key material which is
also in use for other purposes :-). You remove an SSH key, and
On Sat, 23 Mar 2019 16:19, pe...@digitalbrains.com said:
> because ssh-add -d doesn't work with gpg-agent. Well, not with the
> version in Debian stretch anyway, I reserve the right to be ignorant
That is on purpose: gpg-agent stores the key permanently and thus it
makes no sense to add and
On 23/03/2019 13:39, Brian Exelbierd wrote:
> How did you import this key?
If your OpenSSH private key is .ssh/id_ed25519, and you are running
gpg-agent as your SSH agent, it's a matter of:
$ ssh-add ~/.ssh/id_ed25519
Any comment on the private key that was already there (presumably
through
Hi Peter,
Your help has been amazing and very useful. I was re-reading this answer and I
noticed the comments below:
On Sat, Mar 16, 2019, at 11:12 AM, Peter Lebbing wrote:
> (By the way, as you can see in the ssh-keygen output, my key actually
> has a comment field in the gpg-agent. It was
On 17/03/2019 13:17, Brian Exelbierd wrote:
> Having done no code examination, I feel like this is where the
> identity information for subkeys comes into play. I presume the SSH
> request would pass the value of the identity file to the gpg-agent.
> This is probably 100% wrong though/
30%
On Sun, Mar 17, 2019, at 1:12 PM, Peter Lebbing wrote:
> On 17/03/2019 12:45, Brian Exelbierd wrote:
> > There is no longer an identityfile to use in the .ssh/config file
> > which means all auth keys are tried with all hosts. I have multiple
> > auth keys and the hosts give up after 2 or 3
On 17/03/2019 12:45, Brian Exelbierd wrote:
> There is no longer an identityfile to use in the .ssh/config file
> which means all auth keys are tried with all hosts. I have multiple
> auth keys and the hosts give up after 2 or 3 failures. How can I get
> the right key served to the right host
On Sat, Mar 16, 2019, at 11:12 AM, Peter Lebbing wrote:
> Hi Brian,
>
> On 15/03/2019 23:28, Brian Exelbierd wrote:> Hi,
> > Either way, I am unsure how to identify which subkey is which SSH key.
>
> Provided the auth keys are in your .gnupg/sshcontrol file, the following
> will help:
>
>
Hi,
On 16/03/2019 14:22, Dirk Gottschalk wrote:
> In the output from --export-ssh-key is also a comment field. This
> fieldd, in my case shows: openpgp:0xF852DAEE
Yes, but it is only added by the --export-ssh-key command and has a
fixed form. Instead, for my keys, which by the way are not part
Hi.
Am Samstag, den 16.03.2019, 11:11 +0100 schrieb Peter Lebbing:
> (By the way, as you can see in the ssh-keygen output, my key actually
> has a comment field in the gpg-agent. It was imported from an on-disk
> OpenSSH file, that's where it came from. I don't know a way to have a
> comment
On 16/03/2019 11:11, Wolfgang Traylor wrote:
> $ gpg2 --export-ssh-key
Actually, if you want a specific subkey, you need to append a ! to the
key ID (probably need to quote it as well for the shell, \! ).
Otherwise, GnuPG will use key selection rules to take the latest
authentication subkey from
Hi Brian,
On 15/03/2019 23:28, Brian Exelbierd wrote:> Hi,
> Either way, I am unsure how to identify which subkey is which SSH key.
Provided the auth keys are in your .gnupg/sshcontrol file, the following
will help:
--8<---cut here---start->8---
$ ssh-add -L
> I am unsure how to identify which subkey is which SSH key.
You can export your GPG subkey for SSH and compare with the `ssh-add -L` output:
$ gpg2 --export-ssh-key
This gives you the SSH-formatted subkey which will match one of your lines from
`ssh-add -L`.
Note that the comments (anything
On 3/15/2019 11:28 PM, Brian Exelbierd wrote:
> Hi,
>
> I would like to eliminate my SSH keys and consolidate my existing keys into
> my gpg key. I can do this by either importing my existing keys (easier) or
> creating new authentication subkeys.
>
> Either way, I am unsure how to identify
Hi,
I would like to eliminate my SSH keys and consolidate my existing keys into my
gpg key. I can do this by either importing my existing keys (easier) or
creating new authentication subkeys.
Either way, I am unsure how to identify which subkey is which SSH key. I
created a test key, below,
18 matches
Mail list logo
