From owner-freebsd-security@FreeBSD.ORG  Mon Jan 12 01:22:16 2015
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 90A1483D
 for <freebsd-security@freebsd.org>; Mon, 12 Jan 2015 01:22:16 +0000 (UTC)
Received: from roadkill.tharned.org (roadkill.tharned.org [75.145.12.185])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 54073B71
 for <freebsd-security@freebsd.org>; Mon, 12 Jan 2015 01:22:15 +0000 (UTC)
Received: from angus.tharned.org (angus.tharned.org [10.10.10.7])
 (authenticated bits=0)
 by roadkill.tharned.org (8.14.9/8.14.9) with ESMTP id t0C1M288051857
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
 for <freebsd-security@freebsd.org>; Sun, 11 Jan 2015 19:22:08 -0600 (CST)
 (envelope-from gcr+freebsd-security@tharned.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tharned.org; s=2014;
 t=1421025728; bh=tFX8ARJxQil8pIKc8Q942RwxuwtOGhDT6t2vOVnJZf0=;
 h=Date:From:To:Subject;
 b=HRUk1gatRN4lrucUpczRolxNmIWFXzS1uOnU3DEopf9ZvNocMIiGkI6H6BM0CY1Kx
 xSOoZp6Lh7XF1usBJ+xMWTQPpbycD5A1gspNiv9O76+YAlTI1DQ5qDMltpRnpuTNgT
 kdQsL/0n3iTgDtJ407koRKaIPODUV/Bpi/ak1Gb7aE/v+JvhXwXhTW+rGLXbEBuaaJ
 7OddkYVkjns2IG9fVZLlN9O3G0904XPS6xvR6dhdtrX+bZYRKEpIMs+SrW/5RNBJSU
 7UqZurPE2zqyexCPi+pW97PBUT6asj1ttnpi0XSDbn1TYjYLh6PknyjcTTYLCd3C9t
 bKId535dorGNA==
Date: Sun, 11 Jan 2015 19:22:02 -0600 (CST)
From: Greg Rivers <gcr+freebsd-security@tharned.org>
To: freebsd-security@freebsd.org
Subject: Securing SSH
Message-ID: <alpine.BSF.2.11.1501111913310.9102@angus.tharned.org>
User-Agent: Alpine 2.11 (BSF 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3
 (roadkill.tharned.org [75.145.12.185]); Sun, 11 Jan 2015 19:22:08 -0600 (CST)
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jan 2015 01:22:16 -0000

I came across an interesting article[1] about more secure SSH 
configurations.  What do our resident cryptographers think about this? 
Would it make sense to adjust FreeBSD defaults accordingly?

[1] https://stribika.github.io/2015/01/04/secure-secure-shell.html

-- 
Greg Rivers