BridgeAuth goes offline when it has an expired ed25519_signing_cert
However, Roger says in IRC that the BridgeAuth doesn't use (or shouldn't be using) this key, since it's only for v3 DirAuths.
Activity
changed milestone to %Tor: 0.3.2.x-final in legacy/trac
added component::core tor/tor in Legacy / Trac milestone::Tor: 0.3.2.x-final in Legacy / Trac priority::medium in Legacy / Trac resolution::not a bug in Legacy / Trac severity::normal in Legacy / Trac sponsor::M-can in Legacy / Trac status::closed in Legacy / Trac tor-bridgeauth in Legacy / Trac tor-dirauth in Legacy / Trac tor-ed25519-keys in Legacy / Trac type::defect in Legacy / Trac labels
Ah ha -- no, it's the authority_signing_key that I said was only for v3 auths. And I still think that's true.
But the ed25519_signing_cert file is for every relay. It has nothing to do with your bridge authority status in particular.
You have a relay whose signing key (for the relay, not for any authority thing) has just expired. I guess that means you made your relay identity key in an offline way? You need to do whatever the process is for generating a new signing cert from your ed25519_signing_secret_key.
mentioned in issue legacy/trac#23254 (moved)
moved from legacy/trac#23253 (moved)
added Bug label and removed 1 deleted label
