Tim Bruijnzeels
Tim Bruijnzeels
The RCs until now only keep the parent's public key because that is all that is strictly needed and if we keep the IdCert there is a small risk that...
- [x] rename types for clarity - [x] RoaConfiguration with optional comment - [x] Use RoaConfiguration in updates through API - [x] Add/revise Event for def with comment - [x]...
- [ ] Prep / review documentation - [ ] Release krill-manual just before this release so that the documentation links will work - [ ] GitHub release - [...
It looks like some features are intended to be mutually exclusive but this does not work well with `--all-features`. E.g. default config functions.
Typically there will be only one ROA object - assuming that resources are all held under 1 resource class, or at least do not occur in multiple classes. But, conceptually...
Update `Csr::construct_rpki_ca` in rpki-rs to return a Csr so that we don't have to re-parse it. Then use it here.
In case the parent decided to change the URI of a CA certificate (eg they migrated to a new repository) - it would be desirable to re-issue everything so that...
It would be good to support a graceful server shutdown where, after receiving sigint/sigterm: - shutdown task is added to the scheduler - access to the API is disabled (perhaps...
Use the RRDP support from rpki-rs instead of api::rrdp etc. This will allow us to simplify the code and remove the dependency on the xml lib.
Negative numbers are now allowed in some places (i64 vs u64) - even if they don't make sense. Theoretically this allows users kill their own Krill instances by using negative...