The analogy would be to Cargo: `cargo fmt` just runs `rustfmt`, but you can also run `rustfmt` separately if you want.
The analogy would be to Cargo: `cargo fmt` just runs `rustfmt`, but you can also run `rustfmt` separately if you want.
Deleted Comment
How is it a fallacy? The rate of account compromises is a real metric that is affected by how good security there is for accounts.
Yes, the rate of account compromises is a metric we can define. But attestation doesn't directly or invariably improve this metric. It may do so in some specific scenarios, but it's not universally true (unless proven otherwise, which I highly doubt). In other words, it's not an immediate consequence.
It could help to try to imagine a scenario where limited choice can actually degrade this metric. For example, bugs happen - remember that Infineon vulnerability affecting Yubikeys, or Debian predictable RNG issue, or many more implementation flaws, or various master key leaks. The less diverse the landscape is, the worse the ripples are. And that's just what I can think of right away. (Once again, attestation does not guarantee that implementation is secure, only that it was signed by keys that are supposed to be only in possession of a specific vendor.)
Also, this is not the only metric that may possibly matter. If we think of it, we probably don't want to tunnel vision ourselves into oversimplifying the system, heading into the infamous "lies, damned lies, and statistics" territory. It is dangerous to do so when the true scope is huge - and we're talking about Internet-wide standard so it's mindbogglingly so. All the side effects cannot be neglected, not even in a name of some arbitrarily-selected "greater good".
All this said, please be aware that I'm not saying that lack of attestation is not without possible negative effects. Not at all, I can imagine things working either way in different scenarios. All I'm saying that it's not simple or straightforward, and that careful consideration must be taken. As with everything in our lives, I guess.
Attestation provides a guarantee that the credential is stored in a system controlled by a specific vendor. It’s not “more” or “less” secure, it’s just what it literally says. It provides guarantees of uniformity, not safe storage of credentials. An implementation from a different vendor is not necessarily flawed! And properties/guarantees don’t live on some universal (or majority-applicable) “good-to-bad” scale, no such thing exists.
This could make sense in a corporate setting, where corporate may have a meaningful reason to want predictability and uniformity. It doesn’t make sense in a free-for-all open world scenario where visitors are diverse.
I guess it’s the same nearsighted attitude that makes companies think they want to stifle competition, even though history has plenty of examples how it leads to net negative effects in the long run despite all the short term benefits. It’s as if ‘00s browser wars haven’t taught people anything (IE won back then - and where is it now?)
I understand the value of attestations in a corporate environment when you want to lock down your employees' devices. But that could simply have been handled through a separate standard for that use case.
There are such licenses. They are just not open source.
There are such licenses only if you change the definition of "freely" to fit the narrative. Historically, "freely" (as in "free software") means granting end-user four essential software freedoms:
- The freedom to run the program as you wish, for any purpose (freedom 0).
- The freedom to study how the program works, and change it to make it do what you wish (freedom 1). Access to the source code is a precondition for this.
- The freedom to redistribute copies so you can help others (freedom 2).
- The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.
If I can't redistribute ("resell") software, or can't run it and let others access it for a fee - it's not "use freely" anymore.
This was briefly possible with WebUSB, but all mainstream browser vendors have a stoplist of certain USB devices for security reasons.
a) AI is a bubble
b) It's about to burst
This is based on a study that "just 5pc of integrated AI pilots are extracting millions in value, while the vast majority remain stuck with no measurable P&L [profit and loss] impact".
I think the conclusions (while possibly true) are not supported here. By comparison, in the stock market in general, just a handful of stocks provide most of the returns over the past few decades. This does not mean the stock market is a bubble or about to burst.
It's the kind of "AI" I see when I walk by the TVs at Costco and see that every box that used to feature the word "smart" now has "AI" prominently written on it, even though in practice no one knows for sure what it possibly means or does. In this sense - sense of companies slapping "AI" (whatever it means to them) for the sake of having "AI" looks like a bubble/fad/hype.
I have no idea about any possible economical outcomes of that hype declining (for a better term than "bubble" "bursting"), but I'm skeptical it's gonna be anything huge. My whole life I've seen endless examples of companies realizing their "hot topic" marketing strategy stopped working (or never worked at all) and they just pivot for different strategies without any severe impacts. As long, of course, as the company had actually useful product and the issue was merely with the marketing.