3 ms·
As far as http+integrity goes: Integrity checks are also based on a shared secret, see https://en.wikipedia.org/wiki/Hash-based_message_authentication_code http
by Phemist 11y ago
As far as http+integrity goes: Integrity checks are also based on a shared secret, see https://en.wikipedia.org/wiki/Hash-based_message_authentication_code https://en.wikipedia.org/wiki/Hash-based_message_authenticat.... So for http+integrity, without the secrecy aspect of TLS, ie the hmac key being public, it would be trivial to generate your own valid integrity hash.
- wolf550e 11y agoPublic hmac key is same as posting hash of iso next to the ISO on ftp severs without gpg signature of the hash. No protection at all.
- byuu 11y agoI'm not the right person to design the entire system, obviously. But as a starting point, I'd consider using a PGP signing key on responses from a server. Your keys would be hosted on an HTTPS server somewhere. Let's say httpi.org or something. signify also looks really promising. Get the key down to the size of a QR code, and you could separate the issue of signing from signature validation entirely ... post it on your HTTPS Twitter feed, put it on your business card, whatever. I think it would be a positive step to get users to think about how they are verifying integrity themselves and the sources they trust. You could even have a dozen sources and let there be a little button in the URL bar to show you which sources agree on a public key provided by a server.