Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Molly should supports only secure versions of Android. #108

Open
1 task done
ghost opened this issue May 15, 2022 · 10 comments
Open
1 task done

Molly should supports only secure versions of Android. #108

ghost opened this issue May 15, 2022 · 10 comments
Labels
feature-request New feature or request

Comments

@ghost
Copy link

ghost commented May 15, 2022

Is there an existing request for this?

  • I have searched the existing issues

Feature description

As the title says. Molly should be to run only on the four latest major releases, as they get security updates.

Currently, Molly targets minSDK 23 -- Android 6.0 Marshmellow, which is an ancient version of Android without security updates and a proper security model.

Every month Google release a security bulletin, which provides documention about the security vulnerabilties which nave been fixed. It is very important to get those fixes because otherwise you are vulnerable to known vulnerabilities.

As Molly is an hardened version of Molly, maybe this 'feature' should be considered.

@ghost ghost added the feature-request New feature or request label May 15, 2022
@thrdroom
Copy link

I don't see how this would benefit molly in any way. It is up to the user to decide which android version he is using, and therefore the user is responsible for an outdated OS.

Some users may "only" use molly for its advanced app locking feature or amoled theme etc, and they don't care as much about the other features.

Including a bigger range of supported android versions also means including a bigger range of people who are forced to use an older device because they cant afford a new one.

There is a lot more things to consider then just the security aspects.

@Chromatros
Copy link

Chromatros commented Jun 6, 2022

without security updates and a proper security model.

Every month Google release a security bulletin, which provides documention about the security vulnerabilties which nave been fixed. It is very important to get those fixes because otherwise you are vulnerable to known vulnerabilities.

There was some talk on the matrix rooms about adding remote attestation. It would allow you to verify that the other device is not tampered with and runs on the latest security updates. This could be the solution for you request. The app could support older devices and make use of modern hardware.

https://attestation.app/about

They closed 5 RCE on pixel and AOSP 2 in June '22 bulletin.

If i understand it correctly the patch level is also integrated with attestation. Can this be manipulated somehow?

Screenshot_20220607-023009.jpgScreenshot_20220607-022322.jpg

@ByJumperX4
Copy link

Switching to only secure versions of Android would make people that can't switch to a secure Android version (drop of support + financial issues)'s lives worse.

@beaglesnuf
Copy link

The compromise would be to bump the target sdk to 32 and maintain the maximum level that Andoid allows (33 when A13 is released and so on). This would allow an OS which supports it such as GrapheneOS to apply stronger application sandboxing = more secure application.

@BenjaminBrienen
Copy link

BenjaminBrienen commented Jul 30, 2022

I support this idea, but only if it would allow for benefits such as increased security, functionality, maintainability, and such for the project. If dropping support for outdated operating systems means that the app can be leveraged in a more optimal way by newer ones, then I would support that. When using outdated operating systems, you have to accept the fact that you may be stuck with outdated software across the board.

@haarp
Copy link

haarp commented Aug 16, 2022

On the contrary.. Apps shouldn't patronize users, even if they think it's for their own good. "Those who give up liberty for safety deserve neither".

I realize there a good technical reasons for raising the minimum API. But in my case. I actually would like to request a lowering.

My relatives use old devices with old degoogled Androids. They don't use the device for much more than communication, navigation and occasionally browsing in a heavily-adblocked Firefox.

On Android 5.1.1, the latest Molly that could be installed was 5.34.9. Will that make them want to upgrade the device? Nope. They'll simply stick with the old version. That can't be the solution either. Especially as it has started crashing now.

@johanw666
Copy link
Contributor

johanw666 commented Sep 4, 2022

If it starts crashing their best action would be to switch to Signal, which supports Android 4.4 and up, assuming that a new phone is not an option.

@sycam0r-e
Copy link
Contributor

sycam0r-e commented Oct 8, 2022

I strongly support this issue. Molly already has a specific target group in mind, that is security and privacy conscious folks. Only supporting secure versions of Android fits well in, at least the compromise @beaglesnuf mentioned. Also, it would I make maintenance easier for the dev, I think valldrac mentioned this once on Matrix (@benalbrecht).

@valldrac
Copy link
Member

valldrac commented Oct 9, 2022

Molly will phase out support for ancient versions of Android progressively when new core features require it and to reduce maintenance.

Regarding security, it should be noted that even the highest value of minSDK does not guarantee that the device is fully patched. On the contrary, the upcoming remote attestation feature can ensure your contacts' devices are running on the latest patch level. Remote attention also has the advantage that doesn't block anyone from using the app on older hardware if they need to.

@ilu33
Copy link

ilu33 commented Oct 21, 2023

I oppose this. While trying to stay "secure" (1) in our communication we are rapidly destroying the planet we live on. A smartphone can easily last 10 years or more. Sadly not even custom ROMs provide updates that long. But that does not entitle anyone to exhaust our planets resources by buying new devices every 3 years.


(1) Please face reality: The level of security you expect does not exist on hardware which you do not control and cannot trust. The Android version does not guarantee anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request
Development

No branches or pull requests

10 participants