Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Di 09.07.2024 00:01:12 2.880 0 374.874 130,2 Toot Café 4.2.10 500 Mo 08.07.2024 00:01:20 2.880 0 374.707 130,1 Toot Café 4.2.10 500 So 07.07.2024 00:00:37 2.880 0 374.585 130,1 Toot Café 4.2.10 500 Sa 06.07.2024 00:00:04 2.880 0 374.465 130,0 Toot Café 4.2.10 500 Fr 05.07.2024 00:01:16 2.880 0 374.345 130,0 Toot Café 4.2.10 500 Do 04.07.2024 00:01:17 2.880 0 374.203 129,9 Toot Café 4.2.9 500 Mi 03.07.2024 00:02:08 2.880 0 374.021 129,9 Toot Café 4.2.9 500 Di 02.07.2024 00:00:32 2.880 0 373.842 129,8 Toot Café 4.2.9 500 Mo 01.07.2024 00:02:14 2.880 0 373.716 129,8 Toot Café 4.2.9 500 So 30.06.2024 00:01:10 2.880 0 373.617 129,7 Toot Café 4.2.9 500
David Chartier (@chartier) · 10/2018 · Tröts: 10.750 · Folger: 4.233
Di 09.07.2024 14:19
#RCS is NOT encrypted
It does not offer “improved encryption” over SMS, only the *option* IF:
- The phone maker installs the encryption extension
- All carriers involved choose to support RCS encryption
If any phone in a chat does not support it, everyone devolves back to default, unencrypted RCS. And I have yet to see an iOS 18 write up that explains how to tell whether an Android user has encryption enabled.
I’m not in infosec, but this sounds like a fucking mess. https://www.macrumors.com/2024/07/09/rcs-messaging-explained-ios-18/
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0 · via Ivory for iOS