Kunzisoft / Kunzisoft/KeePassDX
Use android:isolatedProcess to improve security
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 7.3k
- Forks
- 403
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 1
Description
“If set to true this service runs under a special process that is isolated from the rest of the system and has no permissions of its own. The only communication with it is through the Service API, with binding and starting”.
— “https://developer.android.com/guide/topics/manifest/service-element”
This feature is good because it makes more difficult for an attacker whom found an exploit to compromise user’s data.
Example:
< service
android:name="com.kunzisoft.keepass.services.DatabaseTaskNotificationService"
android:enabled="true"
android:exported="false"
android:isolatedProcess=“true” />
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Android manifest declaration for DatabaseTaskNotificationService and read how that service is used. Check whether enabling isolatedProcess preserves the service's existing behavior, then verify that the manifest setting is present and the related notification flow still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100