On 16/07/18 23:35, Chris Coutinho wrote:
> Although some sources note the potential security holes of
> using this method, it works great for my use case
Well, yes, even the man page warns about the security implications.
There's a reason I said "it's quite a while back" :-). I try to avoid
it.
Thanks for your reply Peter, the ForwardAgent flag is exactly what I was
looking for. Although some sources note the potential security holes of
using this method, it works great for my use case
https://heipei.github.io/2015/02/26/SSH-Agent-Forwarding-considered-harmful/
Regards,
Chris
On Jul
Hi,
as far as I know this is independently of GnuPG and just depends on the
configuration of the SSH client. Maybe have a search for "Stepping
Stone" configuration or alike. This should use your local keys.
For Example (based on something I used in the past):
Host thirdMachine-alias
Host
On 16/07/18 11:36, Chris Coutinho wrote:
> I have a few remotes where I would also like to forward my ssh-agent so
> that I can make a third connection to a remote machine using my local
> ssh-agent (through gpg-agent). Specifically, I'm trying to ssh into a
> FreeBSD remote, and from there connect
On 16/07/18 12:36, Chris Coutinho wrote:
> I have a few remotes where I would also like to forward my ssh-agent
Have you played with OpenSSH's ForwardAgent option or its -A command
line argument counterpart? I'm fairly sure I had success with it in the
past with an authentication key on an OpenPGP
Hello,
I use the ssh-agent functionality of gnupg (version 2.2.8) to handle
connecting to remote hosts, which works great. I'm also able to forward
my gpg-agent to remote machines to e.g. decrypt files using the
`RemoteForward` flag in my ~/.ssh/config:
Host myremote
RemoteForward /p
