Re: *Now* what is starting ssh-agent? — SOLVED

agents After creating the two xfconf entries per that page: xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled \ -n -t bool -s false xfconf-query -c xfce4-session -p /startup/gpg-agent/enabled \ -n -t bool -s false …and logging out and in again, no more rogue ssh-agent: $ pgrep -a

Re: *Now* what is starting ssh-agent?

On Thu, Jul 28, 2022 at 02:51:04PM -0300, Chris Mitchell wrote: > I don't appear to have a .xsession file at all: > > (Right after a "sudo updatedb") > $ locate .xsession > /home/chris/.xsession-errors > /home/chris/.xsession-errors.old > /home/chris/.xsession-startup-dump It's something yo

Re: *Now* what is starting ssh-agent?

On Thu, 28 Jul 2022 10:08:22 -0500 David Wright wrote: > On Thu 28 Jul 2022 at 10:35:07 (-0400), Greg Wooledge wrote: > I did much the same … > > > My .xsession file contains only this line concerning ssh-agent: > > > > hash ssh-agent 2>/dev/null && eval

Re: *Now* what is starting ssh-agent?

On Thu 28 Jul 2022 at 10:35:07 (-0400), Greg Wooledge wrote: > On Thu, Jul 28, 2022 at 10:34:50AM -0300, Chris Mitchell wrote: > > From the output of systemd-cgls I see that the rogue ssh-agent process > > is part of the .scope CGroup corresponding to my X login session. >

Re: *Now* what is starting ssh-agent?

On Thu, Jul 28, 2022 at 10:34:50AM -0300, Chris Mitchell wrote: > From the output of systemd-cgls I see that the rogue ssh-agent process > is part of the .scope CGroup corresponding to my X login session. > > # systemctl status session-8.scope > ● session-8.scope - Session

Re: *Now* what is starting ssh-agent?

Still picking away at this… The PIDs are, of course, a moving target, as every time I log out and back in to test a change, ssh-agent instances are getting shut down and new ones started. As of right now: * my systemd-managed ssh-agent is PID 3017 * the rogue ssh-agent is PID 7687 $ systemctl

Re: *Now* what is starting ssh-agent?

On Wed, 27 Jul 2022 11:04:49 +0200 Michael Biebl wrote: > Can you post the output of > systemd-cgls First, for context: $ systemd-cgls --user-unit ssh-agent.service Unit ssh-agent.service (/user.slice/user-1000.slice/user@1000.service/app.slice> └─3166 /usr/bin/ssh-agent -D -a /run/

Re: *Now* what is starting ssh-agent?

all users at once with "systemctl --global). A unit in this directory will supersede a same-named unit in /usr/lib/systemd/user, and may in turn be superseded on a user-by-user basis via their respective ~/.config/systemd/user directories. > PID 1 is the system instance of systemd.  Not a

Re: *Now* what is starting ssh-agent?

On Wed, Jul 27, 2022 at 09:08:59AM -0300, Chris Mitchell wrote: > On Tue, 26 Jul 2022 21:54:18 +0200 > Erwan David wrote: > > > ssh-agent is usually started by your session manager. I do not know > > wether all DE use this, but you can find it in > > > > /et

Re: *Now* what is starting ssh-agent?

On Wed, Jul 27, 2022 at 09:08:59AM -0300, Chris Mitchell wrote: > On Tue, 26 Jul 2022 21:54:18 +0200 > Erwan David wrote: > > > ssh-agent is usually started by your session manager. I do not know > > wether all DE use this, but you can find it in > > > > /et

Re: *Now* what is starting ssh-agent?

On Tue, 26 Jul 2022 21:54:18 +0200 Erwan David wrote: > ssh-agent is usually started by your session manager. I do not know > wether all DE use this, but you can find it in > > /etc/X11/Xsession.d/90x11-common_ssh-agent True. The snippet in that file is nested in a conditional,

Re: *Now* what is starting ssh-agent?

Can you post the output of systemd-cgls OpenPGP_signature Description: OpenPGP digital signature

Re: *Now* what is starting ssh-agent?

so far: > > $ env | grep -i ssh > SSH_AUTH_SOCK=/tmp/ssh-XXZAaNOY/agent.3010 > SSH_AGENT_PID=3011 > > $ ps ax | grep 3011 > 3011 ?Ss 0:00 /usr/bin/ssh-agent -s > > $ pstree -ps 3011 > systemd(1)───ssh-agent(3011) PID 1 is the system instance of syste

Re: *Now* what is starting ssh-agent?

Le 26/07/2022 à 20:40, Chris Mitchell a écrit : Hi all, I have my own systemd "user" .service unit that I like to use to start ssh-agent the way I want it started, which works fine… except for the neverending game of whack-a-mole tracking down and disabling various legacy workaroun

*Now* what is starting ssh-agent?

Hi all, I have my own systemd "user" .service unit that I like to use to start ssh-agent the way I want it started, which works fine… except for the neverending game of whack-a-mole tracking down and disabling various legacy workarounds that go ahead and start ssh-agent unasked (or

Re: ssh-agent: I want to start using on all my remote hosts

t, you should document what you do! :) Actually I do and have my current ssh set up documented. And it includes note on how to restart the ssh service. (I'm not even sure if ssh-agent was around with the original ssh.) If I recall correctly, you are setting up a server for production use,

Re: ssh-agent: I want to start using on all my remote hosts

On 6/4/2022 8:28 PM, Tom Browder wrote: On Sat, Jun 4, 2022 at 10:02 Andy Smith wrote: ... You seem to be very reboot-happy. I recommend understanding the impact of the changes you will make instead of assuming you need to reboot to make them effective. Andy. I know I'm "reboot happy," but

Re: ssh-agent: I want to start using on all my remote hosts

On Sat, Jun 4, 2022 at 10:02 Andy Smith wrote: ... You seem to be very reboot-happy. I recommend understanding the > impact of the changes you will make instead of assuming you need to > reboot to make them effective. Andy. I know I'm "reboot happy," but it's lazyness (no other users at the mom

Re: ssh-agent: I want to start using on all my remote hosts

Hello, On Fri, Jun 03, 2022 at 09:43:53AM -0500, Tom Browder wrote: > 1. Will starting the ssh-agent service interfere with my current ssh login > (using keys with NO passhrase). It only matters at the point of authentication, so existing SSH sessions will not be affected. > 2.

Re: ssh-agent: I want to start using on all my remote hosts

Hello, On Fri, Jun 03, 2022 at 09:52:26AM -0500, Tom Browder wrote: > And edit file /etc/ssh/ssh_config to change > > # ForwardAgent no > > to > > ForwardAgent yes > > Then reboot. This is a config file for the ssh client, i.e. the "ssh" command. As such it's read every time you run s

Re: How about ssh certificates (was: Re: ssh-agent: I want to start using on all my remote hosts)

Ahh, thanks Greg, I can now see those missing parts of the article -- it was NoScript, but, seeing most of the graphics in the article, somehow NoScript didn't come to mind as the cause of the problem. On Friday, June 03, 2022 02:29:45 PM Greg Wooledge wrote: > On Fri, Jun 03, 2022 at 01:16:45

Re: How about ssh certificates (was: Re: ssh-agent: I want to start using on all my remote hosts)

On Fri, Jun 3, 2022 at 13:46 wrote: > On Friday, June 03, 2022 02:16:45 PM Tom Browder wrote: > > I briefly looked at the article and didn't notice anything missing. Maybe > > if you could take some screen shots in those areas we could help. > > Thanks for the reply, and thanks, I'll do that. > >

Re: How about ssh certificates (was: Re: ssh-agent: I want to start using on all my remote hosts)

On 6/3/22 08:46, rhkra...@gmail.com wrote: On Friday, June 03, 2022 10:43:53 AM Tom Browder wrote: I have been using ssh for logging in to my remote hosts for many years, but I have NOT been using ssh-agent. I'm intentionally not addressing your specific questions. For me, your po

Re: How about ssh certificates (was: Re: ssh-agent: I want to start using on all my remote hosts)

On Fri, Jun 03, 2022 at 01:16:45PM -0500, Tom Browder wrote: > On Fri, Jun 3, 2022 at 10:46 wrote: > > > > > > One problem with that article is that it se

Re: ssh-agent: I want to start using on all my remote hosts

On 6/3/22 07:43, Tom Browder wrote: I have been using ssh for logging in to my remote hosts for many years, but I have NOT been using ssh-agent. I have checked all those hosts looking for the env var SSH_AGENT_SOCK which one website says should be defined if the ssh-agent process is running

Re: How about ssh certificates (was: Re: ssh-agent: I want to start using on all my remote hosts)

On Fri, Jun 3, 2022 at 10:46 wrote: > On Friday, June 03, 2022 10:43:53 AM Tom Browder wrote: > > I have been using ssh for logging in to my remote hosts for many years, > but > > I have NOT been using ssh-agent. > > I'm intentionally not addressing your specific que

How about ssh certificates (was: Re: ssh-agent: I want to start using on all my remote hosts)

On Friday, June 03, 2022 10:43:53 AM Tom Browder wrote: > I have been using ssh for logging in to my remote hosts for many years, but > I have NOT been using ssh-agent. I'm intentionally not addressing your specific questions. For me, your post is rather timely, because I'm digg

Re: ssh-agent: I want to start using on all my remote hosts

On Fri, Jun 3, 2022 at 09:43 Tom Browder wrote: > I have been using ssh for logging in to my remote hosts for many years, > but I have NOT been using ssh-agent. > ... And edit file /etc/ssh/ssh_config to change # ForwardAgent no to ForwardAgent yes Then reboot. -Tom

ssh-agent: I want to start using on all my remote hosts

I have been using ssh for logging in to my remote hosts for many years, but I have NOT been using ssh-agent. I have checked all those hosts looking for the env var SSH_AGENT_SOCK which one website says should be defined if the ssh-agent process is running, but none have that defined. Now I&#

SSH agent forwarding (was: weird behaviour of quotes in dash variable assignments)

aste, save. Again, the method I used should not have created any changes in the script that would affect its operation. And to date I've seen no indication that it did. I still don't know why the script was leaving the quotes in nor why it started working. You might want to consid

Re: Bug report: prog run via keyboard shortcut gets a different SSH agent?

On Tue, Sep 22, 2020 at 09:10:15AM +1000, Michael Slade wrote: > I don't know what package to assign this to so I guess I can't use the usual > bug reporting mechanism. > > I have a debian bullseye mate desktop with a custom keyboard shortcut set up > to run xterm.  I not

Bug report: prog run via keyboard shortcut gets a different SSH agent?

I don't know what package to assign this to so I guess I can't use the usual bug reporting mechanism. I have a debian bullseye mate desktop with a custom keyboard shortcut set up to run xterm.  I noticed that an ssh agent is automatically set up for it, but a different agent is

Re: Mysterious ssh-agent session

started under "(sd-pam)", so I can use my > >> systemd user service, or > > Comment out use-ssh-agent in /etc/X11/Xsession.options . > > Ah ha!  That's where it was.  Thanks! You're welcome. > >> b) configure the instance started under

Re: Mysterious ssh-agent session

On 25/04/19 6:37 PM, Reco wrote: > Hi. > > On Thu, Apr 25, 2019 at 04:58:28PM +1200, Aidan Gauland wrote: >> I need to know how to either >> a) disable the instance started under "(sd-pam)", so I can use my >> systemd user service, or &g

Re: Mysterious ssh-agent session

Hi. On Thu, Apr 25, 2019 at 04:58:28PM +1200, Aidan Gauland wrote: > I need to know how to either > a) disable the instance started under "(sd-pam)", so I can use my > systemd user service, or Comment out use-ssh-agent in /etc/X11/Xsession.options . > b)

Mysterious ssh-agent session

While troubleshooting my ssh-agent setup, I discovered that an extra ssh-agent instance was running, and I have no idea what is starting this. What I want is to have ssh-agent run as a systemd user service (following the instructions at <https://wiki.archlinux.org/index.php?title=SSH_keys&am

(SOLVED) Re: Xsession.d ssh-agent

nteresting. i have tried another way and it works for me: > > SSHAGENTARGS="-t 1h" > > ulf@deb9-desktop:~$ ps -ef|grep [s]sh-agent > ulf 4307 4221 0 21:04 ?00:00:00 /usr/bin/ssh-agent -t 1h > startxfce4 > > -s is the default, so i guess you can ignore th

Re: Xsession.d ssh-agent

On 25.11.2017 19:19, Beco wrote: > Does anyone knows why KDE won't start if I change this file... > $ head -n8 /etc/X11/Xsession.d/90x11-common_ssh-agent  > SSHAGENTARGS="-s -t 36000" remove the quotes. at the moment ssh-agent got only one (long) argument. You will

Xsession.d ssh-agent

Dear users, Does anyone knows why KDE won't start if I change this file... ```Original $ head -n8 /etc/X11/Xsession.d/90x11-common_ssh-agent # $Id: 90x11-common_ssh-agent 305 2005-07-03 18:51:43Z dnusinow $ # This file is sourced by Xsession(5), not executed. STARTSSH= SSHAGENT=/usr/bi

Re: How to not start ssh-agent with XFCE4 desktop (only gpg-agent)?

Tony Baldwin [2017-01-26 22:12:35-05] wrote: > have you tried turning ssh off in rcconf? I'm talking about not starting ssh-agent in user XFCE desktop session. I need the ssh server. -- /// Teemu Likonen - .-.. <https://keybase.io/tlikonen> // // PGP: 4E10 55DC 84E9 DFF6

Re: How to not start ssh-agent with XFCE4 desktop (only gpg-agent)?

On 01/26/2017 03:38 PM, Liam O'Toole wrote: On 2017-01-26, Teemu Likonen wrote: --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I have a Debian testing XFCE4 desktop system and use gpg-agent to manager ssh-agent protocol as well. There is "enable-ssh-s

Re: How to not start ssh-agent with XFCE4 desktop (only gpg-agent)?

On 2017-01-26, Teemu Likonen wrote: > --=-=-= > Content-Type: text/plain > Content-Transfer-Encoding: quoted-printable > > I have a Debian testing XFCE4 desktop system and use gpg-agent to > manager ssh-agent protocol as well. There is "enable-ssh-support" in > ~/.

How to not start ssh-agent with XFCE4 desktop (only gpg-agent)?

I have a Debian testing XFCE4 desktop system and use gpg-agent to manager ssh-agent protocol as well. There is "enable-ssh-support" in ~/.gnupg/gpg-agent.conf file which, among other things, makes /etc/X11/Xsession.d/90gpg-agent file set variable SSH_AUTH_SOCK so that /etc/X11/Xsessi

Re: A question about ssh-agent

gt; they are opposing goals. > > But instead of reading options from an admin file (under /etc), > it could read options from a user file (under his $HOME). > > I think there could be at least 3 values for the ssh-agent option: > 1. Always start a ssh-agent. > 2. Never start a ssh-ag

Re: A question about ssh-agent

Paul E Condon wrote: > Where in the start-up code of a system that is running ssh client is > the ssh-agent started? The (global) configuration option that determines whether or not it is to start is in /etc/X11/Xsession.options. The tool itself is started in /etc/X11/Xsession.d/90x11-comm

Re: A question about ssh-agent

goals. But instead of reading options from an admin file (under /etc), it could read options from a user file (under his $HOME). I think there could be at least 3 values for the ssh-agent option: 1. Always start a ssh-agent. 2. Never start a ssh-agent. 3. Start a ssh-agent except if the user's

Re: A question about ssh-agent

100, Sven Joachim wrote: > > > > > Nope, this is the script that starts the ssh *server*. The agent is > > > > > started in /etc/X11/Xsession.d/90x11-common_ssh-agent, sourced from > > > > > /etc/X11/Xsession (see Xsession(5). > > > > > &g

Re: A question about ssh-agent

On 20120206_132412, Bob Proulx wrote: > On the server look in /var/log/auth.log and look at the messages logged > there from the sshd [...] > I often will start up a debugging sshd and connect to it so that all > of the messages will be in the foreground. Paul E Condon replied: > Here is the de

Re: A question about ssh-agent [solved]

On 20120206_132412, Bob Proulx wrote: > Paul E Condon wrote: > > "debug1: Roaming not allowed by server" > > > > Then the process switches over to asking for a password, which I > > am trying to avoid. > > On the server look in /var/log/auth.log and look at the messages ^^

Re: A question about ssh-agent

On 20120206_132412, Bob Proulx wrote: > Paul E Condon wrote: > > "debug1: Roaming not allowed by server" > > > > Then the process switches over to asking for a password, which I > > am trying to avoid. > > On the server look in /var/log/auth.log and look at the messages > logged there from the ss

Re: A question about ssh-agent

Paul E Condon wrote: > "debug1: Roaming not allowed by server" > > Then the process switches over to asking for a password, which I > am trying to avoid. On the server look in /var/log/auth.log and look at the messages logged there from the sshd. Do you see something such as: Authentication r

Re: A question about ssh-agent

On 20120206_110312, Bob Proulx wrote: > Vincent Lefevre wrote: > > Erwan David wrote: > > > Vincent Lefevre said: > > > > But it shouldn't. It should be the user who decides whether he wants > > > > to start ssh-agent (since it is a user process), no

Re: A question about ssh-agent

arts the ssh *server*. The agent is > > > > started in /etc/X11/Xsession.d/90x11-common_ssh-agent, sourced from > > > > /etc/X11/Xsession (see Xsession(5). > > > > > > But it shouldn't. It should be the user who decides whether he wants > > &

Re: A question about ssh-agent

Vincent Lefevre wrote: > Erwan David wrote: > > Vincent Lefevre said: > > > But it shouldn't. It should be the user who decides whether he wants > > > to start ssh-agent (since it is a user process), not the admin. > > > > Not necessarily : the user u

Re: A question about ssh-agent

On 2012-02-04 09:05, Paul E Condon wrote: > It seems that it is not run when I log into a host using ssh or more > exactly its pid is not exported to an ssh login process. Could I add > something to the .profile script? If this is possible, it surely > has been thought of before me and better and w

Re: A question about ssh-agent

d in /etc/X11/Xsession.d/90x11-common_ssh-agent, sourced from > > > /etc/X11/Xsession (see Xsession(5). > > > > But it shouldn't. It should be the user who decides whether he wants > > to start ssh-agent (since it is a user process), not the admin. > > Not necessari

Re: A question about ssh-agent

ssion (see Xsession(5). > > But it shouldn't. It should be the user who decides whether he wants > to start ssh-agent (since it is a user process), not the admin. Not necessarily : the user uses it or not through ssh-add. -- To UNSUBSCRIBE, email to debian-user-requ...@

Re: A question about ssh-agent

ether he wants to start ssh-agent (since it is a user process), not the admin. -- Vincent Lefèvre - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UN

Re: A question about ssh-agent

ded connection. An attacker cannot obtain key material from the agent, however they can perform operations on the keys that enable them to authenticate using the identities loaded into the agent. Let me interpret. You sit on your desktop. You log into a remo

Re: A question about ssh-agent

On 20120204_093544, Sven Joachim wrote: > On 2012-02-04 09:09 +0100, Scott Ferguson wrote: > > > On 04/02/12 19:05, Paul E Condon wrote: > >> > >> Where in the start-up code of a system that is running ssh client is > >> the ssh-agent started? It

Re: A question about ssh-agent

On Sat, 04 Feb 2012 01:05:47 -0700, Paul E Condon wrote: > Some might think I have no business wanting to know the answer to this > question, but bare with me: > > Where in the start-up code of a system that is running ssh client is the > ssh-agent started? It has got to be early

Re: A question about ssh-agent

On Sb, 04 feb 12, 01:05:47, Paul E Condon wrote: > It seems that it is not run when I log into a host using ssh or more > exactly its pid is not exported to an ssh login process. Could I add > something to the .profile script? Maybe 'ForwardAgent' is what you are looking for. See ssh(1) and ssh

Re: A question about ssh-agent

On 04/02/12 19:35, Sven Joachim wrote: > On 2012-02-04 09:09 +0100, Scott Ferguson wrote: > >> On 04/02/12 19:05, Paul E Condon wrote: >>> >>> Where in the start-up code of a system that is running ssh client is >>> the ssh-agent started? >>> It

Re: A question about ssh-agent

On 2012-02-04 09:09 +0100, Scott Ferguson wrote: > On 04/02/12 19:05, Paul E Condon wrote: >> >> Where in the start-up code of a system that is running ssh client is >> the ssh-agent started? It has got to be early in the process, but >> where? And what exactly is do

Re: A question about ssh-agent

is running ssh client is > the ssh-agent started? It has got to be early in the process, but > where? And what exactly is done? Should I be able to see it in an > init.d script? It is a daemon, but it is only needed to support an > add-on feature of as ssh client so it should be pa

A question about ssh-agent

Some might think I have no business wanting to know the answer to this question, but bare with me: Where in the start-up code of a system that is running ssh client is the ssh-agent started? It has got to be early in the process, but where? And what exactly is done? Should I be able to see it in

ssh-agent started but environment not set

Hi On my testing box, the ssh-agent gets started by settings in /etc/X11/Xsession.options. This works as expected. However, the environment is not set when I start Konsole (yes, KDE user). IMO this should work out of the box without my patching whatever, but maybe I missed something? TIA, ändu

ssh-agent and TMPDIR

Hello List, I have just built and installed openssh 1:5.8p1-3 from sid on my squeeze box in order to getssh-agent to honour $TMPDIR. In /usr/share/doc/openssh-server/changelog.Debian.gz I read: - ssh(1)/ssh-agent(1): honour $TMPDIR for client xauth and ssh-agent temporary directories

Re: ssh-agent, keychain, xsession bash_profile scripting

On Friday 15 January 2010 14:33:50 T o n g wrote: > On Fri, 15 Jan 2010 11:31:08 -0600, Boyd Stephen Smith Jr. wrote: > > I use this for starting the daemons or connecting to existing daemons by > > setting environment variables in the current shell: eval > > "$(/usr/bin/keychain --eval --quiet --i

Re: ssh-agent, keychain, xsession bash_profile scripting

ollowing different >>>> examples off the web, but can't sort it out and keep getting the old >>>> >>>> "Could not open a connection to your authentication agent." >>>> >>>> from ssh-add, and nothing but inaction from keycha

Re: ssh-agent, keychain, xsession bash_profile scripting

#x27;t sort it out and keep getting the old >>> >>> "Could not open a connection to your authentication agent." >>> >>> from ssh-add, and nothing but inaction from keychain. >>> >>> I know everything has to run as a child of ssh-agent to g

Re: ssh-agent, keychain, xsession bash_profile scripting

Thanks Boyd. On Fri, 15 Jan 2010 11:31:08 -0600, Boyd Stephen Smith Jr. wrote: > I use this for starting the daemons or connecting to existing daemons by > setting environment variables in the current shell: eval > "$(/usr/bin/keychain --eval --quiet --inherit any-once --stop others -- > noask --

Re: ssh-agent, keychain, xsession bash_profile scripting

thentication agent." > > from ssh-add, and nothing but inaction from keychain. > > I know everything has to run as a child of ssh-agent to gain access > to its envvars, but I don't how to achieve this. I used to have in $HOME/.bashrc: | AGENT_INFO_FILE=$HOME/.ssh/ssh-age

Re: ssh-agent, keychain, xsession bash_profile scripting

In <4b5092d0.60...@cyberspaceroad.com>, Adam Hardy wrote: >keychain id_rsa in my .bash_profile doesn't work, I still have to give ssh > my password for the private key when I use ssh. I use this for starting the daemons or connecting to existing daemons by setting environment variables in the cur

Re: ssh-agent, keychain, xsession bash_profile scripting

; from ssh-add, and nothing but inaction from keychain. I know everything has to run as a child of ssh-agent to gain access to its envvars, but I don't how to achieve this. keychain id_rsa in my .bash_profile doesn't work, I still have to give ssh my password for the private key when I

Re: ssh-agent, keychain, xsession bash_profile scripting

ssh-add, and nothing but inaction from keychain. > > I know everything has to run as a child of ssh-agent to gain access to its > envvars, but I don't how to achieve this. > > keychain id_rsa in my .bash_profile doesn't work, I still have to give ssh my > password for

ssh-agent, keychain, xsession bash_profile scripting

hing has to run as a child of ssh-agent to gain access to its envvars, but I don't how to achieve this. keychain id_rsa in my .bash_profile doesn't work, I still have to give ssh my password for the private key when I use ssh. I guess I should be setting up the envvars in my bash env

ssh-agent / gnome keyring / gpg-agent issue

s and eval `ssh-agent`, then ssh-add, everything works as expected, so it's whichever agent process is started as part of my GNOME session that is faulty. The process tree looks something like root /usr/sbin/gdm root \_ /usr/sbin/gdm root \_ /usr/bin/X :0 -audit 0 -auth /var/lib/gd

Re: ssh-agent: multikey

Hello List, thanks for your replies, Jerome Todd A. Jacobs wrote: On Mon, Apr 06, 2009 at 12:31:33AM +0800, Jerome BENOIT wrote: curenlty, during Gomme sessions on my Lenny box, the ssh-agent stores by default only the two default keys: is there a (Debian) way to get the ssh-agent to store a

Re: ssh-agent: multikey

On Mon, Apr 06, 2009 at 12:31:33AM +0800, Jerome BENOIT wrote: > curenlty, during Gomme sessions on my Lenny box, the ssh-agent stores > by default only the two default keys: is there a (Debian) way to get > the ssh-agent to store a larger number of keys by default ? There may be a b

Re: ssh-agent: multikey

On Mon,06.Apr.09, 15:54:28, Jerome BENOIT wrote: > In fact this is not really ssh-agent issue, but rather a gnome-keyring > issue: > as far I can understand, at start gnome start a ssh-agent with the two default > keys id_[rd]sa . I would like to add more keys. The dedicated tool fo

Re: ssh-agent: multikey

Hello List, Andrei Popescu wrote: On Mon,06.Apr.09, 00:31:33, Jerome BENOIT wrote: Hello List, curenlty, during Gomme sessions on my Lenny box, the ssh-agent stores by default only the two default keys: is there a (Debian) way to get the ssh-agent to store a larger number of keys by default

Re: ssh-agent: multikey

On Mon,06.Apr.09, 00:31:33, Jerome BENOIT wrote: > Hello List, > > curenlty, during Gomme sessions on my Lenny box, > the ssh-agent stores by default only the two default keys: > is there a (Debian) way to get the ssh-agent to store > a larger number of keys by default ? A quic

ssh-agent: multikey

Hello List, curenlty, during Gomme sessions on my Lenny box, the ssh-agent stores by default only the two default keys: is there a (Debian) way to get the ssh-agent to store a larger number of keys by default ? Thanks in advance, Jerome -- Jerome BENOIT jgmbenoit_at_mailsnare_dot_net -- To

Re: ssh-agent without graphical display manager? how?

On Mon, 2009-01-05 at 16:58 -0600, Boyd Stephen Smith Jr. wrote: > On Monday 2009 January 05 16:31:35 Richard Hector wrote: > > Or can you just forward your existing agent when you connect (ssh -A), > > then run ssh-add on the remote machine (the one with the private key on > > it)? > > Don't do t

Re: ssh-agent without graphical display manager? how?

On Monday 2009 January 05 16:31:35 Richard Hector wrote: > Or can you just forward your existing agent when you connect (ssh -A), > then run ssh-add on the remote machine (the one with the private key on > it)? Don't do this unless you trust root on the *remote* machine. While the forwarding is

Re: ssh-agent without graphical display manager? how?

ssh. But when I log in this way, it appears that ssh-agent is > not started, and consequently, I cannot use ssh-add on it. I can, of > course, use ssh-add on my desktop computer, but that is not where the > private key for the backup server is stored. Has anyone confronted > th

Re: ssh-agent without graphical display manager? how?

On 2009-01-04T17:16:22, Paul E Condon wrote: > A puzzle: I don't have either .login or .bash_login in my ~ directory. > I do have .profile > Is there any difference? Yes. .login / .bash_login are executed for a login shell (in your case, first time only), while .profile / .bashrc are executed

Re: ssh-agent without graphical display manager? how?

t; > > > As far as I recall the manpage of ssh-agent has generic instructions on > > how to start it. > > > > The man page instructions assume that one is running a graphical display > manager, and I am not. This is precisely why I need help, IMHO. from memory the

Re: ssh-agent without graphical display manager? how?

On Sun, Jan 04, 2009 at 02:52:58PM -0500, Allan Wind wrote: > You want to run ssh-agent in the parent login shell, so later shells > inherit the SSH_AGENT_ID and SSH_AGENT_PID environment variables. If > you use bash, then .login or .bash_login should contain something like: >

Re: ssh-agent without graphical display manager? how? SOLVED Thanks

On Sun, Jan 04, 2009 at 11:07:22PM +, Tzafrir Cohen wrote: > On Sun, Jan 04, 2009 at 08:55:27AM -0700, Paul E Condon wrote: > > I'm in the process of converting from nfs to sshfs on my home-grown ... A lot of good answers. I'll need some time to see which works for me. You all have gotten me

Re: ssh-agent without graphical display manager? how?

; using ssh. But when I log in this way, it appears that ssh-agent is > not started, and consequently, I cannot use ssh-add on it. I can, of > course, use ssh-add on my desktop computer, but that is not where the > private key for the backup server is stored. Has anyone confronted > th

Re: ssh-agent without graphical display manager? how?

On Sun,04.Jan.09, 12:18:32, Paul E Condon wrote: > The man page instructions assume that one is running a graphical display > manager, and I am not. This is precisely why I need help, IMHO. I admit it's cryptic, but it's there: ,[ ssh-agent(1) ] | There are two main ways

Re: ssh-agent without graphical display manager? how?

On 2009-01-04 14:52:58 -0500, Allan Wind wrote: > You want to run ssh-agent in the parent login shell, so later shells > inherit the SSH_AGENT_ID and SSH_AGENT_PID environment variables. Only sub-shells will inherit them. If you start a second SSH session to the remote host, it will not i

Re: ssh-agent without graphical display manager? how?

On 2009-01-04 12:18:32 -0700, Paul E Condon wrote: > The man page instructions assume that one is running a graphical display > manager, and I am not. This is precisely why I need help, IMHO. I use ssh (and ssh-agent) to jump from one machine to another, most often without X forwarding, an

Re: ssh-agent without graphical display manager? how?

; using ssh. But when I log in this way, it appears that ssh-agent is > not started, and consequently, I cannot use ssh-add on it. I can, of > course, use ssh-add on my desktop computer, but that is not where the > private key for the backup server is stored. Has anyone confronted > th

Re: ssh-agent without graphical display manager? how?

You want to run ssh-agent in the parent login shell, so later shells inherit the SSH_AGENT_ID and SSH_AGENT_PID environment variables. If you use bash, then .login or .bash_login should contain something like: eval `ssh-agent` /Allan -- Allan Wind Life Integrity, LLC http

Re: ssh-agent without graphical display manager? how?

On Sunday 04 January 2009, Paul E Condon wrote about 'ssh-agent without graphical display manager? how?': >I control it mostly by logging into it >using ssh. But when I log in this way, it appears that ssh-agent is >not started. Has anyone confronted >this situation and

Re: ssh-agent without graphical display manager? how?

On Sun, Jan 04, 2009 at 08:38:46PM +0200, Andrei Popescu wrote: > On Sun,04.Jan.09, 08:55:27, Paul E Condon wrote: > > I'm in the process of converting from nfs to sshfs on my home-grown ... > > As far as I recall the manpage of ssh-agent has generic instructions on > h

Re: ssh-agent without graphical display manager? how?

But when I log in this way, it appears that ssh-agent is > not started, and consequently, I cannot use ssh-add on it. I can, of > course, use ssh-add on my desktop computer, but that is not where the > private key for the backup server is stored. Has anyone confronted > this situat

  1   2   >