retr0.id/media/bd23a2fb-c7a6-4…

alt text:

Goose chase meme. In the first frame, the goose asks “all the data is encrypted?” In the second, the goose chases a person, asking “encrypted how and with whose keys, motherfucker?”

@196

    • verdare [he/him]@beehaw.org
      30·
      11 months ago

      The fact that you have to enter your iCloud credentials directly into the app was a red flag.

      Security PSA: Don’t enter passwords or other secrets for important accounts directly into a third party UI. This is why we have tokens and federated login. Third parties should never see your Google/Apple/whatever credentials.

      • ALostInquirer@lemm.ee
        6·
        11 months ago

        Security PSA: Don’t enter passwords or other secrets for important accounts directly into a third party UI.

        By chance, would you (or some other passerby) happen to know how this is handled with the Lemmy apps/interfaces? I’ve been mixed on using them since I’m unclear how they’re handling this info.

        • verdare [he/him]@beehaw.org
          8·
          11 months ago

          Hmmm, that’s a good point. I did type my Lemmy credentials directly into at least two different apps. I guess it would be better if it redirected to a login page provided by my instance (Beehaw). But I also don’t consider my Lemmy account to be very critical. It’s not a huge deal if it gets compromised, as long as it’s not associated with my real identity.

          EDIT: Also, I use a password manager, so a leak of my randomly generated Lemmy password shouldn’t affect anything else.

      • unalivejoy@lemm.eeEnglish
        23·
        11 months ago

        Many chat apps actually use the Signal protocol for end to end encryption. This includes WhatsApp, Google Messages (RCS), Facebook Messenger, and Skype. iMessage doesn’t seem to use it.

        • LWD@lemm.ee
          16·
          11 months ago

          Facebook Messenger only uses it for specially marked chats AFAIK, and to initialize one you need to specifically request it. Nothing puts up a red flag like initializing one. Source (Facebook warning)

            • LWD@lemm.ee
              15·
              11 months ago

              Because the default message form is not encrypted. In order to switch to E2EE you basically shout to Facebook, “hey I’m going to start talking to this person right here, right now, and I don’t want you to know what I’m saying!”

              • AVincentInSpace@pawb.socialEnglish
                7·
                11 months ago

                oh, red flag for facebook, that makes sense.

                but then if you care about privacy why touch anything Facebook has made at all?

                • LWD@lemm.ee
                  6·
                  11 months ago

                  I’m not creative enough to come up with a good reason TBH

        • Lemongrab@lemmy.one
          9·
          11 months ago

          But we also can’t check their process since they are closed source. Also, if they can decrypt in the browser or proprietary app, then they can still read your messages. Browser is vulnerable to other attacks.

    • setVeryLoud(true);@lemmy.ca
      16·
      11 months ago

      That’s not even Nothing Chats’ biggest problem: it’s that it gets completely MITM’d by going onto some mac mini in some server farm somewhere.