Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Arno Welzel Newsgroups: comp.mobile.android,misc.phone.mobile.iphone Subject: Re: Encryption comes to RCS at last on iPhones. Date: Tue, 18 Mar 2025 12:15:54 +0100 Lines: 30 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net YbnrMK0p5ckHoZ/R8yFSeA4k2N60rWI6QiiIHOD65eqYrjnsXp Cancel-Lock: sha1:UatoPbQGCKN3hrNQm77jxzVEUpI= sha256:V74oeuyXcW/p/ldOu+Bmohh4Mk578OKp387TiSMAwls= Content-Language: en-US, de-DE In-Reply-To: Xref: csiph.com comp.mobile.android:147249 misc.phone.mobile.iphone:193735 Jörg Lorenz, 2025-03-17 21:32: > On 17.03.25 19:40, Carlos E.R. wrote: >> As for >> Google’s side of things, Android users already have E2EE between them by >> default for RCS texts. > > This is simply wrong. No, this is correct. When you communicate with other Google users, E2EE is default for RCS. However Googles E2EE in RCS is a properietary solution yet. But I assume, that Google will adopt MLS as well and hopefully this will soon be the common standard. >> What the article does not clarify is whether Android will also implement >> this (Google uses its own encryption method), and so what will happen to >> cross platform messages. > > They will not because Apple will not apply a proprietary encryption > under Google's control. You confused some things here: the question was, if *Google* will implement MLS as well. And I don't see any reasone, why Google should not change to MLS. MLS makes their proprietary solution obsolete. -- Arno Welzel https://arnowelzel.de