trezor-agent VS rekor

It doesn't support signing and authentication subkeys (But maybe it will soon!).

GPG "master keys" are on the Trezor, which has no mass storage. You can read more how to use if for GPG in here: https://github.com/romanz/trezor-agent/blob/master/doc/README-GPG.md. Trezor needs a PIN + passphrase typed on the device to be secure from physical attacks (Google: trezor hacked).

I use romanz/trezor-agent and it is recommended on the official trezor wiki.

it looks like someone on the github for the Trezor GPG has worked on it but I have no clue how to run this script. Here's the first link I found under the issues tab.

I'd been working with the trezor-gpg and trezor-ssh features recently, but found them difficult to configure in Windows. When I saw the WSL-2 article on usbipd, found everything worked great.

Ledger/Trezor have solved this since ~2016. I have a Ledger that has a private key inside and using a small open source tool (https://github.com/romanz/trezor-agent) I can SSH into machines, sign random data and Github commits and FIDO authenticate into several websites. All of that and knowing that these devices offer some of the best security out there.

SSH/PGP agent is a proxy application intended to work with https://github.com/romanz/trezor-agent

There could be asset hashes in sigstore: https://sigstore.dev/

Is there a good way to run native mobile app GUI tests with GitHub Actions?

A VM/container emulator like anbox, waydroid, (or all of ChromeOS Flex in KVM) in a GitHub Action is probably enough to run GUI tests?

"Build your own SLSA 3+ provenance builder on GitHub Actions"

I expect something like https://sigstore.dev

sigstore is another suite of tools that focuses on attestation and provenance. Within the suite are two tools I heard mentioned a few times at KubeCon: Cosign and Rekor.

Since we can distribute Spin applications using popular registry services, we can also take advantage of ecosystem tools such as Sigstore and Cosign, which address the software supply chain issue by signing and verifying applications using Sigstore's new keyless signatures (using OIDC identity tokens from providers such as GitHub).

With containers being the heart of Cloud Native application development, it has become even more critical to ensure the integrity of the containers. One of the ways to do this to sign and verify the container images.sigstore is a open source project that empowers software developers to securely sign the container images.

https://sigstore.dev - although its really not true to say I built it. I started it off, but very quickly smarter folks then me jumped on board and really took it to all sorts of new directions.

Powered by Wolfi, Chainguard Images are a suite of distroless images that consolidate the base features of the Wolfi undistro into end-user container images that can be integrated into existing workflows. Chainguard Images are fully declarative and reproducible, and include SBOMs that cover all image dependencies. In addition, Chainguard Images are signed via Sigstore, which attests the provenance of all artifacts. All images and corresponding signatures, as well as their SBOMs, are hosted in Chainguard's OCI registry cgr.dev.

What's your thoughts on the sigstore project from the linux foundation?