Date: Tue, 1 Jan 2013 18:59:05 +0330 From: takCoder <tak.official@gmail.com> To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: ssh server hashcode change on nanoBSD Message-ID: <CAPkyVLz1DSEn3hsJBBDN=YS5E9qRri5GyYXaqvJyNkXkiJojdQ@mail.gmail.com> In-Reply-To: <20130101154021.322bef33.freebsd@edvax.de> References: <CAPkyVLxQhPr0k-HOyFLHumpqwHrBg6f_zex_gDTi9d8WEUJuYw@mail.gmail.com> <20130101154021.322bef33.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
thank you for the details mentioned :) but now, a questions occurred to me about this ssh key. as i don't know enough about its process, would you please tell me whether this key is a shared key for all ssh clients who send a request? or it differs as the client changes? (this question may sound a bit newbiesh, but i don't know much about the ssh process, sorry :) ) Best Regards, t.a.k On Tue, Jan 1, 2013 at 6:10 PM, Polytropon <freebsd@edvax.de> wrote: > On Tue, 1 Jan 2013 14:11:21 +0330, takCoder wrote: > > everything is fine until i restart my nanoBSD server. the problem is that > > each time i restart my server, the source system is complaining about > that > > i need to edit my known_hosts file cause my nanoBSD hash-code is not > > matched.. > > > > how can i fix this?! it really bothers me cause i think of it as a > security > > problem.. i can't risk such things on my server.. > > You should make the key permanent (i. e. include it on the > boot media you're using). In case no key is found at sshd > startup, a new one will be generated - a different one each > time, of course. So what you're seeing seems to be "normal", > even though not desired at all. :-) > > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPkyVLz1DSEn3hsJBBDN=YS5E9qRri5GyYXaqvJyNkXkiJojdQ>