From owner-freebsd-arch@FreeBSD.ORG  Tue Feb 10 22:06:05 2015
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: arch@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 08D2134E
 for <arch@FreeBSD.org>; Tue, 10 Feb 2015 22:06:05 +0000 (UTC)
Received: from keltia.net (cl-90.mrs-01.fr.sixxs.net
 [IPv6:2a01:240:fe00:59::2])
 (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 AEF56F60
 for <arch@FreeBSD.org>; Tue, 10 Feb 2015 22:06:04 +0000 (UTC)
Received: from [192.168.1.39] (foret.keltia.net [78.232.116.160])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested) (Authenticated sender: roberto)
 by keltia.net (Postfix) with ESMTPSA id D779452AD;
 Tue, 10 Feb 2015 23:05:58 +0100 (CET)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: removing bdes..
From: Ollivier Robert <roberto@keltia.net>
X-Mailer: iPad Mail (12B466)
In-Reply-To: <20150210191329.GL3698@zxy.spb.ru>
Date: Tue, 10 Feb 2015 23:05:57 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <964BFD22-E04A-40A4-9F82-BEB1AD97EB5A@keltia.net>
References: <20150209181502.GF1953@funkthat.com>
 <20150210151812.GB67127@zxy.spb.ru> <20150210172039.GA1071@reks>
 <20150210175240.GD67127@zxy.spb.ru> <20150210175852.GV1953@funkthat.com>
 <20150210180906.GI3698@zxy.spb.ru> <20150210181916.GY1953@funkthat.com>
 <20150210183638.GK3698@zxy.spb.ru> <20150210190132.GB1953@funkthat.com>
 <20150210191329.GL3698@zxy.spb.ru>
To: Slawa Olhovchenkov <slw@zxy.spb.ru>
Cc: "arch@FreeBSD.org" <arch@FreeBSD.org>, John-Mark Gurney <jmg@funkthat.com>
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2015 22:06:05 -0000


> Hmm, as I reminder FreeBSD motto is "tools, not policies".
> If tools work as expected -- all OK.

It is also some lines of code no one want to maintain, providing a false sen=
se of security, what's the point?

> Deny insecure crypto algorithm? Why don't force to use stong crypto
> algorithm in all places (force disk, swap and memory encryption)?
> Deny unencrypted network connection?
> Deny unencrypted arhive?

That's besides the point, we are not here to keep old code for the sake of i=
t, esp. Since it will be a port.  We obsolete old code all the time you know=
.  I'd say that uucp was more useful than bdes and we still removed it.=20

Why making so big a fuss?
--=20
Ollivier Robert=