Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
Tor
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,067
    • Issues 1,067
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 20
    • Merge Requests 20
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
  • Core
  • Tor
  • Issues
  • #13054

Closed
Open
Opened Sep 04, 2014 by Roger Dingledine@armaReporter

[warn] Invalid result from curve25519 handshake: 4

I get this on the moriatoo relay, which is running git master and is also hooked up to a bwauth.

The messages around it are:

Sep 04 03:21:11.000 [warn] Invalid result from curve25519 handshake: 4
Sep 04 03:21:11.000 [warn] onion_skin_client_handshake failed.
Sep 04 03:21:11.000 [warn] circuit_finish_handshake failed.

It actually happens not infrequently, so it's not just a one-off thing.

The code is

  if (bad) {
    log_warn(LD_PROTOCOL, "Invalid result from curve25519 handshake: %d", bad);
  }

and I think 4 shows up when

  bad |= (tor_memneq(s.auth, auth_candidate, DIGEST256_LEN) << 2);

So I guess the first issue is that "4" is really not a helpful error message for me.

The second issue is to wonder what's gone wrong and whether there's a deeper bug.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.6.x-final
Milestone
Tor: 0.2.6.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/core/tor#13054