tr1pd
tr1pd copied to clipboard
kpcyrd
tamper resistant audit log
Sessions have been added recently to address the previous init block of a specific block with the `@` syntax. It would be useful to list all sessions.
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...
It would be useful to transfer blocks between systems for eg. backups: - `tr1pctl send @.. | ssh foo tr1pctl recv` - would transfer the blocks of the current session...
Encryption is currently out of scope and needs to be done in a different layer if needed by encrypting the data before passing it to `tr1pctl write`. Since the blocks...
Especially since binary support was introduced, it might be needed to tag messages and filter messages by tags when printing them. The interface would be along the lines of: ```...
- [ ] tr1pd(1) - [ ] tr1pd.toml(5) - [ ] tr1pctl(1) - [ ] tr1pctl-from(1) - [ ] tr1pctl-fsck(1) - [ ] tr1pctl-get(1) (subject to change) - [ ]...
- [ ] tighten down seccomp, especially for tr1pd - [x] introduce chroot with capabilities to chroot into /var/lib/tr1pd after the socket has been setup #4 - [x] drop all...
There should be a somewhat complete integration test that is executed by travis to ensure seccomp is compatible with various libc implementations and distributions - [ ] busybox-glibc (used in...
There's currently no interface to read blocks as soon as they are written. A tail -f style interface would be useful.
The original prototype had a hard limit for the block size by limiting the len field to an u16. This caps the number of bytes that can be signed at...