Thread (49 messages) 49 messages, 10 authors, 2024-06-28

Re: [RFC net-next 01/15] psp: add documentation

From: Lance Richardson <hidden>
Date: 2024-06-28 19:33:40

On Thu, Jun 27, 2024 at 6:33 PM Jakub Kicinski [off-list ref] wrote:
I was under the possibly mistaken impression that Google have used PSP
for years without rekeying... Did I misunderstand?
Actually Google does implement connection rekeying when master key
rotation occurs. I believe this was the case even in the first production
deployment (Willem would know the history better).
quoted
A tiny bit logic would also be needed on the Rx
side to track the current and previous SPI, if the hardware supports
keys indescriptors then nothing more should be needed on the Tx side.
If the NIC maintains an SA database and doesn't allow existing
entries to be updated, a small amount of additional logic would be
needed, but perhaps that could be (waving hands a bit) the
responsibility of the driver.
Interesting. Hm. But SADB drivers would then have to implement some
complex logic to make sure all rings have cycled, or take references.
I'd rather have an opt-in for core to delay reaping old keys until
all sockets which used them went empty at least once (in wmem sense).
Right, ensuring that the old entry is no longer referenced by packets in the
transmit pipeline before removing is definitely a concern. One simple
approach is to simply keep the old entry around for long enough (e.g. a
minute or two) to ensure that any packets referencing it have been transmitted.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help