> Some suggestions:
>
> - don't copy the ed25519_master_id_public_key file. If it is missing,
> Tor will just compute it from the certificate and save it to disk.
> But, if by accident an user copies the medium term signing keys
> related to another relay, Tor will detect they don't match the
>
>> I copy/expose the following files to the relay:
>> >
>> > [ 'ed25519_master_id_public_key', 'ed25519_signing_cert',
>> > 'ed25519_signing_secret_key', 'secret_id_key', 'secret_onion_key',
>> > 'secret_onion_key_ntor']
>> >
>> >
> When first setting up (new relay) or restoring the relay,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/19/2015 12:19 AM, nusenu wrote:
>> background: I might want to integrate offline master key
>> functionality into ansible-relayor [1].
>
> I added (preliminary) OfflineMasterKey support to ansible-relayor
> [1] - in fact it will become the
> background:
> I might want to integrate offline master key functionality into
> ansible-relayor [1].
I added (preliminary) OfflineMasterKey support to ansible-relayor [1] -
in fact it will become the only option eventually as it make many things
actually simpler, would be great if someone could
