Path: ...!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Arno Welzel Newsgroups: comp.mobile.android,misc.phone.mobile.iphone,comp.sys.mac.system Subject: Re: DOJ is correct that Apple iPhone is far less secure than Android when RCS messaging is involved Date: Fri, 12 Apr 2024 18:26:02 +0200 Lines: 37 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: individual.net iWKM56XsN+EFNnvKi+SMHARzwsYGN3b+jNhVDul2jE3IEK4zO3 Cancel-Lock: sha1:K1yFdYekeZYgGNQcz4uQtrgibAs= sha256:h4aTmY9aI2RQdDpQZ/xiuyxohdo4egK/dKFH2M8hQPY= Content-Language: de-DE In-Reply-To: Bytes: 2119 Alan, 2024-04-05 20:11: > On 2024-04-05 05:42, Arno Welzel wrote: >> Tamborino, 2024-04-01 02:55: >> >>> This is the common misunderstanding with both RCS in general and Apple's >>> update in particular. RCS is not end-to-end encrypted. >> >> RCS *is* end-to-end encrypted. But this is not mandatory, so using >> unencrypted connections is possible. But the Google messaging app in >> Android will show you if the recipient has RCS and also if the >> connection is encrypted. >> > > Incorrect. > > RCS as implemented by Google has end-to-end encryption. > > The RCS standard does not have encryption as a part of it. Yes, you're right. I stand corrected. [...] > Apple is not prepared to adopt Google's encryption, and given that > Google can't be trust with your privacy (Google Chrome sweeping up > information while in incognito mode, anyone?), can you blame Apple? What is the difference? Messages get send anyway, just not encrypted during transmission. But where is the security issue here? It's more likely that Apple just does not want to implement stuff which is not an official standard. -- Arno Welzel https://arnowelzel.de