-
Notifications
You must be signed in to change notification settings - Fork 1
update workflow is broken #12
Comments
@ineiti the problem might be that the environment variables AUTHORITY/DIR_AUTH_PASSWORD contain a certificate that has expired there is a process described in the README.md on how to renew the certificate, but only when one knows DIR_AUTH_PASSWORD (else it will create a new certificate) - since the secrets are encrypted I cannot access either of them so I tend to "just create a new certificate" but I'm not clear on the consequences it might have if our certificate changes what do you think? |
unfortunately creating a new certificate did not resolve the issue - but at least we now have a certificate/password in our hands... |
OK, the issue seems to be that moria1's (the authority server we use) key has been changed: https://gitlab.torproject.org/tpo/core/tor/-/issues/40722 what we have:
which corresponds to the old key as seen here: so I'm currently looking into how to retrieve the authorities' new key |
so the information in question is retrieved by this ticked and c4dt/lightarti-rest#116 are blocked for the moment |
blocking c4dt/lightarti-rest#116
The text was updated successfully, but these errors were encountered: