From owner-freebsd-questions@FreeBSD.ORG Mon Jan 27 12:11:21 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F0BA96A0 for ; Mon, 27 Jan 2014 12:11:21 +0000 (UTC) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5274211FB for ; Mon, 27 Jan 2014 12:11:20 +0000 (UTC) Received: from [192.168.1.35] (host86-163-127-175.range86-163.btcentralplus.com [86.163.127.175]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id s0RCBIMs064085 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 27 Jan 2014 12:11:18 GMT (envelope-from frank2@fjl.co.uk) Message-ID: <52E64CE9.10304@fjl.co.uk> Date: Mon, 27 Jan 2014 12:11:21 +0000 From: Frank Leonhardt User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Sendmail Error at Boot References: <52E5C7D3.8050703@bsdbox.co> <52E60AA0.8080904@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 12:11:22 -0000 On 27/01/2014 07:40, Robert Simmons wrote: > On Mon, Jan 27, 2014 at 2:28 AM, Matthew Seaman wrote: >> On 27/01/2014 03:19, Robert Simmons wrote: >>> Why is this not part of the install? >> Sendmail in base doesn't come configured to use TLS by default, although >> the appropriate capabilities are compiled in to the binaries. >> >> I've no idea why enabling TLS isn't the default -- seems like a >> no-brainer in this day and age. It would require generating a key and >> (self-signed) cert on first startup after installation, much like the >> way SSH keys are generated, but so long as the problems with startup >> entropy availability have been satisfactorily sorted out (which I >> believe they have) I can't see any huge problem with that. > Thanks for the explanation. I agree with the no-brainer. Last week the > keynote at ShmooCon was Ian Golberg, and one of the main points of his > talk was that nothing should ever be sent over a network in plaintext > from now on. And there should not be a choice of two protocol > versions, one encrypted and one plaintext, because a non-zero number > of users will choose plaintext. > It's not as simple as that as quite a lot of application software uses the unencrypted ports and it has no way of knowing whether it's talking on a secure unencrypted line (i.e. local copper or VPN). I haven't played with the latest release sendmail, but if SSL and SASL are easier to turn on, that's a great start. I don't think anyone with a brain has been sending unencrypted email across the Internet, except possibly iPhone users, for whom installing a self-signed certificate seems to be impossible (if anyone knows a method that's simple enough for a fanboi to understand, please tell me!)