[Replicant] Replicant risks

[Adonay Felipe Nogueira]

As browser, I use com.stoutner.privacybrowser.standard (Privacy Browser) for most websites, and leave the stock browser for trusted websites.

Privacy Browser doesn't run JS, nor loads images by default. It works evem without LLVMpipe graphics rendering.

Em 6 de outubro de 2024 13:18:41 BRT, John via Replicant <replicant at osuosl.org> escreveu:
>On Tue, 1 Oct 2024 00:53:57 +0200 Denis 'GNUtoo' Carikli via Replicant
>wrote:
>
>> First the browser component shipped by Replicant is outdated, so it's
>> probably trivial for a website to take control of the phone. The
>> system browser component is used in a lot of applications shipped by
>> F-Droid.
>
>Is it not possible to use an alternative better browser? (which?)
>
>> But it doesn't stop here as there could be unpatched vulnerabilities
>> everywhere in the system, including in things like the SMS application
>> for instance.
>> 
>> So even if the phone is not connected to Internet there are still
>> risks.
>> 
>> Denis.
>
>But such risks exist in all Android versions, no?
>So, perhaps the even more important questions related to that are:
>
>- How does Replicant compare to alternatives security-wise?
>- What can be done to improve things without sacrificing freedom?
>_______________________________________________
>Replicant mailing list
>Replicant at osuosl.org
>https://lists.osuosl.org/mailman/listinfo/replicant