Skip to content
This repository has been archived by the owner on Oct 11, 2024. It is now read-only.

Pruning? #1015

Open
idibidiart opened this issue Jul 10, 2018 · 1 comment
Open

Pruning? #1015

idibidiart opened this issue Jul 10, 2018 · 1 comment
Labels

Comments

@idibidiart
Copy link

Hi,

Any plans to support pruning?

For example, for keys that have not been accessed in 10 years?

See this: https://groups.google.com/forum/#!topic/certificate-transparency/tsZsUP0Lxk8

I assume all docs are in sync with the master branch?

@gdbelvin
Copy link
Contributor

gdbelvin commented Sep 5, 2018

Hi,

Pruning is something we're thinking about. Trillian Logs are typically sharded by the expiry of certificate certificates so they have a natural end of life. Trillian Maps are still evolving a bit, but something analogous would be desirable. eg. The history for the Trillian Map could stop returning responses for tree revisions X number of years in the past.

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

No branches or pull requests

2 participants