>---------- 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 can create ssh_host keys and embed them in you NanoBSD image >-- >Aldis Berjoza >FreeBSD addict
thank you :) for the ones who know about nanobsd, i've got a /cfg on nanobsd. during nanoBsd startup, files in /etc are replaced with their new version in /cfg, if any; (as /etc is a md here). so, in the case i explained above, i just needed to copy /etc/ssh/* to /cfg/ssh/ and now, everything is fine :) Best Regards, t.a.k Best Regards, t.a.k On Tue, Jan 1, 2013 at 2:11 PM, takCoder <tak.offic...@gmail.com> wrote: > hi everyone, > > i've got a nanoBSD server. when i ssh to it from another bsd system, > first time everything is fine. the source bsd system asks me whether i > trust my nanoSBD server or not and i apply y and the nanoBSD hash key is > written in known_hosts file. > > 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.. > > would someone please give me a hand on this? > > always grateful of all your helps here :) > > Best Regards, > t.a.k > _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
