TeamAmaze / TeamAmaze/AmazeFileManager
Setup custom Certificate for FTPs
@TranceLove is already working on this.
Since Oct 21, 2023.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Currently when the FTPs server runs, it uses "your own" (Amaze Team) certificate.
I would like to request to allow users to use "their own" certificate in the settings.
IF not setup / error / default > use the Amaze Team default cert
ELSE > use the user's certificate
In this case i would also suggest a new line/entry/label in the simple panel to start and stop the FTPs server reporting the certificate used, so the user is aware in case of issue (Certificate: default / custom). Maybe also a button to show (via popup) the Fingerprints (MD5, Sha1, Sha256 & Sha512) of the certificate in use/loaded.
About the location, I would recommend to not create copy in Amaze config folders of the custom certificate, leaving the path decided by the user. This may prevent "attack" that substitute the copied certificate placed in the "hard coded" path of the phone memory.
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.
Assessment
This issue has not been assessed yet.