TeamAmaze / TeamAmaze/AmazeFileManager
Bug (?): Setting a master password only encrypts folder with AES, files encrypted with AZE
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Describe the bug
As the title says, when setting a master password to encrypt and then select a folder folder to encrypt, choosing AES, it will encrypt the files with AZE, not AES.
Decryption, then fails.
Encryption works fine if I individually encrypt folders, without setting a master password.
To Reproduce
Steps to reproduce the behavior:
- Go to 'Settings'
- Click on 'Security'
- Set 'Master Password'
- Create a test folder
- Create a test file inside that folder
- Encrypt the folder with AES
Expected behavior
File should be encrypted with AES, not AZE.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
- Device: Alcatel 1C
- OS: Android 8.1
- Rooted: No
- Version: 3.8.4 downloaded from Github.
Additional context
Allow me to also question if it's normal that the master password is suppose to be visible, when going to Settings > Security > Master Password?
Shouldn't be hidden?
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 in Settings > Security > Master Password and reproduce the issue by setting a master password, creating a folder and file, then encrypting the folder with AES. Check why the files are encrypted with AZE and why decryption fails; also verify the reported master-password visibility. Done means folder encryption respects the selected AES option and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100