From owner-freebsd-arch@FreeBSD.ORG Tue Feb 10 17:50:21 2015 Return-Path: Delivered-To: arch@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 B3173B99 for ; Tue, 10 Feb 2015 17:50:21 +0000 (UTC) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 6CFA3E05 for ; Tue, 10 Feb 2015 17:50:21 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1YLEwz-000KZZ-Ly; Tue, 10 Feb 2015 20:50:17 +0300 Date: Tue, 10 Feb 2015 20:50:17 +0300 From: Slawa Olhovchenkov To: John-Mark Gurney Subject: Re: removing bdes.. Message-ID: <20150210175017.GC67127@zxy.spb.ru> References: <20150209181502.GF1953@funkthat.com> <20150210151812.GB67127@zxy.spb.ru> <20150210174301.GT1953@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150210174301.GT1953@funkthat.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: arch@FreeBSD.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 17:50:21 -0000 On Tue, Feb 10, 2015 at 09:43:01AM -0800, John-Mark Gurney wrote: > Slawa Olhovchenkov wrote this message on Tue, Feb 10, 2015 at 18:18 +0300: > > On Mon, Feb 09, 2015 at 10:15:02AM -0800, John-Mark Gurney wrote: > > > > > So, I happen to stuble across bdes recently and think we should remove > > > it.. > > > > > > I'm fine w/ making it a port so that people who need it can use it... > > > > > > Especially considering: > > > The DES cipher should no longer be considered secure. Please consider > > > using a more modern alternative. > > > > > > Though sadly, that comment was added almost 15 years after DES was > > > brute forced by DEEPCrack. > > > > Clear text also insecure. Do you remove all clear text? > > If I have to answer that question for you, I don't need to respond to > you... > > Once you have a valid argument for keeping it, I'll respond... Keeping support for DES encrypting/decrytpting create vulnerability? or support difficult? What problem resolv removing DES support (and break compatibility)?