On Thu, 30 Mar 2017, Paul Heinlein wrote:
> If you want your agent available in runlevel 3, adding it to the startx
> invocation obviously won't do any good. (Similarly, if you exit your X
> window manager temporarily, your terminal won't have access to the agent.)
>
> If you do most of your SSH
On Thu, 30 Mar 2017, Rich Shepard wrote:
> On Thu, 30 Mar 2017, Paul Heinlein wrote:
>
>> This, IMO, is the way to do this. Wrap your entire X session in
>> ssh-agent. Even the Mac exports ssh-agent to all its terminals.
>
> Paul,
>
> What is the difference between adding ssh-agent to the
you could use the gnome-keyring and add the decryption key for an SSH
key in it. Then simply unlock that keychain upon boot.
On 03/30/2017 01:12 PM, Rich Shepard wrote:
>My laptops are not always on. When I do fire up one and want to exchange
> files with the desktop each transaction
On Thu, 30 Mar 2017, Rich Shepard wrote:
> virtual tables while the latter makes it present in consoles and vts.
^^
Oops! That should be terminals, not tables.
Rich
___
PLUG mailing list
PLUG@lists.pdxlinux.org
On Thu, 30 Mar 2017, Robert Citek wrote:
> You can try the manual way by typing these two commands after you have
> logged in to your account:
>
> exec ssh-agent bash --login
> ssh-add ~/.ssh/*_rsa
Robert,
This makes the test sooner rather than later. :-)
Thanks,
Rich
On Thu, 30 Mar 2017, Steve Dum wrote:
> If you're using neither of these window management systems, there is a
> tool called Keychain, that provides the same sort of service. You invoke
> keychain in your .login (or other appropriate startup script) with a mode
> setting and list of public keys,
On Thu, 30 Mar 2017, Paul Heinlein wrote:
> This, IMO, is the way to do this. Wrap your entire X session in
> ssh-agent. Even the Mac exports ssh-agent to all its terminals.
Paul,
What is the difference between adding ssh-agent to the startx alias and
having it in ~/.bash_profile? Seems to
On Thu, Mar 30, 2017 at 3:04 PM, Rich Shepard wrote:
> On Thu, 30 Mar 2017, Robert Citek wrote:
>
>> This is a simplified version of what I have in my ~/.profile :
>>
>> [ -z "$SSH_AGENT_PID" ] && tty -s && exec ssh-agent bash --login
>> [ -n "$SSH_AGENT_PID" ] && tty -s
If you are using GNOME or KDE they both have mechanisms to add a ssh
agent when you log in. They maintain a locked cache of your ssh keys.
The first time you open a ssh session, a popup will ask for your passwd
to the cache, and then for the duration of your login session the agent
has your
On Thu, 30 Mar 2017, Rich Shepard wrote:
> On Thu, 30 Mar 2017, chris (fool) mccraw wrote:
>
>> I've had good luck making sure that my entire session runs under ssh-agent
>> - before the days of ubiquitous desktop managers and login panels, I just
>> ran 'ssh-agent startx'. Then one 'ssh-add'
On Thu, 30 Mar 2017, chris (fool) mccraw wrote:
> I've had good luck making sure that my entire session runs under ssh-agent
> - before the days of ubiquitous desktop managers and login panels, I just
> ran 'ssh-agent startx'. Then one 'ssh-add' was good for the duration of my
> xwin session,
On Thu, 30 Mar 2017, Galen Seitz wrote:
> I don't recall the details, but I believe I'm using some part of the GNOME
> keyring manager here. After logging in, the first attempt to use ssh will
> pop up a window asking for my passphrase. All subsequent use of ssh does
> not require the passphrase.
On Thu, 30 Mar 2017, Robert Citek wrote:
> This is a simplified version of what I have in my ~/.profile :
>
> [ -z "$SSH_AGENT_PID" ] && tty -s && exec ssh-agent bash --login
> [ -n "$SSH_AGENT_PID" ] && tty -s && {
> echo -e "\nAdding keys to ssh-agent ..."
> ssh-add ~/.ssh/*_rsa
> echo
>
I've had good luck making sure that my entire session runs under ssh-agent
- before the days of ubiquitous desktop managers and login panels, I just
ran 'ssh-agent startx'. Then one 'ssh-add' was good for the duration of my
xwin session, including suspends. I think modern login panels/managers
On Thu, Mar 30, 2017 at 1:28 PM, Rich Shepard wrote:
> On Thu, 30 Mar 2017, Rich Shepard wrote:
>
>> My laptops are not always on. When I do fire up one and want to exchange
>> files with the desktop each transaction requires my typing my passphrase.
>> Can I add
On 03/30/17 13:12, Rich Shepard wrote:
>My laptops are not always on. When I do fire up one and want to exchange
> files with the desktop each transaction requires my typing my passphrase.
> Can I add ssh-agent and ssh-add to ~/.bash_profile so I need type the
> passphrase only once after
On Thu, 30 Mar 2017, wes wrote:
> well... at the risk of getting bashed by security fans, you could
> always... not have a passphrase on your ssh key?
wes,
B-zzz-zzzt. Bash, csh, zsh makes no difference. I won't go naked into
the 'Net.
Rich
On Thu, Mar 30, 2017 at 1:28 PM, Rich Shepard
wrote:
> On Thu, 30 Mar 2017, Rich Shepard wrote:
>
> > My laptops are not always on. When I do fire up one and want to exchange
> > files with the desktop each transaction requires my typing my passphrase.
> > Can I add
On Thu, 30 Mar 2017, Rich Shepard wrote:
> My laptops are not always on. When I do fire up one and want to exchange
> files with the desktop each transaction requires my typing my passphrase.
> Can I add ssh-agent and ssh-add to ~/.bash_profile so I need type the
> passphrase only once after
My laptops are not always on. When I do fire up one and want to exchange
files with the desktop each transaction requires my typing my passphrase.
Can I add ssh-agent and ssh-add to ~/.bash_profile so I need type the
passphrase only once after booting a host?
Rich
20 matches
Mail list logo