#33032: Decode key files with Unix or Windows newlines -------------------------------------------------+------------------------- Reporter: larshilse | Owner: asn Type: defect | Status: | reopened Priority: Medium | Milestone: Tor: | 0.4.4.x-final Component: Core Tor/Tor | Version: Tor: | 0.3.5.8 Severity: Normal | Resolution: Keywords: Scallion, onion, private key, | Actual Points: 044-should, 035-backport, 041-backport, | 042-backport, 043-backport | Parent ID: | Points: 0.5 Reviewer: | Sponsor: -------------------------------------------------+------------------------- Changes (by teor):
* status: closed => reopened * severity: Major => Normal * points: => 0.5 * milestone: Tor: 0.4.3.x-final => Tor: 0.4.4.x-final * keywords: Scallion, onion, private key => Scallion, onion, private key, 044-should, 035-backport, 041-backport, 042-backport, 043-backport * resolution: worksforme => Old 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? New description: 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? -- -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33032#comment:10> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs