From owner-freebsd-ports@FreeBSD.ORG  Tue Jun  2 01:25:16 2015
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@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 398B9EBA
 for <freebsd-ports@FreeBSD.ORG>; Tue,  2 Jun 2015 01:25:16 +0000 (UTC)
 (envelope-from marquis@roble.com)
Received: from mx5.roble.com (mx5.roble.com [206.40.34.5])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 2980017CF
 for <freebsd-ports@FreeBSD.ORG>; Tue,  2 Jun 2015 01:25:15 +0000 (UTC)
 (envelope-from marquis@roble.com)
Date: Mon, 1 Jun 2015 18:25:14 -0700 (PDT)
From: Roger Marquis <marquis@roble.com>
To: Tim Daneliuk <tundra@tundraware.com>
cc: FreeBSD Ports Mailing List <freebsd-ports@FreeBSD.ORG>
Subject: Re: Port Fetch Failing
In-Reply-To: <20150602000954.GF1733@over-yonder.net>
References: <556CEBE2.7030005@tundraware.com> <556CEEB8.2090406@delphij.net>
 <556CF2B1.30100@tundraware.com> <20150602000954.GF1733@over-yonder.net>
User-Agent: Alpine 2.11 (BSF 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jun 2015 01:25:16 -0000

>> Thanks to you and Chuck, I have a more reasonable (I think):
>> SSLCipherSuite  ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+EXP:-eNULL:-SSLv3:-SSLv2:TLS_RSA_WITH_AES_256_CBC_SHA:TLS_RSA_WITH_AES_256_CBC_SHA256

Reasonable depends on the use case.  Though this topic would be better
discussed on freebsd-security@, the good advice given on
<https://wiki.mozilla.org/Security/Server_Side_TLS>,
<https://www.insecure.ws/2013/10/11/ssltls-configuration-for-apache-mod_ssl/>
and <https://weakdh.org/sysadmin.html> tends to recommend:

  SSLCipherSuite HIGH:MEDIUM:!IDEA:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA
  SSLProtocol         all -SSLv2 -SSLv3
  SSLCompression      off
  SSLHonorCipherOrder on

and if you're using httpd 2.3.3 or higher:

  SSLUseStapling          on
  SSLStaplingResponderTimeout 5
  SSLStaplingReturnResponderErrors off
  SSLStaplingCache        shmcb:/var/run/ocsp(128000)

If you're processing credit cards SSLProtocol will need to be expanded to
"-SSLv2 -SSLv3 -TLSv1" by 2016/07 (for PCI compliance) and if you have
good reason to be paranoid and all of your clients are up-to-date, add
"-TLSv1.1".

Roger Marquis