> Why do you use such a value for SigningKeyLifetime when the default is
> 30 days already? You can just skip --signingkeylifetime and have
> medium term signing key valid for 30 days (1 month). I am not totally
> sure *1 months* is a valid argument here (could be, not sure)
--signingkeylifetime
> Two months ago I decided to try the new ed25519 key introduced in Tor
> 2.7 with OfflineMasterKey
great to see more people using/testing this feature.
> That raises two questions to me:
> - why does Tor think the new keys are already expired?
Did you manually verify the expire dates of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thank you s7r for helping!
On 03/02/2016 17:53, s7r wrote:
> Hello - see inline
>
> On 2/3/2016 3:49 PM, Riccardo Mori wrote:
>> Hi everyone,
>
>> Two months ago I decided to try the new ed25519 key introduced
>> in Tor 2.7 with OfflineMasterKey s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello - see inline
On 2/3/2016 3:49 PM, Riccardo Mori wrote:
> Hi everyone,
>
> Two months ago I decided to try the new ed25519 key introduced in
> Tor 2.7 with OfflineMasterKey set so I can keep the master key in
> a different place and just uploa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi everyone,
Two months ago I decided to try the new ed25519 key introduced in Tor
2.7 with OfflineMasterKey set so I can keep the master key in a
different place and just upload the medium-term signing key every month.
Last month everything went ok
As a follow-up on this issue: I can't easily hook up my Raspberry Pi with a
network cable, but I've had this command running for the past few days:
$ while :; do ping -c 3 www.google.com &> /dev/null; if [ $? != 0 ];
then date; fi; done
There's been occasional output that doesn't correspond to
