MrTolkinghoen

This. Just make Europe a bunch of puppet states.

Then, when you destabilize them or ruin the country, wreck the economy, oppress the people whatever else, it isn't your country. It's this other country and your people don't care (as much) that a bunch of neighbors across the way are fighting for their lives to regain their freedom.

All the weakness and oppression strengthens the countries not going through that.

Google continues to do everything they can to close android down and force everyone to use their os directly. Imo this is a direct attack on graphene OS and anyone based on aosp. Now for every release developers will have to manually merge basically an unusable mess of changes.

Edit: https://discuss.grapheneos.org/d/21231-google-will-develop-the-android-os-fully-in-private Might not change anything actually.

Seems like graphene is already merging based on tags vs individual commits. It's also not like google is letting anyone (graphene) merge commits into android.

Iirc the graphene developers have basically given up on up streaming some changes because google doesn't actually want many of the security fixes/ changes graphene devs make. Their faq still says they'll try to upstream stuff, I wonder if this will impact that. https://grapheneos.org/faq#upstream

Lol

"incriminating" to be clear here, criticism of a political person should not cause you to be denied entry. That's fucking insane. On the other hand, yes. Everything has to be encrypted, locked, and def have a dummy OS. I'm going to need to set some up.

Right

So you're saying, that a private key within the TEE expired... So they probably had to write a custom TEE program in-order to rotate it? Along with actually securely delivering it.

So... Did we (someone) manage to capture it? Ultimately though each device is going to have to request a new key, so even with a jailbroken TEE you're still only going to be capturing the key for that specific device. The key would be how they implemented the verification that an expired device was allowed to get a new key and that verification.. Idk not an expert in widevine keys and such but I assume that cert chain expired.

Edit: sounds like it wasn't the factory key that expired, just a system level intermediate CA but updating it was still a PITA because of all the cert expiration checks by all the apps. I.e. Google home. Feel free to correct me if I'm incorrectly summarizing. (https://www.reddit.com/r/Chromecast/comments/1j8wtxa/heres_why_a_fix_is_taking_so_long/) Obligatory 🖕 reddit.

I actually can't believe how long this took them to fix.

End tax exempt status for all religious organizations. Full stop.

No. It is supportive. You are normalizing removing a gender stereotype. I.e. instead of saying my wife/husband which inherently brings a gender, and then also stated sexuality, you say partner, removing the gender statement. In so doing, you both help defend others to also be able to say it without forcing them to share their sexuality while also normalizing the removal of an over emphasis on gender with something that doesn't fucking matter.

I really haven't seen any details. Most comments I've read indicate they think you already have to have access to the device and that this is just undocumented opcode calls. I.e. not a remote Bluetooth stack issue or remotely exploitable.

Given an opcode, as noted in the article (vague on details) and yes, I did read it. This doesn't give me much cause for alarm.

"don't worry, nothing to see here. our genocide(s) isn't as bad as your genocide(s)."

Thanks for the rec. Ngl for something like sms though, maybe not maintained isn't a problem. Heh as long as it doesn't have any bugs, not like the protocol is changing