From owner-freebsd-questions@FreeBSD.ORG Wed Jan 2 14:22:49 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 2B80CB70 for ; Wed, 2 Jan 2013 14:22:49 +0000 (UTC) (envelope-from talayeh.asadi@gmail.com) Received: from mail-ia0-f170.google.com (mail-ia0-f170.google.com [209.85.210.170]) by mx1.freebsd.org (Postfix) with ESMTP id 79FC48FC12 for ; Wed, 2 Jan 2013 14:22:48 +0000 (UTC) Received: by mail-ia0-f170.google.com with SMTP id i1so11909590iaa.15 for ; Wed, 02 Jan 2013 06:22: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:cc:content-type; bh=yahIwQEyb7ZhrQz+6ahCkVOwDfPutUX3VC2CkZfUOlg=; b=lDM1pyicDp7M8npVRendTf8tQjF+N/+y75a+E9cknJ2qmLyyNxx+KourTd7D8jasE+ 93owmzdCkMOD3EnvjoLvaSRuwakI7kFQ53buJO8U4CLKqJSVc6eYseJQ7l0JVywvNErH jnmw77vFYfmiOFO74qDreaJIm2PqxUPSfmiq8pItJLAiLvKkd++eeBIWWVmfXy2+WCub JhHgXDl4B44d4kT9OB9K4xIV9JIZ0UENzoTHOWuarVHn3EiOGWeOUPX2YQ5E866TE28p lIMu6JVAVoxoUcaA5M0Povmg/9/zMaZ1EKKf8OqUUoqGWPCeMNlZwiu65WTBONc5JplY Mdfg== Received: by 10.50.195.135 with SMTP id ie7mr39036739igc.8.1357136567801; Wed, 02 Jan 2013 06:22:47 -0800 (PST) MIME-Version: 1.0 Sender: talayeh.asadi@gmail.com Received: by 10.42.161.130 with HTTP; Wed, 2 Jan 2013 06:22:27 -0800 (PST) In-Reply-To: <20130102115227.67242dd5.freebsd@edvax.de> References: <20130101154021.322bef33.freebsd@edvax.de> <20130102115227.67242dd5.freebsd@edvax.de> From: takCoder Date: Wed, 2 Jan 2013 17:52:27 +0330 X-Google-Sender-Auth: OcmjvRElGl_aGie32VZXdAr15SU Message-ID: Subject: Re: ssh server hashcode change on nanoBSD To: Polytropon , Lowell Gilbert Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-questions@freebsd.org 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: Wed, 02 Jan 2013 14:22:49 -0000 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 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. and On Wed, Jan 2, 2013 at 2:22 PM, Polytropon wrote: >The key received in the first step of a SSH session is the >host key which identifies the host (in your case: the nanoBSD >box). This key is stored in the SSH client's key database for >reference because the key of a box typically does not change. .. >As explained, this host key is generated when no key is found >at startup. As soon as you make it permanent to your nanoBSD >installation, the key will obviously stay the same, and the >SSH client won't complain i made my ssh server key permanent on my nanoBSD server, by moving /etc/ssh/ files to /cfg/ssh files (i think those two files named dsa_key are enough, but in this test, i copied all files in the source dir..) and now there are no compliments from any clients, thanks to Polytropon and Lowell and Aldis. :) >Cryptography in general is quite complicated, and ssh is a lot more >complicated than just its cryptography. and also thank you all for your patience and good explanations :) Best Regards, t.a.k