Skip to content
GitLab
Projects Groups Snippets
  • /
  • 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
  • #33032
Closed (moved) (moved)
Open
Issue created Jan 22, 2020 by Trac@tracbot

Decode key files with Unix or Windows newlines

Update:

In my case culprit was the line endings in PEM, lines were terminated Windows-style - {CR}{LF}. Changed them to {LF} and keys were read just fine.

After the upgrade to v 0.3.5.8 my onion wasn't available anymore.

This is the info I get when attempting to start tor:

Jan 23 00:29:34.000 [warn] Error decoding PEM wrapper while reading private key Jan 23 00:29:34.000 [warn] Unable to decode private key from file "/var/lib/tor/hidden_service//private_key" Jan 23 00:29:34.000 [err] Error loading private key. Jan 23 00:29:34.000 [warn] Error loading rendezvous service keys Jan 23 00:29:34.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.3.5.8 ) Jan 23 00:29:34.000 [err] Reading config failed--see warnings above.

More users are having the same issue, that their Scallion generated keys cannot be read by the most recent version of TOR.

Any ideas?

Trac:
Username: larshilse

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