Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 311
    • Issues 311
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 35
    • Merge requests 35
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #40128
Closed
Open
Created Sep 20, 2020 by Felix@Felix

Libressl 3.2.1 with compatibility issues to Tor relays

Hi all

After upgrade of Ichotolot60 1AE039EE0B11DB79E4B4B29CBA9F752864A0259E from 4.2.7 to 4.4.5 it dropped off consensus.

Apr 02 21:51:31.872 [notice] Tor 0.4.2.7 running on FreeBSD with Libevent 2.1.11-stable, OpenSSL LibreSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.4.4.

The consensus-health on April/9 shows all auths see it running.

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.

The consensus-health after one day shows:

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
bwauth=n/a

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. The consensus-health shows 2 hours after Libressl 321 -> 320

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
bwauth=gabelmoo

Libressl 321 is not compatible to the authorities tor26, dizum, gabel., maatu. and longc. to grant a "Running. What can that be?

:: Legacy :: We had the same trouble with Libressl 292 when 28x worked well and 30x too.

With Libressl292 the consensus-health showed Sep/7 2019 ACBBB426CE1D0641A590BF1FC1CF05416FC0FF6F Planetclaire62

 Fast             !Running Stable V2Dir Valid bw=8200
 Fast             !Running Stable V2Dir Valid
!Fast              Running Stable V2Dir Valid
 Fast             !Running Stable V2Dir Valid
!Fast              Running Stable V2Dir Valid
 Fast             !Running Stable V2Dir Valid
 Fast              Running Stable V2Dir Valid bw=747
 Fast Guard HSDir  Running Stable V2Dir Valid
 Fast Guard HSDir  Running Stable V2Dir Valid bw=8180
 Fast              Running Stable V2Dir Valid bw=8180
bwauth=faravahar 
Edited Sep 20, 2020 by Felix
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking