It appears that a few people (incl. me) are having trouble with their scallion generated keys after upgrade to a recent version of tor.
In my case the scallion generated key cannot be read by tor upon launch.
This the output I get:
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.
Yes, I did notice the second "/" in the dir path... how's that resolved? And: is that the issue?
Keys generated by tor (and associated hostnames) work fine.
It appears that a few people (incl. me) are having trouble with their scallion generated keys after upgrade to a recent version of tor.
In my case the scallion generated key cannot be read by tor upon launch.
This the output I get:
Yes, I did notice the second "/" in the dir path... how's that resolved? And: is that the issue?
Keys generated by tor (and associated hostnames) work fine.