Am Freitag, 8. Dezember 2017, 12:39:06 CET schrieb Jonathan Cameron: Hi Jonathan, > > As a heads up, the other nasties we've found so far are around hitting > limits on the various socket buffers. When you run into those you can end > up with parts of the data to be encrypted going through without it being > obvious. > The entire code uses sock_alloc to prevent user space to chew up kernel memory. I am aware that if you have a too low skb buffer limit, parts of the cipher operation will not succeed as a malloc will fail. But that is returned with an error to user space. If you observe such an error, the entire message you wanted to read with recvmsg must be considered tainted (i.e. you do not know which part of the message has been encrypted or not). Thus, the recvmsg must be invoked again on the same buffer sent to the kernel if you want to ensure you encrypted the data. Could you please help me understand where that functionality fails? PS: If you want to give more memory to your sockets, you have to tweak /proc/ sys/net/core/optmem_max. Ciao Stephan
