From: Martin Vaeth <martin@mvath.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Current status with openssl-1.1
Date: Sat, 9 Jun 2018 09:19:07 +0000 (UTC) [thread overview]
Message-ID: <slrnphn70f.7dd.martin@fox.invalid> (raw)
In-Reply-To: 20180609102206.131b1117@abudhabi.paradoxon.rec
Lars Wendler <polynomial-c@gentoo.org> 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.
next prev parent reply other threads:[~2018-06-09 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-09 8:22 [gentoo-dev] Current status with openssl-1.1 Lars Wendler
2018-06-09 8:36 ` Michał Górny
2018-06-09 9:16 ` Pacho Ramos
2018-06-09 9:19 ` Martin Vaeth [this message]
2018-06-09 11:55 ` [gentoo-dev] " Luca Barbato
2018-06-09 21:48 ` [gentoo-dev] " James Cloos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrnphn70f.7dd.martin@fox.invalid \
--to=martin@mvath.de \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox