Lines Matching refs:decryption

22    latency on socket reads (decryption only starts when a read syscall
54 On the receive side if the device handled decryption and authentication
59 request, records are retrieved from the socket and passed to decryption routine.
60 If device decrypted all the segments of the record the decryption is skipped,
61 otherwise software path handles decryption.
180 decryption, authentication for each record in the packet). The device leaves
189 and takes care of partial decryption.
284 arrive continue decryption. Finally when 2 arrives it's completely outside
286 handling. ``ktls`` software fallback handles the decryption of record
324 At this point the device is in sync and can resume decryption at next
382 decryption is not advised. In other words either all records in the packet
388 decryption and authentication errors, packets with errors must simply not
432    decryption.
484 fallback cleanly to software decryption (RX).
537 Similarly, device-offloaded TLS decryption implies doing RXCSUM. If the user