Tech 2026-07-06 Meeting Notes

@Antonio Murdaca

Red Hat

Miguel Martin

Red Hat

Brad Goodman

DELL

Sven Uthe

Devity

1

java->go transition

• OpenHorizon has assigned an engineer to look at this

  • @LE ZHANG - updates will follow

  • Is there a potential for Open Horizon to collaborate with Dell team and divide the work?

  • Open Issues:

    • https://github.com/fido-device-onboard/go-fdo-server/issues/228

    • https://github.com/fido-device-onboard/go-fdo-server/issues/216

    • Issue #215: Feature Request: dynamically added fdo.download file

2

Deprecation of the C sdk/client

• unmaintained, too many intel’s specifics in there (add-ons, runtime/build time)

• Talk to Bryan (Intel) to check if Intel will maintain it

  • https://github.com/fido-device-onboard/client-sdk-fidoiot will be deprecated officially soon

  • TBD if Intel engineers can help maintain this.

• Move to rust if it compiles to a smaller binary

  • Brad got rust to 600k but no openssl built in

• Brad will meet with Bryan in the future for planning

• Sven uses the C library internally, there’s interest in contributing to Rust, “potentially” dropping the C library

3

go-fdo 2.0 updates

https://github.com/fido-device-onboard/go-fdo/pull/208

• https://github.com/bkgoodman/fdo-sim/blob/main/fsim-repository more generic FSIMs to be considered

• new branch vs new repo?

  • decisions:

    • move go-fdo main to v2 in go.mod

    • branch v1.1

    • v2.0 will not be compatible with v1.1

      • future releases (e.g. v3.0…) planned to support backward compat with v2.0

  • Timeline for v2.0 go-fdo

    • still TBD, but likely unable to move forward until post-June 2026

• Need: start reviewing the go-fdo library 2.0 Pull-Request

4

update on Intel’s policies to work with LF Edge’s FDO GH

Bryan to reconcile intel’s policies to work with LF Edge upstream (i.e. https://github.com/orgs/fido-device-onboard/teams/security-manager )

• in progress 03/30

• turn intel and everybody into normal contributors vs “offical Intel devs” - avoid Intel-specific policy.

5

Additional Golang FDO contributions

Potential FDO-related contributions from Brad: https://github.com/bkgoodman?tab=repositories

• Goal: move FDO applications/tools implementations to an “official” repo

  • decision TBD:

    • can these be moved into the Github FDO Alliance Org? (Action item for Antonio added)

Need: review + feedback:

• 2.0 go-fdo

• rust +2.0

• go applications - various

• non-go: UEFI “shim” compontent - enable secure firmware update, load TO2 from Rendezvous and perform signature verification of payload

6

Lifecycle for Rust Impl

https://github.com/fdo-rs/fido-device-onboard-rs

Issue: Currently marked “deprecated”, but other groups/orgs are using it.

Need:

• new maintainers and identify stakeholders and encourage them to attend this meeting.

• TBD: will maintainers support both client and server, or will only one role be maintained?

7

Community Lab Support

UNH Interopt (IOL) lab - involved with all LF Edge projects, can host infrastructure needed for the project (github runners, rendezvous servers, etc). Non-commercial.

See Wiki (meeting info, etc): Shared Community Lab

This is a resource at our disposal. Ideas for use cases TBD.

8

FIPS Compliance

Miguel reviewing FIPS compliance with respect to go implementation. Will be following up with related issues/pull requests at github. For reference:

• https://go.dev/doc/security/fips140

• https://go.dev/blog/fips140

• https://developers.redhat.com/articles/2025/03/10/benefits-native-fips-support-go-124

9

PQC

10

TPM

status of the draft specification

• as of 06/22 “feels” close, the quiet period should end in July

11

is https for to1/to2 really necessary? as implementors we can chose to just say “no” and say “fdo protocol is already secure” right? what about DI instead?

• Servers shall/must support https/http

• clients can only support HTTP