TeamAmaze / TeamAmaze/AmazeFileManager
Alternatives to AESCrypt
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
As of April 2025 it is found that AESCrypt had updated to V3, while their source code had been removed and changed their license model to 30-day trialware.
While AESCrypt V2 will continue to work, we shall need to consider alternatives to AEScrypt for file encryption in Amaze.
The new encryption method may not be compatible with AESCrypt as there was no direct drop-in replacements however.
Describe the solution you'd like
Porting Picocrypt to Java and implement support in Amaze
Describe alternatives you've considered
Implement AESCrypt V3 support with limited information released to public and face the possibilities of license issue if we support AESCrypt V3 too.
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 reviewing Picocrypt's design and the project's existing AESCrypt V2 support. Establish whether a Java implementation is feasible and legally suitable, then define the encryption compatibility requirements before attempting integration. Done means Amaze supports the selected alternative without relying on AESCrypt V3.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, kotlin
- Domain
- cryptography, mobile, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100