Skip to content
Snippets Groups Projects
New look: Off

Decode key files with Unix or Windows newlines

    • Closed (moved) Issue created by Trac @tracbot

    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

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Trac changed milestone to %Tor: 0.4.2.x-final

      changed milestone to %Tor: 0.4.2.x-final

    • Trac added 035-backport 041-backport 042-backport 043-backport 044-should Scallion actualpoints::.2 component::core tor/tor consider-backport-after-0435 key milestone::Tor: 0.4.2.x-final onion owner::nickm points::0.5 priority::medium private reporter::larshilse reviewer::asn severity::normal status::merge-ready type::defect version::tor 0.3.5.8 labels

      added 035-backport 041-backport 042-backport 043-backport 044-should Scallion actualpoints::.2 component::core tor/tor consider-backport-after-0435 key milestone::Tor: 0.4.2.x-final onion owner::nickm points::0.5 priority::medium private reporter::larshilse reviewer::asn severity::normal status::merge-ready type::defect version::tor 0.3.5.8 labels

    • Nick Mathewson
      Nick Mathewson @nickm ·

      Trac:
      Keywords: N/A deleted, 043-should 035-backport 041-backport 042-backport added
      Milestone: N/A to Tor: 0.4.3.x-final
      Cc: N/A to dgoulet, asn

    • Alexander Hansen Færøy
      Alexander Hansen Færøy @ahf ·
      Developer

      Assigning this HS ticket to asn. Feel free to reorganize the ownership if David is a better choice here for example.

      Trac:
      Owner: N/A to asn
      Status: new to assigned

    • George Kadianakis
      George Kadianakis @asn ·

      Hm, I can't reproduce with the scallion keys found in the README with tor master or with tor 0.3.5.8.

      Is it possible you give me a scallion key directory that doesn't work for you, so that I can try to reproduce?

      Thanks!

    • Trac
      Trac @tracbot ·
      Author

      It's in

      Jan 23 00:29:34.000 [warn] Unable to decode private key from file "/var/lib/tor/hidden_serviceprivate_key"

      for me. I did just notice that the slash before "private_key" is missing. Are you getting the same issue?

      Also, I could send you my scallion.exe - perhaps that helps?

      Trac:
      Username: larshilse

    • Trac
      Trac @tracbot ·
      Author

      I tested the PK in multiple ways.

      1. took the file itself and introduced it; thought permission issues were the case.
      2. generated new key and hostname > then c&p the content of the old keys into it

      still the problem persisted.

      Trac:
      Username: larshilse

    • George Kadianakis
      George Kadianakis @asn ·

      Yes the slash should not be missing.

      Can you please generate a new key and hostname and attach it to this ticket?

      Thanks!

    • George Kadianakis
      George Kadianakis @asn ·

      Trac:
      private_key

    • George Kadianakis
      George Kadianakis @asn ·

      scallion private key (working)

    • George Kadianakis
      George Kadianakis @asn ·

      Trac:
      hostname

    • George Kadianakis
      George Kadianakis @asn ·

      scallion hostname (working)

    • George Kadianakis
      George Kadianakis @asn ·

      Hello, I can't replicate the bug. I downloaded scallion for Windows and generated the hostname and private keey that I attached above. I managed to start tor 0.4.3 with it just fine.

      Please make sure that this is not a problem with your torrc and if you are positive feel free to reopen the ticket with more info.

      Thanks!

      Trac:
      Status: assigned to closed
      Resolution: N/A to worksforme

    • T
      teor @teor ·

      Trac:
      Keywords: 043-should 035-backport 041-backport 042-backport deleted, N/A added

    • Trac
      Trac @tracbot ·
      Author

      I've had a similar problem while migrating relay keys from Windows to Debian. Same message "Error decoding PEM wrapper while reading private key". 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.

      Trac:
      Username: mr_rokman

    • T
      teor @teor ·

      Trac:
      Keywords: N/A deleted, 041-backport, 042-backport, 043-backport, 044-should, 035-backport added
      Points: N/A to 0.5
      Summary: Private keys from Scallion vanity .onion not working to Decode key files with Unix or Windows newlines
      Description: 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?

      to

      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?
      Milestone: Tor: 0.4.3.x-final to Tor: 0.4.4.x-final
      Severity: Major to Normal
      Status: closed to reopened
      Resolution: worksforme to N/A

    • Trac
      Trac @tracbot ·
      Author

      Replying to asn:

      Hello, I can't replicate the bug. I downloaded scallion for Windows and generated the hostname and private keey that I attached above. I managed to start tor 0.4.3 with it just fine.

      Please make sure that this is not a problem with your torrc and if you are positive feel free to reopen the ticket with more info.

      Thanks!

      Works in Microsoft Word as well as in v 0.4.3 ;-) It was there all of a sudden in aforementioned version. I probably upgraded. Turns out it was the line endings.

      Thanks for the great support!

      Trac:
      Username: larshilse

    • Trac
      Trac @tracbot ·
      Author

      Replying to mr_rokman:

      I've had a similar problem while migrating relay keys from Windows to Debian. Same message "Error decoding PEM wrapper while reading private key". 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.

      Thank you good sir! That was it. No idea why that would happen all of a sudden and without me (knowingly) changing anything on the system. Must have been an update/upgrade I made.

      Again: thank you very much for the great support!

      Trac:
      Username: larshilse

    • Nick Mathewson
      Nick Mathewson @nickm ·

      Trac:
      Status: reopened to accepted
      Owner: asn to nickm

    • Nick Mathewson
      Nick Mathewson @nickm ·

      Okay, this is a simple fix, now that it's been tracked down -- and thanks for tracking it down!

      My main branch is bug33032_035, with PR at https://github.com/torproject/tor/pull/1785

      The patch merges forward cleanly. I've made merge-forward branches with PRs for CI testing:

      Trac:
      Status: accepted to needs_review
      Actualpoints: N/A to .2

    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    Please register or sign in to reply