Privacy

41400 readers

492 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
Don't promote proprietary software
Try to keep things on topic
If you have a question, please try searching for previous discussions, maybe it has already been answered
Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
Be nice :)

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

Does Google keep logs of my text messages(RCS)? (sh.itjust.works)

submitted 2 weeks ago by unicornBro@sh.itjust.works to c/privacy@lemmy.ml

28 comments fedilink hide all child comments

In the past, I've heard about how Google can keep records of all your Google phone's past locations and text messages.

What about RCS messages which supposedly are encrypted from Android to Android? I know that it's possible that they secretly keep a log behind the scenes, but as far as the regular consumer knows is there any record being kept with regard to the contents of these RCS messages?

you are viewing a single comment's thread
view the rest of the comments

[–] EveryMuffinIsNowEncrypted@lemmy.blahaj.zone 1 points 1 week ago (1 children)

You are clearly misunderstanding me.

If the keys are stored server-side, that means it's stored by either the "sender or recipient". The server is among those two options.

[–] artyom@piefed.social 1 points 1 week ago (1 children)

I am not misunderstanding you. You just do not understand what E2EE means. Th server is not a sender or a recipient. It is not an "end".

[–] EveryMuffinIsNowEncrypted@lemmy.blahaj.zone 2 points 1 week ago* (last edited 1 week ago)

Okay, so, originally, I was going to look it up to prove you wrong, but after looking it up across multiple sources, it seems that you're right and I'm wrong.....mostly.

How-To Geek, Proton, and CloudFlare all mirror what you say.

However, the Wikipedia page section "Definitions" does back me up somewhat. It says:

The term "end-to-end encryption" originally only meant that the communication is never decrypted during its transport from the sender to the receiver.[23] For example, around 2003, E2EE was proposed as an additional layer of encryption for GSM[24] or TETRA,[25] ... This has been standardized by SFPG for TETRA.[26] Note that in TETRA, the keys are generated by a Key Management Centre (KMC) or a Key Management Facility (KMF), not by the communicating users.[27]

Later, around 2014, the meaning of "end-to-end encryption" started to evolve when WhatsApp encrypted a portion of its network,[28] requiring that not only the communication stays encrypted during transport,[29] but also that the provider of the communication service is not able to decrypt the communications ... This new meaning is now the widely accepted one.[30]

(Relevent text is embolded.)

So, I'm not misunderstanding, just misinformed that the definition changed.

Make no mistake, of course: I do appreciate you correcting me as I hadn't realized the definition had changed. Lol.