client
client copied to clipboard
keybase
Verify page: "Error: no header found"
https://keybase.io/verify
When inserting a saltpack signed message, it always gives this error.
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkDbcHiZ z1KmaVGP2MwDu8W IeOGWy46RgXq0vo vyO9lixKuQEJJ5b fHHInZJvGEdYcR1 LSOPcF4y6CV5Fta acr9eYCg7nsn5Zh wvmHAXhD07xJ25i fyH9kLZUBGheVJT 0xfAUDxiCpRViPm dGwZX8zQbjPfEFd mtzEA6WMqTdOGs1 . END KEYBASE SALTPACK SIGNED MESSAGE.
Yeah, that's confusing, those pages predate saltpack and are just for PGP. We should fix it
cc: @malgorithms
Ideally, you should detect and verify saltpack, and the sign page should have a switch for pgp or saltpack.
The saltpack format is pretty cool imo, and would like to see it easier to sign and verify etc. via the browser.
Encountered this today. My use case is allowing visitors to my personal website to verify my SSH public key.
I'd also like to see the verification page support both PGP and saltpack. I want to be able to verify to my Facebook friends (or on any platform that doesn't explicitly work with the proof system) that my Keybase account is actually me by posting a signed message that they can then verify. It's important for people to be able to verify my signature and my Keybase identity without having to use and install Keybase themselves, and https://keybase.io/verify is a hugely useful tool for this kind of real world interoperability. Posting PGP keys on Facebook in particular is a pain because their formatting breaks the ASCII armor (which saltpack nicely fixes). Bonus is that it would be a tool that makes adopting Keybase much much smoother!
From the Keybase apps (desktop Crypto tools, and the new mobile Crypto tools) I can generate saltpack signatures, which the web verify page doesn't support. From the apps I also can't do anything with PGP, which would be another useful feature so that all these tools are consistent with one another. One specific flow that currently isn't possible is to sign a message on mobile (which only works with saltpack), and then allow non-Keybase users to verify it (because the verify page doesn't work with saltpack).
I ran into this issue today. The error should at least say the header is unsupported and not that the header doesn't exist.
Thought I was going crazy.. turns out it's still using PGP, thankfully google lead me here.
Another vote for this. Just started using keybase and this would definitely be helpful.
