On Tue, 1 Jan 2013 18:59:05 +0330, takCoder wrote:
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
On Tue, Jan 1, 2013 at 10:41 PM, Lowell Gilbert wrote:
Don't top-post, please.
Sorry for top-posting.. i'll try to keep an eye on it from now on :)
well, cause i got my answer, let's have a conclusion:
According to:
On Tue, Jan 1, 2013 at 10:41 PM, Lowell Gilbert wrote:
There are a number of
-- Forwarded message --
From: Aldis Berjoza graude...@yandex.com
Date: Tue, Jan 1, 2013 at 2:17 PM
Subject: Re: ssh server hashcode change on nanoBSD
I've never used NanoBSD, but, check if ssh daemon can write to /etc/ssh/
otherwise it won't be able to save ssh_host_* keys
Or you
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
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
Don't top-post, please.
takCoder tak.offic...@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
