Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Key doesn't match TAL until restart #211

Closed
ximon18 opened this issue Sep 6, 2019 · 3 comments
Closed

Key doesn't match TAL until restart #211

ximon18 opened this issue Sep 6, 2019 · 3 comments

Comments

@ximon18
Copy link
Member

ximon18 commented Sep 6, 2019

With Routinator 0.5.1 (Docker) running create a new TAL file in the tals/ directory.
After the refresh period expires Routinator detects the new TAL file but complains in the logs:

https://some.fqdn/ta/ta.cer: key doesn't match TAL.

Yet after docker restart routinator the TAL file is accepted.

Found valid trust anchor https://some.fqdn/ta/ta.cer. Processing.
@partim
Copy link
Member

partim commented Sep 9, 2019

Routinator does not reload the TALs between validation runs. This is on purpose as it increases robustness in normal operation.

Issue #200 requests implementation of a reload via signals.

@partim partim closed this as completed Sep 9, 2019
@ximon18
Copy link
Member Author

ximon18 commented Sep 9, 2019

Should the error message perhaps be different then, e.g. "Ignoring new TAL 'xxx', please restart to load it." ?

@partim
Copy link
Member

partim commented Sep 9, 2019

It doesn’t even look at the directory ever again, so that would require extra code and whatnot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants