From owner-freebsd-bugs@FreeBSD.ORG Fri Aug 9 07:41:55 2013 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.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 ESMTP id 01C8DF40; Fri, 9 Aug 2013 07:41:55 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CC4DB2414; Fri, 9 Aug 2013 07:41:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r797fsqk026507; Fri, 9 Aug 2013 07:41:54 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r797fs4o026506; Fri, 9 Aug 2013 07:41:54 GMT (envelope-from remko) Date: Fri, 9 Aug 2013 07:41:54 GMT Message-Id: <201308090741.r797fs4o026506@freefall.freebsd.org> To: remko@FreeBSD.org, cperciva@FreeBSD.org, freebsd-bugs@FreeBSD.org From: remko@FreeBSD.org Subject: Re: bin/149412: bdes(1) in CFB/OFB modes can't decrypt own output X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 07:41:55 -0000 Synopsis: bdes(1) in CFB/OFB modes can't decrypt own output Responsible-Changed-From-To: cperciva->freebsd-bugs Responsible-Changed-By: remko Responsible-Changed-When: Fri Aug 9 07:41:13 UTC 2013 Responsible-Changed-Why: This is not something -secteam related so throw it back in the pool. One of the questions that passed me is that why would someone do this when openssl is capable of doing the same? http://www.freebsd.org/cgi/query-pr.cgi?pr=149412