From owner-freebsd-security@freebsd.org Mon Jul 11 20:13:41 2016 Return-Path: Delivered-To: freebsd-security@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5BFBDB92C94; Mon, 11 Jul 2016 20:13:41 +0000 (UTC) (envelope-from slw@zxy.spb.ru) 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 1D71110FA; Mon, 11 Jul 2016 20:13:41 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bMhaQ-000Hpm-MN; Mon, 11 Jul 2016 23:13:50 +0300 Date: Mon, 11 Jul 2016 23:13:50 +0300 From: Slawa Olhovchenkov To: Andrey Chernov Cc: Mark Felder , freebsd-security@freebsd.org, freebsd-current@freebsd.org Subject: Re: GOST in OPENSSL_BASE Message-ID: <20160711201350.GF20831@zxy.spb.ru> References: <20160710133019.GD20831@zxy.spb.ru> <20160710150143.GK46309@zxy.spb.ru> <9ead7cd7-7d1b-2dd8-eea8-43f7766d92a9@freebsd.org> <20160711102906.GN46309@zxy.spb.ru> <1468253073.695754.662984777.1E8F9C28@webmail.messagingengine.com> <20160711162902.GO46309@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) 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 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 20:13:41 -0000 On Mon, Jul 11, 2016 at 07:48:44PM +0300, Andrey Chernov wrote: > On 11.07.2016 19:29, Slawa Olhovchenkov wrote: > > On Mon, Jul 11, 2016 at 11:04:33AM -0500, Mark Felder wrote: > > > >> > >> > >> On Mon, Jul 11, 2016, at 05:29, Slawa Olhovchenkov wrote: > >>> > >>> I.e. GOST will be available in openssl. > >>> Under BSD-like license. > >>> Can be this engine import in base system and enabled at time 1.1.0? > >>> And can be GOST enabled now? > >>> > >> > >> I think the wrong question is being asked here. Instead we need to focus > >> on decoupling openssl from base so this can all be handled by ports. > > > > This is wrong direction with current policy. > > ports: unsupported by FreeBSD core and securite team, no guaranted to comaptible > > between options and applications. > > > > base: supported by FreeBSD core and securite team, covered by CI, > > checked for forward and backward API and ABI compatibility. > > > > Ports are supported by secteam, and recently I notice "headsup" mail > with intention to make base openssl private and switch all ports to > security/openssl port. I mean `support` is commit reviewing, auditing and etc. Secteam do it for ports? > Adding of GOST as 3rd party plugin is technically possible in both > (base, ports) cases, the rest of decision is up to FreeBSD openssl > maintainers and possible contributors efforts. > > I need to specially point to "patches" section of the 3rd party GOST > plugin, from just viewing I don't understand, are those additional > openssl patches should be applied to openssl for GOST, or they are just > reflect existent changes in the openssl. > > _______________________________________________ > freebsd-security@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"