Okay, so fixing the permissions fixed the whole problem.
At least until it asks where the master_id_secret_key is again when it
needs a newer medium-term signing_secret_key.
I know why debian-tor and [user] are separate, I'm just saying that
having the [user] move debian-tor files around can make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 1/5/2016 12:13 AM, 12xBTM wrote:
> Now I'm getting permission denied, still out-dated key, and
> missing master_id_secret_key errors, which are unsurprisingly
> fatal.
>
> Jan 04 22:41:33.000 [warn] Could not open
> "/var/lib/tor/keys/ed25519_s
Now I'm getting permission denied, still out-dated key, and missing
master_id_secret_key errors, which are unsurprisingly fatal.
Jan 04 22:41:33.000 [warn] Could not open
"/var/lib/tor/keys/ed25519_signing_secret_key": Permission denied
Jan 04 22:41:33.000 [notice] It looks like I need to generate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
Let's recap (hope I am not missing something):
a) you make sure master_id_secret_key is available in
/home/[user]/.tor/keys
b) you run # tor --keygen and provide the correct passphrase
c) you *move* the newly generated ed25519_signing_secret
So my medium-term signing key expires tomorrow, and Tor notices.log is
all up and down about:
Jan 04 19:22:46.000 [notice] It looks like I should try to generate and
sign a new medium-term signing key, because the one I have is going to
expire soon. But OfflineMasterKey is set, so I won't try to l
