Skip to content

Conversation

@k9ert
Copy link
Contributor

@k9ert k9ert commented Aug 21, 2025

The installation and update process is done with two different binaries. Both binaries contain pubkeys which makes it possible to check signatures on the device when upgrading.
This PR is removing Ben's key and it's adding k9ert's key. It gets checked with each update. That means that this PR gets relevant for new installations with a new release and for upgrades one release after.

This release is ugrading the specter-bootloader from fc6e61 to 6e727 which contains 2 PRs:

Most of the files come from the test PR in the test directory. The relevant change is in the pubkeys.c. The xpubconvert.py tool can be used to convert an xpub to the format needed in the pubkeys.c.

@netlify
Copy link

netlify bot commented Aug 21, 2025

Deploy Preview for specter-diy-docs ready!

Name Link
🔨 Latest commit a93f2f2
🔍 Latest deploy log https://app.netlify.com/projects/specter-diy-docs/deploys/68e3f42578c0e00008be117b
😎 Deploy Preview https://deploy-preview-306--specter-diy-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@3rdIteration
Copy link
Contributor

Ack

@k9ert
Copy link
Contributor Author

k9ert commented Oct 2, 2025

  • signature test would be very reasonable to have for all participants
  • Also doing an initial firmware and test an upgrade.
  • Figure out how to build a firmware which is upgrading the bootloader

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants