netdev - RE: kTLS getsockopt TLS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <DB7PR04MB4252AE898032DB6D4C49BB3C8B790@DB7PR04MB4252.eurprd04.prod.outlook.com>
Date:   Sun, 24 Feb 2019 01:50:19 +0000
From:   Vakul Garg <vakul.garg@....com>
To:     Hayakawa Yutaro <yhayakawa3720subscribe@...il.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: kTLS getsockopt TLS_RX support



> -----Original Message-----
> From: netdev-owner@...r.kernel.org <netdev-owner@...r.kernel.org> On
> Behalf Of Hayakawa Yutaro
> Sent: Saturday, February 23, 2019 10:59 PM
> To: netdev@...r.kernel.org
> Subject: kTLS getsockopt TLS_RX support
> 
> Hello,
> 
> While trying the kTLS, I found out that currently, there is no support for kTLS
> getsockopt TLS_RX which extracts receive side crypto information from kTLS
> socket. Since setting crypto information for RX side is supported, I felt
> wonder why it is not supported.
> 
> Is there any particular reason for it?

What use case do you have in mind?
Why give back state of record layer which also contains (record sequence number) to user space?

> 
> Regards,
> Yutaro