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: <nycvar.YFH.7.76.2407240119140.11380@cbobk.fhfr.pm>
Date: Wed, 24 Jul 2024 01:22:14 +0200 (CEST)
From: Jiri Kosina <jikos@...nel.org>
To: James Bottomley <James.Bottomley@...senPartnership.com>
cc: Dan Williams <dan.j.williams@...el.com>, ksummit@...ts.linux.dev, 
    linux-cxl@...r.kernel.org, linux-rdma@...r.kernel.org, 
    netdev@...r.kernel.org, jgg@...dia.com
Subject: Re: [MAINTAINERS SUMMIT] Device Passthrough Considered Harmful?

On Tue, 23 Jul 2024, James Bottomley wrote:

> That's not entirely true.  FIDO tokens (the ones Konstantin is
> recommending for kernel.org access) are an entire class of devices that
> use hidraw and don't have a kernel driver.  There's an array of
> manufacturers producing them, but the CTAP specification and its
> conformance is what keeps a single user mode driver (which is now
> present as a separate implementation in all web browsers and the
> userspace libfido2) for all of them.  

Agreed, but that pretty much underlines my point though.

The ecosystem didn't get shattered as a result of me having created 
hidraw.

libfido2 is on pretty much everyone's machine now (at least for those who 
need it), and people are using that all the time to authenticate to 
kernel.org/Google/Okta/whatnot. No workflow got broken in the process.

-- 
Jiri Kosina
SUSE Labs


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ