Re: F37 Change: Support FIDO Device Onboarding (Self-Contained Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 29, 2022 at 3:25 PM Simo Sorce <simo@xxxxxxxxxx> wrote:
>
> Can we get a link to the actual software stack being proposed?
> The link in this proposal is a marketing post ...

Yes, that was an oversight, for reference:
https://github.com/fedora-iot/fido-device-onboard-rs

> On Tue, 2022-03-29 at 09:50 -0400, Ben Cotton wrote:
> > https://fedoraproject.org/wiki/Changes/FIDODeviceOnboarding
> >
> > == Summary ==
> > Package and enable the
> > [https://fidoalliance.org/fido-alliance-creates-new-onboarding-standard-to-secure-internet-of-things-iot/
> > FIDO Device Onboarding] software stack for Zero Touch Onboarding on
> > Fedora IoT.
> >
> > == Owner ==
> > * Name: [[User:pbrobinson| Peter Robinson]]
> > * Email: [mailto:pbrobinson@xxxxxxxxxxxxxxxxx| pbrobinson@xxxxxxxxxxxxxxxxx]
> > * Name: [[User:runcom| Antonio Murdaca]]
> > * Email: [mailto:amurdaca@xxxxxxxxxx| amurdaca@xxxxxxxxxx]
> >
> >
> > == Detailed Description ==
> >
> > The ability for an IoT or Edge device to be plugged in and
> > automatically onboard itself with zero user interaction is critical to
> > be able to scale IoT/Edge to millions of devices. To do this in a
> > secure way with open standards across the industry is even more
> > critical. The FIDO IoT working group has worked with leaders in the
> > silicon industry such as Intel and Arm to produce the FIDO Device
> > onboarding spec which allows a device credential, a root and chain of
> > trust to ensure the secure onboarding of a device without the need of
> > stored credentials.
> >
> > == Benefit to Fedora ==
> >
> > The benefit to Fedora is to allow the IoT Edition to demonstrate the
> > use of leading edge open industry protocols for onboarding IoT and
> > Edge devices.
> >
> > == Scope ==
> > * Proposal owners:
> > ** Package the rust implementation of the FIDO device onboarding stack
> > including client, rendezvous service, owner onboarding service and
> > prototype manufacturing service.
> > ** Enable the client service by default for IoT Edition
> > ** Add the client service to the IoT Edition deliverables
> >
> > * Other developers:
> > ** No impact
> >
> > * Release engineering: [https://pagure.io/releng/issue/10720 #10720]
> > * Policies and guidelines: N/A (not a System Wide Change)
> > * Trademark approval: N/A (not needed for this Change)
> >
> > == Upgrade/compatibility impact ==
> > There is no upgrade impact. FIDO FDO is a single use onboarding
> > protocol and will not impact existing IoT user systems.
> >
> > == How To Test ==
> >
> > * Test with FDO all-in-one services. Documentation will be available
> > for testing.
> >
> > == User Experience ==
> >
> > No impact to non IoT Edition users.
> >
> > The user experience for the IoT Edition is still evolving and this
> > will be updated as things fall into place later in Spring and early
> > Summer 2022.
> >
> > == Dependencies ==
> > N/A (not a System Wide Change)
> >
> > == Contingency Plan ==
> >
> > * Contingency mechanism: Not shipping FDO as a package in Fedora or
> > including it in the IoT Edition
> > * Contingency deadline: GA
> > * Blocks release? No.
> > * Blocks product? No.
> >
> > == Documentation ==
> > N/A (not a System Wide Change)
> >
> > == Release Notes ==
> > Fedora IoT Edition supports the FIDO Device Onboarding 1.1
> > specification for zero touch onboarding of IoT and Edge devices.
> >
> >
> > --
> > Ben Cotton
> > He / Him / His
> > Fedora Program Manager
> > Red Hat
> > TZ=America/Indiana/Indianapolis
> > _______________________________________________
> > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>
> --
> Simo Sorce
> RHEL Crypto Team
> Red Hat, Inc
>
>
>
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux