kd4e Signify isn't used as part of the current CLI install process. Use our official installation instructions instead of whatever unofficial guide you're following.
Signify Error
kd4e WebUSB does not require systemd.
- Edited
GrapheneOS
I was here:
[(https://grapheneos.org/install/cli)]
And read this ...
The current public key is signed with the previous signify key. If you already have the previous signify public key (factory.pub) and want to verify the new key with it:
curl -O https://releases.grapheneos.org/allowed_signers.sig
signify -V -m allowed_signers -x allowed_signers.sig -p factory.pub
When the current signing key is replaced, the new key will be signed with it.
- Edited
kd4e As @boldsuck mentioned, they're essentially the same chat rooms whether you use Discord, Matrix, Telegram or IRC due to the bridge. We support multiple chat platforms officially since if we don't people are still going to make communities on each of them, which would end up filled with misinformation and malicious people trying to harm GrapheneOS. By making rooms on each major platform ourselves, we avoid that situation. There's also an unofficial group on SimpleX created by some of our moderators created which cannot be official due to technical limitations which may end up being resolved in the next couple years. It was created to replace a previous unofficial group with absolutely no moderation at all which was filled with trolls and misinformation, which is how we get pushed into supporting more chat platforms.
kd4e This information is only for people who previously used the older instructions with signify and therefore already have the previous signify key which they can use to verify the newer OpenSSH key. The switch to OpenSSH signing was done in February and at some point we can remove the instructions on verifying the key rotation. If you're starting fresh, you have no use for this.
When I power on the phone while holding the volume Down - on the phone display where it shows Fastboot Mode it also shows ...
Device State: locked
In Developer options OEM unlocking is ON.
I tried turning on USB debugging and USB file transfer ... no Unlock Bootloader Screen in Web Installer.
Oh, wait, for some reason this doesn't work with Firefox - just remembered that.
Sigh, OK, I'll have to move to a different computer.
OK, got to the "Download release" step ...
Error: undefined
???
I have a good Internet connection.
- Edited
Chromium is OS sensitive?
I thought Chromium was essentially self-contained.
Why would it be able to do 'Unlock bootloader' (communicate with the phone) but not 'Download release' (communicate with the Internet)?
'Download release' would seem a generic browser activity.
I just tried and no problem downloading a .wav file from the Internet.
Could I manually download the 'release' then 'flash' it?
Oh, wait, that would loop me back to the OpenSSH signing problem ... sigh.
kd4e Chromium is OS sensitive?
I thought Chromium was essentially self-contained.
Unfortunately, many things have the ability to break other things. After a problem has been solved it may seem obvious in retrospect that what went wrong could have gone wrong.
kd4e Why would it be able to do 'Unlock bootloader' (communicate with the phone) but not 'Download release' (communicate with the Internet)?
'Download release' would seem a generic browser activity.
I just tried and no problem downloading a .wav file from the Internet.
What the installer does is not the same thing as when the browser downloads a file to store in the file system for you to use later. It is fetching the contents across the Internet, storing it in a special temporary file, and then sending the contents of the file over WebUSB.
kd4e I just tried and no problem downloading a .wav file from the Internet.
Maybe the problem is insufficient temporary space, which is something various Linux distributions configure differently.
kd4e "Error: Failed to execute 'open' on 'USBDevice': Access denied."
Most likely issue: https://grapheneos.org/install/web#flashing-as-non-root
OK, after reconfiguring the laptop setup some more it all finally worked.
Just need to swap the sim card and will be all working fine.
Thanks for the help!
I always get the error Could not verify signature
on macOS.
Found others with the same error https://unix.stackexchange.com/questions/780313/openbsds-signify-doesnt-work-on-macos-signify-osx-sonoma-could-not-verify
- Edited
Scott I always get the error
Could not verify signature
on macOS.
Here is my recent experience on Sonoma (14.5). I created a new empty directory and did this:
% curl -O https://releases.grapheneos.org/allowed_signers
[...]
% curl -O https://releases.grapheneos.org/bluejay-factory-2024071600.zip.sig
[...]
% curl -O https://releases.grapheneos.org/bluejay-factory-2024071600.zip
[...]
% ssh-keygen -Y verify -f allowed_signers -I contact@grapheneos.org -n "factory images" -s *.zip.sig < *.zip
Good "factory images" signature for contact@grapheneos.org with ED25519 key SHA256:AhgHif0mei+9aNyKLfMZBh2yptHdw/aN7Tlh/j2eFwM
If you are still getting signature failures from ssh-keygen
, can you indicate exactly which commands you are issuing?