On 2018-09-11 16:11:02 [+0300], Adrian Bunk wrote:
> Dmitry already implemented my short-term workaround:
> https://tracker.debian.org/news/986618/accepted-qtbase-opensource-src-5111dfsg-8-source-into-unstable/
>
> When this has been built on all release architectures openssl can bump
> the
On Tue, Sep 11, 2018 at 08:14:35PM +0300, Dmitry Shachnev wrote:
> Hi Kurt,
>
> On Tue, Sep 11, 2018 at 07:09:04PM +0200, Kurt Roeckx wrote:
> > If this is for a call to SSL_CTX_set_max_proto_version(), you can
> > use 0 instead of TLS_MAX_VERSION.
>
> Good point, thanks.
>
> However as the
Hi Kurt,
On Tue, Sep 11, 2018 at 07:09:04PM +0200, Kurt Roeckx wrote:
> If this is for a call to SSL_CTX_set_max_proto_version(), you can
> use 0 instead of TLS_MAX_VERSION.
Good point, thanks.
However as the patch is temporary, I do not think it is worth
a new upload to change that.
--
Dmitry
On Tue, 11 Sep 2018 at 09:00, Jan-Marek Glogowski wrote:
> Am 11.09.2018 um 11:57 schrieb Adrian Bunk:
>
>
> Qt5 is just the first breaking package - I have no idea, how many packages
> use TLS_MAX_VERSION in
> their code.
Only a handful according to
Am 11.09.2018 um 11:57 schrieb Adrian Bunk:
>> Basically libssl 1.1.1 (in whatever 1.1.1 version - my guess is
>> 1.1.1~~pre9-1 from the changelog)
>> changed the definition of TLS_MAX_VERSION from TLS1_2_VERSION to
>> TLS1_3_VERSION, which will start to
>> break all software in buster using
Control: severity 908567 serious
Control: severity 907774 serious
Control: block 907774 by 908567
On Tue, Sep 11, 2018 at 11:00:00AM +0200, Jan-Marek Glogowski wrote:
> Package: libssl1.1
> Version: 1.1.1~~pre9-1
> Severity: important
>
> I'm on buster and with the latest updates from yesterday
6 matches
Mail list logo
