• 148 Posts
  • 930 Comments
Joined 7 months ago
cake
Cake day: February 10th, 2024

help-circle

  • Discord’s audio and video end-to-end encryption (“E2EE A/V” or “E2EE” for short)

    That last bit is a little concerning. E2EE is widely understood to mean full end-to-end encryption of communications, not selective encryption of just the audio/video bits while passing the text around in the clear. If Discord starts writing “E2EE” for short when describing their partial solution, it is likely to mislead people into thinking their text chats are protected, or thinking that Discord is comparable to real E2EE systems. They aren’t, and it isn’t.

    We want an E2EE A/V protocol that is publicly auditable

    Their use of the word “auditable” here is also concerning. What does it mean for a protocol to be auditable? Sure, it’s nice that they’re publishing their design, but that doesn’t allow independent audit of the implementation that actually runs on their servers and (importantly) people’s devices. Without publicly auditable code that can be independently, built, run, and used instead of the binaries they provide, there’s no practical way to know that it matches the design that was reviewed. And even if code is made available, without a way to verify that the code being run is the code that was inspected, any claim giving the impression that the system was audited is misleading at best.

    During the rollout phase, a single non-supporting member being present forces the call to transport-only encryption. The call will automatically “upgrade” to E2EE if that member disconnects.

    This sort of thing has historically been ripe for abuse. (See also: downgrade attack.) I hope they are very careful about how they implement it.

    The protocol uses Messaging Layer Security (MLS) for group key exchange

    Interesting. This makes me wonder if their motivation might be eventual compliance with the European Digital Markets Act. If that is the case, perhaps they also have a plan in the works for protecting text chats?

    My early impression, based on what they wrote:

    This won’t fix Discord’s major fundamental flaws. However, if their E2EE A/V design holds up to scrutiny, and if they were to fix their problematic language and provide truly auditable client code, the protection offered for audio & video could at least reduce Discord users’ exposure to unwanted harvesting of voice & face samples. A step in the right direction, and a timely one, given that biometric data collection and AI impersonation are on the rise.









  • We could quibble about the details, but all of them are fundamentally last-man-standing competitions.

    The Hunger Games was indeed one of them. I didn’t mention it because it’s the most obvious one in current cultural memory (no need for me to point it out) and because Battle Royale came a decade earlier, and Battle Royal half a century before that. The characters’ situation is probably older than printed words.

    Even if a competitive game format was unique to the Hindi film, it would be tough to argue that nobody else could have thought of that detail when making their own variation of the same theme. Calling it a “blatant rip-off” of Luck (2009) is quite a stretch.

    (Incidentally, the Luck synopsis that I read says it focuses on gambling, not competitive trials or children’s games. A quick look at the video confirms it.)








  • https://en.wikipedia.org/wiki/Internet_Draft

    I think it’s pretty clear that IETF drafts are not what author meant when he wrote draft, and I’m pretty sure the IETF doesn’t have much to do with C++ standards.

    Are you under the impression that there is no other sense of the word?

    It might help you in the future when you are discussing things like drafts, specifications, and proposals.

    As it turns out, I have done more than a little of that. Thankfully, I don’t usually see such condescending remarks in the process, nor such insistence on misunderstanding. Good luck to you, too.





  • mox@lemmy.sdf.orgOPtoProgramming@programming.devSafe C++
    link
    fedilink
    arrow-up
    8
    arrow-down
    8
    ·
    edit-2
    5 days ago

    this is yet another competing standard of static analysis.

    No, it isn’t.

    Those are linters. They might or might not discover problematic use of unsafe language features lurking in existing code.

    This proposal is a new iteration of the language and standard library. It would provide safe language features for preventing such problems existing in the first place.