1
Yeah. This is absolutely on purpose. What’s that hard-hitting documentary about the 2014 revolution called, it’s definitely “Ukraine on Fire” right?
- GRAND THEFT AUTO
- THE ELDER SCROLLS V: SKYRIM
- GRAND THEFT AUTO III
Wow… okay, this is good. It is really rare to see one of these lists that is actually populated with extremely influential games. That’s a good choice of metric, too. Not which ones are “great” but which ones had a lasting impact on the landscape.
- WORLD OF WARCRAFT
- PONG
I wonder if it might be good to separate by decades or generations or something. These are both obviously ground-breakingly influential and belong on the list but it seems kind of senseless to try to “compare” them.
- HALF-LIFE 2
Okay that’s a little weird. We’re getting up into the real high-water heights here and I mean HL2 is good but…
- KINGDOM COME: DELIVERANCE 2
Guys? You okay? I haven’t played it but it seems unlikely that it needs to be above WoW and Dark Souls.
- MINECRAFT
- THE LEGEND OF ZELDA: OCARINA OF TIME
- HALF-LIFE
Okay, here we go. You guys found your stride again. These are legit choices yes.
- SHENMUE
THE FUCK WHY WHAT
Because it is transparently obvious that it's going to happen.
If you're sending your users' private statuses to an ActivityPub server, and just hoping that it's going to choose to keep them private according to certain parameters even though that's not what the spec stays it needs to do, then you're fucking up. The fact that we know that particular instances of particular software are exposing them is a nice demonstration of the harm, a confirmation that you're fucking up when you're doing that, but it's not really needed. It is the absolutely predictable result of some basic principles of security which, as a security researcher, you should absolutely be aware of.
I've repeatedly explained this. You've repeatedly explained your position. We've both had our say. You seem addicted to the concept of "winning" the conversation and wanting to just go back and forth. In that case I would really encourage you to state your position again, and I can state mine again, and we can both have fun doing that for a while. Want to? It sounds like a productive use of both of our time. It's fun, too.
Edit: Actually, I didn't even realize you are on fedia.io when I was typing this. You can test for yourself whether mbin does this, too, by coordinating with @Irelephant@lemm.ee. Follow his user, then have him post one of those private statuses, then fetch his user profile via fedia.io from an incognito window and see whether the private statuses show up. I have no idea whether they will, but if I had to guess, I would say it's better than even odds.
https://news-pravda.com/ posts multiple stories every minute, as far as I can tell just at all times. Something like this seems fairly likely.
Are you hoping to restart our disagreement through sheer passive-aggressiveness? Okay, sure.
In my view, this is a Mastodon design flaw (or a user-expectation issue or whatever you want to call it.) I already said that, and you're involved in the unproductive-arguer's pastime of pretending not to understand that that's my position, and just aggressively repeatedly reframing things according to your position and hoping I'll knuckle under to it through sheer force of repetition.
I'm not super invested in trying to track down each and every software that might manage to expose the "private" statuses in this way. I just know that as things come and go there are guaranteed to be some. If you have an mbin account and Mastodon account, though, we can try a little experiment. I don't know the outcome, I'm just curious after taking a quick look down the FediDB list and a quick grep through mbin's source code. You can be the one to responsibly disclose to mbin how their ActivityPub-conforming behavior is a problem, if indeed it turns out that it is, since you seem to be extremely committed to the idea that the model of "vulnerability" needs to be applied to this particular ActivityPub-conforming behavior. Since you're a security researcher, having that as a CVE you discovered can be an achievement for you. It's all yours, you can have it.
Hm... maybe. The exact nature of the problem in Pixelfed means that anyone with a Pixelfed account on a server which is getting private statuses can choose to follow someone who's set to "approve followers" and then read all the private statuses. I do see how that's significantly worse than just the normal lay-of-the-land of the problem, which is a little more random, and laying that out as a little roadmap to read someone else's private statuses before there's been a nice responsible length of time for things to get fixed could be seen as worsening the problem.
The point that I'm making is that anyone who's posting private statuses to Mastodon and expecting them to stay private is making a bad mistake already. The structure of the protocol is such that they can't be assured of staying private regardless of what Pixelfed did or even if Pixelfed didn't exist. They're getting federated to servers whose behavior is not assured, in a way where a conformant ActivityPub implementation can expose them. People who are posting private statuses need to understand that.
That whole blog post where the person is talking about her partner writing private statuses, and then the gut-wrenching realization that they were being exposed on Pixelfed... but then the resolution being "Pixelfed fucked up I hate Dansup now" and then continuing to post the private statuses, is wrong. That person's partner needs to stop treating their private posts on Mastodon that way. The timer for responsible disclosure started circa 2017 or whenever Mastodon decided on how to implement their private statuses. It's been and gone.
Like I say, I get the harm-reduction aspect of saying it would have been better if Dansup was a little more discreet about this particularly bad attack vector until a few more days went by for everyone to upgrade. But it hardly matters. There are still server softwares our there that are going to be exposing people's private Mastodon posts. It's just how federation between untrusted servers works. Giving people the illusion that if Dan had just been more discreet then this harm would have been reduced is lulling them into a false sense of security, in my view.
Maybe I’m wrong, but shouldn’t posts only be insecure if they’re propagated to the insecure instance?
"Insecure" in this case simply means any server that doesn't implement Mastodon's custom handling for "private" posts. With that definition, the answer to your question is yes. It has been mentioned by Mastodon people that this is a significant problem for the ability to actually keep these private posts private in the real world. The chance of it going wrong is small (depending on your follower count) but the potential for harm is very large. I would therefore go further, and say that it's a very bad thing that Mastodon is telling people that these posts are "private" when the mechanism which is supposed to keep them private is so unreliable.
https://github.com/mastodon/mastodon/issues/712
Is any private post visible to people on servers that the poster doesn’t have followers on?
It is not. If you're sufficiently careful with approving your followers, making sure that each of them is on an instance that's going to handle private posts the way you expect, then you're probably fine.
Could I curl the uri of a post thats “private” and get the post’s content?
If it's been federated to an insecure server then yes. If not then I think no.
Yeah, you said that stuff before and then you said it again. I do understand what your argument is here. I was trying a couple of different ways of explaining what I was saying in response, but it seems like it's not working. Oh well.
I’ve said nothing about any spec violation. That’s not relevant.
It has everything to do with ActivityPub since if you follow that protocol strictly you will cause this behavior.
That's what I was going by. I guess I could re-read this now and interpret "this behavior" as Pixelfed's side, instead of Mastodon's side as I initially read it, and decide that you are agreeing with me that Mastodon's behavior was (and is) out of spec? Do I have that right?
It still doesn’t change that Dansup was told that this caused Bad Things™ and yet he didn’t follow normal procedure in how you handle it.
It is normal procedure to fix a bug when you are notified about it.
The design flaw in Mastodon that managed to bite Pixelfed in this situation still exists. People were writing about it back in 2017 when this was all being first implemented. The idea that "normal procedure" needs to include keeping it a secret that Mastodon's "private" statuses can be exposed by any server software that doesn't handle them in the way that's expected, is 100% wrong.
I'll rephrase what I said earlier: Since you're a security researcher, and you apparently think Dan should have played into the idea of keeping it a secret that Mastodon's private statuses are not secret by obfuscating the information about how he was fixing Pixelfed to more effectively hide them, you are bad at your job. In this instance. The fault lies with how private statuses are implemented, and nothing about that needs to be kept secret as would a normal vulnerability, during responsible disclosure. In fact, it is extremely harmful to let users believe that these privacy settings are anything other than vague recommendations, specifically because of the risk they will act accordingly and expose some of their private posts to the world. They should know exactly what's going on with it, and Dan accidentally failing to keep that a secret is in no way causing bad things.
It is to the person who discovers the vulnerability. That's fairly normal... how would giving it to someone else motivate the result they're trying to get?
Okay. What part of the spec did Pixelfed violate? Where in the spec is Mastodon's implementation of private posts justified?
1
Vance’s posturing in Greenland was not just morally wrong. It was strategically disastrous.
(www.theguardian.com)
Zero Punctuation as usual gets to the heart of the matter very effectively: https://youtu.be/g4Dw0Z2Dsts
That’s for Shenmue 3. He actually made a separate video reviewing the original, but that one covers more of the history and context. TL;DR It has a devoted cult following of people who basically want a very specific type of gaming experience, but the specific game that was the first to give it to them just objectively is not very good at all as an interactive video game, which is why it has never been all that popular outside that little following. Some people trace to Shenmue the lineage of huge cinematic games that emphasize narrative, which I guess could be valid, but even a super-charitable reading shouldn’t put it anywhere near the coveted number 1 spot.
Oh, you know what happened? I just realized, I hadn’t even read the introductory material and realized it was from a public survey. It’s a “first past the post” problem. Plenty of people had various lists of games they felt passionate about (and you can tell where the boundary is where “I played this game recently and I love it now so it is my favorite” started to distort the placement of some recent games), but anyone who had Shenmue anywhere on their list put it as the number 1 spot. And so, it won by bad voting algorithm. I can almost guarantee that each respondent was only allowed a single choice for most influential game.
I actually think the list, with some exceptions, is remarkably accurate. It definitely isn’t perfect. There are also some big omissions, notably in old PC games that had a big influence or fleshed out new genres that have mutated since then, or gone extinct or something. I think they’re just outside of too many people’s memory at this point.
Off the top of my head: