From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 5 Jan 2014 11:38:43 +0100 Message-ID: From: Rudolf Sykora To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] secstore in p9p, how to use well Topicbox-Message-UUID: ad5298fe-ead8-11e9-9d60-3106f5b1d025 so nobody uses secstored+factotum+ssh-agent on linux with p9p like I do? Thanks! Ruda On 19 December 2013 17:22, Rudolf Sykora wrote: > Hello everyone, > > already for some time I've been using secstored+factotum+ssh-agent > on linux with p9p. The machine, call it 1, runs basically all the time and > let's presume I am logged on it all the time, too. > The problem/inconvenience I've had is when I connect to this machine > via ssh and want to use the system to connect to yet another machine, > call it 2. > The best would be if all worked transparently and as soon as I manage > to log in to machine 1 I could easily proceed an use the running > ssh-agent to get me to machine 2. However, I don't know how to set this > up. > > So far I have, among other things, this in my .profile. > ---------- > secstore=localhost export secstore > NAMESPACE=/tmp/ns.ruda.0 export NAMESPACE > if [ ! -d "$NAMESPACE" ]; then > mkdir $NAMESPACE > fi > auth=localhost export auth > secstored > factotum > eval `9 ssh-agent -e` > ----------- > > > This ends with the following when I connect: > ------------------ > secstored: tcp!*!5356: Address already in use > > secstore password: > 9pserve: announce unix!/tmp/ns.ruda.0/factotum: Address already in use > factotum: post9pservice factotum: 9pserve failed > ssh-agent: announce unix!/tmp/ns.ruda.0/ssh-agent.socket: Address already in use > ------------------ > > which is not unexpected, however, whatever I tried didn't get me to > the desired effect. > > Can you suggest what I should do? > > Thank you! > Ruda Sykora