Hi everybody
Sep 18 21:00:22.384 [notice] Tor 0.4.4.5 running on FreeBSD with Libevent 2.1.12-stable, OpenSSL LibreSSL 3.2.1, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.4.5. moria1 Fast Run Stab V2Dir Valid bw=566 tor26 Fast Guard Stab V2Dir Valid dizum Fast Guard Stab V2Dir Valid gabel. Fast Stab V2Dir Valid bw=1130 danne. Fast Guard Run Stab V2Dir Valid maatu. Fast Stab V2Dir Valid bw=1200 farav. Fast Guard Run Stab V2Dir Valid bw=2970 longc. Fast Stab V2Dir Valid bw=490 bastet Fast Guard Run Stab V2Dir Valid bw=3520
2 hours after Libressl 321 -> 320 Sep 20 10:30:45.633 [notice] Tor 0.4.4.5 running on FreeBSD with Libevent 2.1.12-stable, OpenSSL LibreSSL 3.2.0, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.4.5. moria1 Fast Run Stab V2Dir Valid bw=566 tor26 Fast Run Stab V2Dir Valid dizum Fast Run Stab V2Dir Valid gabel. Fast Run Stab V2Dir Valid bw=1130 danne. Fast -Guard Run Stab V2Dir Valid maatu. Fast Run Stab V2Dir Valid bw=1200 farav. Fast -Guard Run Stab V2Dir Valid bw=2970 longc. !Fast Run Stab V2Dir Valid bw=70 bastet Fast -Guard Run Stab V2Dir Valid bw=3520 OWNER :: bwauth=gabelmoo
(Yeah, some Lib stuff is new too, hehe)
Libressl 321 is not compatible to what is needed to make the authorities tor26, dizum, gabel., maatu. and longc. happy (let them not grant a "Running"). What can that be?
Please somebody can _confirm_ this thing?
PS: We had the same trouble with Libressl 292 when 28x worked well and 30x too.
PPS: Is that a good reason to stay away from automated updates? Ok, Libressl 321 is -devel ....
-- Cheers, Felix