From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 1C762138334 for ; Sat, 9 Jun 2018 09:21:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 05CC1E0963; Sat, 9 Jun 2018 09:21:29 +0000 (UTC) Received: from blaine.gmane.org (unknown [195.159.176.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7A099E08EC for ; Sat, 9 Jun 2018 09:21:28 +0000 (UTC) Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1fRa1i-0004Fc-R7 for gentoo-dev@lists.gentoo.org; Sat, 09 Jun 2018 11:19:14 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Martin Vaeth Subject: [gentoo-dev] Re: Current status with openssl-1.1 Date: Sat, 9 Jun 2018 09:19:07 +0000 (UTC) Message-ID: References: <20180609102206.131b1117@abudhabi.paradoxon.rec> X-Complaints-To: usenet@blaine.gmane.org User-Agent: slrn/1.0.3 (Linux) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Archives-Salt: 911237d4-f85d-4049-912a-6a4d8f36f379 X-Archives-Hash: b89325bfb668bff5d71f6d7ddf18f244 Lars Wendler wrote: > So, basically openssl is the last big showstopper for openssl-1.1 to > get out of p.mask. s/openssl/openssh/ Another showstopper is net-libs/wvstreams, hence net-dialup/wvdial. BTW, this is a Debian bug open without any comment since April 2017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859791 Debians and Archs workarounds can be called slotting of openssl:1.0 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828603 While many of the new opaqueness problems are easy to fix, some functions of wvstreams rely so much on internals which are inaccessible with openssl-1.1 that they seem impossible to convert. My guess (I am not an openssl guru) is that the whole wvstreams implementation would need to change, maybe also the provided API with some functionality being dropped or attacked completely differently. The uncommented bugreports and missing PRs suggest that this will never happen by upstream, and there also seems to be no fork with it. Maybe for wvstreams a workaround might be to mask/remove USE=ssl: Perhaps wvdial would then loose some functionality (does anybody know what would break?) but given how useful wvdial is, this is better than dropping it completely.