mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-25 16:15:55 +03:00
[GH-ISSUE #421] 400 Bad Request downloading iOS Root CA #417
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#417
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @FinHorsley on GitHub (Mar 2, 2020).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/421
Originally assigned to: @NghiaTranUIT on GitHub.
Proxyman version? (Ex. Proxyman 1.4.3)
Version 1.17.1 (11710)
macOS Version? (Ex. mac 10.14)
Version 10.15.3 (19D76)
iOS Version
Version 13.3.1
Steps to reproduce
Follow the steps to install iOS certificate on physical device.
The http://proxy.man/ssl request returns a 400 Bad Request
Expected behavior
iOS will show the alert to install the certificate
@NghiaTranUIT commented on GitHub (Mar 3, 2020):
Hi @FinHorsley, I tested and I was able to reproduce your bug if we had not install the Proxyman CA first (Step 1)
Tutorial: https://proxyman.io/blog/2019/06/How-I-use-Proxyman-to-see-HTTP-requests-responses-on-my-iPhone.html
Please let me know if it works for you.
@FinHorsley commented on GitHub (Mar 3, 2020):
Thanks 😊
Is the cause behind this because the “Install Root Proxyman Certificate on this Mac” actually creates the Root CA?
In my case I was trying to fetch the root CA from iOS, but ProxyMan hadn’t created the CA yet?
@NghiaTranUIT commented on GitHub (Mar 3, 2020):
Yes, it's
That's correct.
Proxyman separates the generation Proxyman CA step and the fetch from iOS. In order to work, we have to install the certificate firstly 🙌
@NghiaTranUIT commented on GitHub (Mar 3, 2020):
I also improve the behavior by adding some useful instruction if we got 400 Bad Request (https://github.com/ProxymanApp/Proxyman/issues/422) 👍
@FinHorsley commented on GitHub (Mar 3, 2020):
Why do i need to trust the RootCA on macOS in order to see SSL responses coming from an iOS device?
I understand that I'd need to trust the certificate on Mac to see the macs traffic, but not for iOS
@NghiaTranUIT commented on GitHub (Mar 3, 2020):
It's a really good question. From what I understand, we don't need to trust RootCA on macOS, but we have to generate the certificate firstly(and the generation step comes with trusting the certificate, it' our decision to make it easier to use).
In your first case, you haven't generated any certificates, so it's 400 Bad Request (Missing file)
@NghiaTranUIT commented on GitHub (Mar 3, 2020):
But thank for the question, I will consider to improve this procedure 👍 @FinHorsley
@FinHorsley commented on GitHub (Mar 3, 2020):
So I have created the root CA (using the manual process) on my Mac, but purposely didn’t trust that certificate.
When I come to intercept traffic from iOS, ProxyMan says that I have to trust the certificate on MacOS before I can inspect SSL responses.
Is this expected behaviour?
@NghiaTranUIT commented on GitHub (Mar 3, 2020):
At the moment, it's expected behavior because at the initial development, I'm not aware that we don't need to trust Proxyman CA on macOS in order to intercept the requests from your iPhone 😬
I will consider to fix it to make more flexible than forcing trust the certificates.
@FinHorsley commented on GitHub (Mar 3, 2020):
That’s great 😊
(I don’t think it’s necessarily to install the rootCA on MacOS for this, having used tools like MitmProxy in the past I know they don’t require this)
@NghiaTranUIT commented on GitHub (Mar 3, 2020):
Totally agree 👍