Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #21152

Closed (moved)
(moved)
Open
Created Jan 06, 2017 by Roger Dingledine@arma

"connections died in state handshaking (TLS) with SSL state SSLv3" sure makes it look like we're using SSLv3

A user on #tor pointed out:

Jan 05 13:52:18.000 [warn]  158 connections died in state handshaking (TLS) with SSL state SSLv3 read server certificate B in HANDSHAKE

Yet the ChangeLog for Tor 0.2.5.9-rc says:

    - Disable support for SSLv3. All versions of OpenSSL in use with Tor
      today support TLS 1.0 or later, so we can safely turn off support
      for this old (and insecure) protocol. Fixes bug 13426.

So, are the handshakes using SSLv3, or are they not? :)

I assume this is just a cosmetic issue where SSL_state_string_long() lies to us. But who knows, maybe there is something deeper going on?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking