netdev - Re: quic in-kernel implementation?

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: <20210905140931.345774-1-ericcurtin17@gmail.com>
Date:   Sun,  5 Sep 2021 15:09:31 +0100
From:   Eric Curtin <ericcurtin17@...il.com>
To:     vfedorenko@...ek.ru
Cc:     aahringo@...hat.com, linux-cifs@...r.kernel.org,
        linux-nfs@...r.kernel.org, lsahlber@...hat.com,
        netdev@...r.kernel.org, smfrench@...il.com, swhiteho@...hat.com
Subject: Re: quic in-kernel implementation?

Hi Guys,

Great idea, something I have been hoping to see in the kernel for a
while. How has your implementation been going @Vadim? I'd be interested
in a non-encrypted version of QUIC also in the kernel (may not be
supported in the spec but possible and I think worth having), would be
useful for cases where you don't care about network ossification
protection or data-in-transit encryption, say a trusted local network
where you would prefer the performance and reliability advantages of
going plaintext and you don't want to figure out how to deploy
certififcates. Something that could be used as a straight swap for a
TCP socket.