ProxymanApp / ProxymanApp/Proxyman
export .0 cert file for rooted android devices
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Description
We would like to add a feature on Mac to “Export certificates in .0 format.”
The current process is somewhat complex. I have to first download the certificate in .pem format on my phone and then convert it to .0 format.
For reference on how to convert a .pem certificate to .0 format, please check:
https://blog.csdn.net/haduwi/article/details/125696208
Why this feature/change is important?
I know that Proxyman currently offers a solution for exporting certificates in .pem format, but this process is a bit cumbersome. For rooted Android devices, there is actually a simpler way to capture network traffic:
After exporting the certificate in .pem format, you can use the following command:
openssl x509 -subject_hash_old -in CERT.pem
This command will get a filename at first line. Rename the file with a .0 extension.
Then, push the renamed file to the /system/etc/security/cacerts/ directory on the phone. This will allow you to capture network traffic easily without needing to configure res/xml/network_security_config.xml in your app.
Contributor guide
No contributing guide indexed for this repository
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 existing Mac certificate export flow that produces PEM files. Check how the requested .0 filename should be derived from the certificate, then verify that the exported file can be used in the rooted Android cacerts directory as described; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, macos
- Domain
- desktop-dev, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100