Skip to content

Conversation

@messede-degod
Copy link
Contributor

  • Allows CT index to persisted.
  • CT indexes are dumped to disk every 30 seconds
  • Future sessions resume from last saved CT index.

@d-Rickyy-b
Copy link
Owner

Thank you for your contribution :) I appreciate it a lot. I left some comments on the code. Feel free to reply and/or fix.

@messede-degod
Copy link
Contributor Author

I've addressed all your comments, please do take a look and let me know what you think.

@messede-degod messede-degod changed the title Ability to persist CT indexes and resume from the save index file Ability to persist CT indexes and resume from the saved index file Jan 17, 2025
@d-Rickyy-b
Copy link
Owner

Quick update: I did not forget about this PR, I just had a lot of life going on. Tonight I thought about this PR a bit, and some things need a few more thoughts.

  • start_at_latest_sth and resume_from_ct_index_file should be mutually exclusive, shouldn't they? So why have two variables?
  • There should be a final save on exit. For that we need some signal handling (Gracefully shutdown certstream-server-go #50). I'll add that in a separate commit on master. For now let's just assume that the Stop() function of the ct-watcher gets called on a graceful shutdown
  • The index file should be auto-created if it doesn't exist yet
  • If no setting is defined, the default should be to use the latest STH

I'll add these missing features asap

@d-Rickyy-b d-Rickyy-b force-pushed the feat/ct-index-save-restore branch from 9d6d11f to 4bfea45 Compare May 5, 2025 00:38
@d-Rickyy-b
Copy link
Owner

Sorry for the force push. Was the easiest way to get the rebase done. This PR should now be ready to be merged. Mind taking a look at the new changes and stating your opinion? Thanks a lot!

@messede-degod
Copy link
Contributor Author

looks great, but i have to admit that it looks nothing like what it started off as 😄 .

@d-Rickyy-b d-Rickyy-b merged commit bf24abb into d-Rickyy-b:master Aug 1, 2025
3 checks passed
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

Successfully merging this pull request may close these issues.

2 participants