From owner-freebsd-questions@FreeBSD.ORG Tue Jan 1 12:36:54 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C64A4F47 for ; Tue, 1 Jan 2013 12:36:54 +0000 (UTC) (envelope-from talayeh.asadi@gmail.com) Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) by mx1.freebsd.org (Postfix) with ESMTP id 7F05E8FC08 for ; Tue, 1 Jan 2013 12:36:54 +0000 (UTC) Received: by mail-ie0-f170.google.com with SMTP id k10so16217706iea.29 for ; Tue, 01 Jan 2013 04:36:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=VeQoeVuktM4ZSXRhmSQWILc/49sgVdQ4rO/o8f/+4dU=; b=UkqkFqDl6C161EhEW/MEpIuRb9YRFAt6GBeMT5BRyJOcShGJInWDj8vtSxHbraUTNS jZb9g9v1xh4e7NIf4nQm33XnF6cLrGOIKBlYncv1G/s7uDHRPwCrHOdtSipyNTmvZwG/ MN3uLBakbe2ST3WC9+KvgSPqNEvotD/8rHxX/1HHfwG1iiqRq0kuQnhMDVIN2OfZIJBL klQbJwxPUlOl3yVZZ/RO/zCQ8bWQpBqUQXngMZvYC+RTSDcyFm/ZFyQgKastQevEkNLJ 0hJ5GdnmT32dVYCrcLVbOA5qAGThOzhbQHkux4YOLPkRBbOEvisZy9TDBxxqbftKsph8 N+uA== Received: by 10.42.121.1 with SMTP id h1mr32939163icr.43.1357043807086; Tue, 01 Jan 2013 04:36:47 -0800 (PST) MIME-Version: 1.0 Sender: talayeh.asadi@gmail.com Received: by 10.42.161.130 with HTTP; Tue, 1 Jan 2013 04:36:26 -0800 (PST) In-Reply-To: References: From: takCoder Date: Tue, 1 Jan 2013 16:06:26 +0330 X-Google-Sender-Auth: B-2CUqL8XzrprBHBIMD0mPEW7_8 Message-ID: Subject: Re: ssh server hashcode change on nanoBSD To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: tak.official@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jan 2013 12:36:54 -0000 >---------- Forwarded message ---------- >From: Aldis Berjoza >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 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 >