W3C home > Mailing lists > Public > public-credentials@w3.org > December 2022

Re: Google Browser/FedCM team exploring native APIs for CHAPI

From: Harrison <harrison@spokeo.com>
Date: Mon, 12 Dec 2022 11:29:47 -0800
Message-ID: <CAFYh=40eQZQxhPnDoep5vrTZ4Sa6nT7tpXRBBVDMROJ4tv=BOQ@mail.gmail.com>
To: Juan Caballero <caballerojuan@pm.me>
Cc: public-credentials@w3.org
Please feel free to ask these questions at our regular Tuesday meetings.
In addition, we've invited the Google FedCM team to present at W3C CCG
on *Tuesday

Here is a list of the upcoming discussions:


On Sun, Dec 11, 2022 at 7:11 PM Juan Caballero <caballerojuan@pm.me> wrote:

> Can we put this very issue on the agenda?  I'm a little confused myself so
> if there's time in Q&A I'd love an ELI5 on different ways/points in the
> flow diff kinds of hardware crypto might work, in present or future
> versions!
> Thanks,
> __juan
> On 11/27/2022 3:23 PM, Manu Sporny wrote:
> On Sun, Nov 27, 2022 at 6:04 PM ANTHONY NADALIN <nadalin@prodigy.net> <nadalin@prodigy.net> wrote:
> Doesn't allow hardware crypto support unless the browsers enable it by implementing CHAPI as far as I'm aware
> The Credential Handler API is about registering applications and
> routing messages to and from the appropriate applications. CHAPI isn't
> a hardware cryptography API.
> If what you mean is that you need a first party context to run
> hardware crypto, then CHAPI can run in first party mode. Another
> expectation with the FedCM interface is that you would be able to
> utilize hardware crypto. What am I missing here, sounds like we're
> either comparing apples with oranges or that there is a
> misunderstanding about how CHAPI works.
> -- manu
> --
> ------------
> Juan Caballero, PhD.
> Personal/Freelance account, opinions are not my employers', etc.
> PST/CET; Self-schedule through cal.com <https://cal.com/bumblefudge>
Received on Monday, 12 December 2022 19:30:17 UTC

This archive was generated by hypermail 2.4.0 : Monday, 12 December 2022 19:30:18 UTC