• 1 Post
  • 1.8K Comments
Joined 2 年前
cake
Cake day: 2023年12月28日

help-circle


  • They’re probably assuming the chats aren’t encrypted because telegram doesn’t encrypt those. Source

    Multi-device End-to-end encrypted chats are a mess

    The concept of End-to-End Encryption has no limits for the number of communicating devices. However, if you want to access your end-to-end encrypted chats from multiple devices, you’re facing many technical difficulties, especially when it comes to connecting new devices, loading chat history and restoring backups.

    Most of our competitors (notably, Whatsapp and iMessage) solve these problems in ways that make their end-to-end encryption useless (this is a big topic, so requires a separate manual [poster note, that link goes to a ‘manual’ that hasn’t been filled out lol]). To solve them in a secure way, you’d have to sacrifice usability and some of the features you’re used to – the result would never be as fluent and simple as what we offer in Cloud Chats.

    Telegram says they don’t encrypt them and tries to imply that people who actually know how to use cryptography failed to solve this problem because they couldn’t solve it with their shitty self rolled ‘encryption’ algo that hasn’t been peer reviewed (unlike the signal protocol)



  • Wait wait wait wait wait wait…

    Are you trying to tell me that the activists who said for decades that legalizing would reduce youth use because it would be regulating the product and making it harder for the black market to thrive were right this whole time???

    Color me fucking shocked. Next you’re going to tell me that it was really just criminalized because of racism and the right wanting another way to attack and imprison their opponents and minorities.














  • So if they were going to do an attack like this, they wouldn’t do anything like the DH attack you’re talking about, they’d have a custom CA in the browser’s SSL root store. That root cert means they can generate a certificate for any website you visit, and that custom root cert would be how they decrypt your traffic.

    Afaik there isn’t a current attack on proper DH key pairings, but you can’t block the custom certificate path at the browser level without some serious server side work/client side JS to validate



  • Yeah, but then you give them something to complain about afterwards. Pissing them off by being kind is sooooo much more rewarding. You haven’t experienced pettiness until you’ve gotten a customer to a boiling rage by being nothing but saccharine and professional to a pissed off customer looking for a fight.

    I used to work retail cell phone sales for a now defunct reseller, and we’d frequently get people in who got pissed off when they found out we couldn’t do a lot of carrier functions, and boy was it fun winding people up by being kind, courteous and professional.

    I wasn’t as bad as the South Park ISP dudes, but same vibe lol