Date: Tue, 01 Jan 2013 14:11:23 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: tak.official@gmail.com Cc: freebsd-questions@freebsd.org Subject: Re: ssh server hashcode change on nanoBSD Message-ID: <44y5gciuqs.fsf@lowell-desk.lan> In-Reply-To: <CAPkyVLz1DSEn3hsJBBDN=YS5E9qRri5GyYXaqvJyNkXkiJojdQ@mail.gmail.com> (takCoder's message of "Tue, 1 Jan 2013 18:59:05 %2B0330") References: <CAPkyVLxQhPr0k-HOyFLHumpqwHrBg6f_zex_gDTi9d8WEUJuYw@mail.gmail.com> <20130101154021.322bef33.freebsd@edvax.de> <CAPkyVLz1DSEn3hsJBBDN=YS5E9qRri5GyYXaqvJyNkXkiJojdQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Don't top-post, please. takCoder <tak.official@gmail.com> writes: > 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? There are a number of keys involved in ssh. The host keys are used at the start of the connection to make sure that some other machine doesn't impersonate the one you wanted. The encryption of the data happens with per-session keys, which are not only different for each client, but for every session. The two types of keys are not related to each other. > (this question may sound a bit newbiesh, but i don't know much about the > ssh process, sorry :) ) Cryptography in general is quite complicated, and ssh is a lot more complicated than just its cryptography.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44y5gciuqs.fsf>