Groups > comp.os.linux.networking > #800

ssh security question

Path	csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!nuzba.szn.dk!pnx.dk!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From	General Schvantzkoph <schvantzkoph@yahoo.com>
Newsgroups	comp.os.linux.networking
Subject	ssh security question
Date	14 Nov 2011 19:15:34 GMT
Lines	13
Message-ID	<9id7mmF8mjU1@mid.individual.net> (permalink)
Mime-Version	1.0
Content-Type	text/plain; charset=UTF-8
Content-Transfer-Encoding	8bit
X-Trace	individual.net IGemuKkp3Fox78vu0dAELQI0KJqFkB+oNs5KmMOO04AWP+wsTi
Cancel-Lock	sha1:NagggdjbfiOu10YwyG+slYv/iDM=
User-Agent	Pan/0.133 (House of Butterflies)
Xref	x330-a1.tempe.blueboxinc.net comp.os.linux.networking:800

Show key headers only | View raw

I just regenerated the keys on one of my F14 systems. I am still able to 
access systems which don't have the new public key in their 
authorized_keys file. The one thing I did differently this time was that I 
did an ssh-add after I regenerated the keys. I did the ssh-add because 
putting the new public key into the authorized_keys files of my other 
systems wasn't sufficient to give me access. After the ssh-add I could 
access the other systems, however I could also access systems that don't 
have the new authorized_keys file.

Does ssh-add keep the old keys in the authentication agent as well as the 
new key? This would negate the value of changing keys if true.

Back to comp.os.linux.networking | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

ssh security question General Schvantzkoph <schvantzkoph@yahoo.com> - 2011-11-14 19:15 +0000
  Re: ssh security question Jorgen Grahn <grahn+nntp@snipabacken.se> - 2011-11-14 20:02 +0000
  Re: ssh security question Richard Kettlewell <rjk@greenend.org.uk> - 2011-11-14 21:05 +0000
  Re: ssh security question David Schwartz <davids@webmaster.com> - 2011-12-01 14:37 -0800

csiph-web