@mjg59
I don't have the nuance of whomever you're replying to, so broadly:
(Approximately) no one complains about Yubikeys, datacenter HSMs, etc., because context matters. FIDO deployment wasn't going to lead to controlling what computers you can use the web with. But Google's ReCAPTCHA replacement has as a specific tactic to stop people operating outside the phone duopoly from using portions of the web.
And it probably won't even be good at their alleged goal: https://bsky.app/profile/retr0.id/post/3mljwh4k4k225
@mjg59 Ah OK, yeah I can't go so far as to oppose all attestation yet. If you had to bring up "free software gets used in weapons, ya know", I can only imagine.
Where I sit right now: Yubikeys and secure elements are pretty good. Google Play Integrity is bad.
@mjg59 Fair point. My brokerage restricted by key vendor too.
But certain implementations of attestation are going to bias more towards particular uses. Yubikeys are *mostly* (to me) good. I think Google Play Integrity, because it is flaky for security yet effective for control, is mostly bad. That's why I argue against this particular "technology" or at least implementation of it.
I can't tell if I'm arguing something you disagree with though :).
@mjg59 I don't know if you are subtooting this, but this threas broadly summarizes my experience:
https://grapheneos.social/@GrapheneOS/116550899908879585
As someone with an infosec background, I am of course highly intrigued by the tech and what it *theoretically* enables. But my experience with big tech so far has been: if a technology is widely deployed and has the potential to strengthen their monopoly, it will be used for that sooner rather than later.
Apple and Google are gradually expanding their use of hardware-based attestation. They're convincing a growing number of services to adopt it. Google's Play Integrity API and Apple's App Attest API are very similar. Apple brought it to the web via Privacy Pass, which Google intends on doing too.
@mjg59 The fixation on this topic may come from the fact that there is no turning back on this one once hardware attestation is baked into everone's personal devices.
I see a lot of advantages if I am the attesting party, instead of being the attested party (i.e. your signal use case vs GrapheneOS's Google/Android issue). But again, Google started by letting users attest their own boot chain and is now continuously switching to a Google-only solution.
@stark @mjg59 it's very difficult to determine if someone is breaking the GPL when they use (my) free software unless they are actively boasting about it. It would be even harder to enforce a no kill license, most of the military users of my software would claim they were using it defensively and it would be impossible for me to check, even with friendly nations like Germany, Finland and the UK. With hostile nations like North Korea I don't think I'll ever find out how they use it.
1/n
@stark @mjg59 I wrote up my thoughts about this a while back
https://blog.ianturton.com/foss/2022/03/11/open-source.html
Basically, it boils down to there's nothing I can do about it, my software is dual use and mapping has been a function of the military and or state enforcement of taxation since the beginning.
A no war license would perhaps deter my friends, but it would hardly deter their enemies.