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

Flesh out alert blocks #19

Open
kpcyrd opened this issue Jan 20, 2018 · 0 comments
Open

Flesh out alert blocks #19

kpcyrd opened this issue Jan 20, 2018 · 0 comments

Comments

@kpcyrd
Copy link
Owner

kpcyrd commented Jan 20, 2018

Alert blocks exist in the current implementation, but are currently not fully implemented.

The purpose of an alert blocks is:

  • include bytes of the event
  • act as an rekey block which destroys the old session signing key
  • mark the block as incident

Currently, every info block triggers a second rekey block, since there's no other way to periodically rekey without explicitly triggering rekeys with tr1pctl rekey. I think there are some usecases where not every info block should rekey for performance reasons, but info blocks should be able to act as rekey block as well.

Alert blocks would be more useful if there's a framework that allows triggering actions with alert blocks, so certain events trigger the execution of a script. For sandboxing reasons, this command needs to be executed from a separate process. This could be combined with #18.

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

No branches or pull requests

1 participant