Solar Designer
Solar Designer
To reduce the ability of a non-root user on a system running LKRG to flood the receiver with connections, we could be making our own ones from a privileged port,...
Nov 28, 2022 This is now implemented as `LKRG_WITH_NET` defined in `net.h`. I suggest we use the `LKRG_WITH_*` naming for these things, and we might later move them all e.g....
Nov 10, 2022 When LKRG decides to panic the kernel and we have networking enabled, the panic should be deferred until after we've at least tried sending the message out....
Nov 10, 2022 Right now, clients are "authenticated" by being able to establish TCP connections from their IP address and by them having a copy of the server's public key....
Nov 10, 2022 Right now, the networking settings are only available via kernel module parameters. Maybe that's just fine, or maybe we want to (also or instead) have other means...
Nov 10, 2022 We have `msg_id` for limited replay protection. We could also include those message numbers in textual messages themselves - that way, reconnects would be apparent (`msg_id` would...
Nov 10, 2022 LKRG protects some of its most critical variables by keeping them on a read-only page most of the time. Net is currently written as a somewhat-separate module...
Nov 10, 2022 Right now, when we enable LKRG's `heartbeat`, those messages are getting to the kernel's ring buffer and are seen in `dmesg`, quickly scrolling other messages out of...
Nov 10, 2022 Right now, we're opening `/dev/kmsg` through the filesystem. Ideally, we'd do this without such external dependency. Unfortunately, there doesn't appear to be a way to open a...
Nov 9, 2022 This is needed for forward secrecy and it's a way to implement client authentication and it'd help with replay protection #306, but it has drawbacks such as...