On Jul 20, 2019, at 1:35 PM, Rich Shepard wrote:
>
> On Sat, 20 Jul 2019, Louis Kowolowski wrote:
>
>> If you’re logging in to a *nix box with X, you might check out something
>> like https://github.com/sigmavirus24/x11-ssh-askpass. This would prompt
>> you at login and make the keys available
On Sat, 20 Jul 2019, Louis Kowolowski wrote:
If you’re logging in to a *nix box with X, you might check out something
like https://github.com/sigmavirus24/x11-ssh-askpass. This would prompt
you at login and make the keys available for any terminal/shell session
that is spawned from your X
On Jul 20, 2019, at 7:49 AM, Rich Shepard wrote:
>
> On Fri, 19 Jul 2019, Louis Kowolowski wrote:
>
>> If you reboot, you’ll have to re-ssh-add.
>
> Thanks, Louis. That't the part I forgot.
>
If you’re logging in to a *nix box with X, you might check out something like
On Fri, 19 Jul 2019, Rich Shepard wrote:
On Fri, 19 Jul 2019, Paul Heinlein wrote:
Your local ssh-agent should do the trick. Going out on a limb, I'm
going to suggest that the fix should be easy.
Paul,
I thoght ssh-agent was the tool.
It is. On a Linux machine ssh-agent is usually run
On Fri, 19 Jul 2019, King Beowulf wrote:
I only use ssh and associated tools with keys when remoting in from the
outside. On my internal LAN, I find NFS simpler and more versatile. One
box exports several directories via NFS, users/no root. The other boxes
then just mount those as users and its
On Fri, 19 Jul 2019, Louis Kowolowski wrote:
If you reboot, you’ll have to re-ssh-add.
Thanks, Louis. That't the part I forgot.
Regards,
Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
On 7/19/19 2:52 PM, Rich Shepard wrote:
> As I transition from the old server/workstation I frequently copy files and
> directories using scp. Each time I need to enter my pass phrase and I
> thought that ssh-agent eliminated that need. Apparently not. Since all
> transfers are in the LAN and not
For each login session (it works as env), you need to ’ssh-add’. You can test
this with ’ssh-add -l’ and if you see keys, then you’re OK on the local host.
If you reboot, you’ll have to re-ssh-add.
> On Jul 19, 2019, at 6:21 PM, Rich Shepard wrote:
>
> On Fri, 19 Jul 2019, Paul Heinlein
Adding to what Paul said,
you should also be able to run ’ssh-add -l’ on the destination host and see the
same key. If not, you aren’t successfully forwarding the agent.
You may wish to try things manually, with a ssh -A ${host}, alternatively, you
could add ' ForwardAgent yes’ to your
On Fri, 19 Jul 2019, Paul Heinlein wrote:
Your local ssh-agent should do the trick. Going out on a limb, I'm going to
suggest that the fix should be easy.
Paul,
I thoght ssh-agent was the tool.
And, I had used it with ssh locally without the pass phrase, but not before
with scp.
On
On Fri, 19 Jul 2019, Rich Shepard wrote:
As I transition from the old server/workstation I frequently copy
files and directories using scp. Each time I need to enter my pass
phrase and I thought that ssh-agent eliminated that need. Apparently
not. Since all transfers are in the LAN and not
As I transition from the old server/workstation I frequently copy files and
directories using scp. Each time I need to enter my pass phrase and I
thought that ssh-agent eliminated that need. Apparently not. Since all
transfers are in the LAN and not exposed to the outside world, which tool
allows
12 matches
Mail list logo
