Bug 250613 - security/libressl-devel regression as of 3.2.1 due to change in tls1_export_keying_material()
Summary: security/libressl-devel regression as of 3.2.1 due to change in tls1_export_k...
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Bernard Spil
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2020-10-25 22:14 UTC by Felix
Modified: 2022-05-13 12:30 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (brnrd)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Felix 2020-10-25 22:14:50 UTC 
Hello to whom this might concern

We have a potential issue [0] between Tor and Libressl from ports since version 3.2.1. The issue was already reported [1].

So this might be a duplicate. Forgive me if I am doing wrong here but for everybodies awareness ...

The not so nice thing is 3.2.2 sits in devel and non-devel, so we have to move to 3.2.0 (which works) or to the base system.

[0] https://gitlab.torproject.org/tpo/core/tor/-/issues/40128
[1] https://github.com/libressl-portable/portable/issues/629

-- 
Cheers and have a nice week, Felix
Comment 1 Bernard Spil freebsd_committer freebsd_triage 2020-10-26 19:23:54 UTC 
Hi Felix,

This is very unfortunate. Will keep it open here until it is resolved.
Comment 2 Felix 2021-10-22 22:19:54 UTC 
(In reply to Bernard Spil from comment #1)

Good news, Libressl seems to work for Tor 4.6.7 (current stable) with Libressl 3.4.1 (Freebsd ports libressl/devel).

You can watch https://gitlab.torproject.org/tpo/core/tor/-/issues/40128 for updates. We want to wait a week or two to get confirmation.
Comment 3 Felix 2022-05-13 12:30:57 UTC 
TLS 1.3 API works fine since then. Issue can be closed