linux-kernel - Using QUIC from kernel drivers

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>] [day] [month] [year] [list]

Message-ID: <CAH2r5ms4+GyqD3VJNRXXwDsPnEWvWpqEPXqm+UiR92myiAVUww@mail.gmail.com>
Date:   Wed, 25 Mar 2020 21:56:40 -0500
From:   Steve French <smfrench@...il.com>
To:     quic@...f.org, LKML <linux-kernel@...r.kernel.org>
Cc:     ronnie sahlberg <ronniesahlberg@...il.com>,
        Jeremy Allison <jra@...ba.org>
Subject: Using QUIC from kernel drivers

We have been trying to experiment with using QUIC for access to
network file systems (Samba, Windows etc. over SMB3.1.1 over QUIC) but
cifs.ko is a kernel driver.

Are there any examples of using QUIC from Linux kernel drivers? Or
suggestions on how to do this (I didn't see any QUIC kernel drivers
yet from a "git grep" of 5.6-rc7).  Presumably worst case scenario is
that the kernel driver could upcall for the authentication phase, and
then presumably there is a better way to avoid upcalls for the rest.

There were some details on how Windows did this at the annual large
Storage Developer Conference (https://youtu.be/xUvfjZXIu9E) but was
wondering if any progress with figuring out how kernel drivers can use
QUIC.

-- 
Thanks,

Steve