mitmproxy ios certificate #1

Yannik · 2011-05-21T11:25:35Z

Cerifitcate expires in 1902 and is not working.
http://imageshack.us/m/405/2772/img0974.png

Download cert here:
http://www.mediafire.com/?gcosyenvi03m733

cortesi · 2011-05-24T03:00:06Z

Hey Yannik,

That's odd - we definitely generate these certs with a far-future expiry date. I've just generated and regenerated using mitmproxy, and it works for me.

What version of OpenSSL are you using? Which platform are you on? Is there anything else odd about your configuration? Are you using a checkout from trunk?

Cheers,

Aldo

Yannik · 2011-05-24T08:58:27Z

Hey,

Platform: Debian GNU/Linux 6.01
OpenSSL: OpenSSL 0.9.8o 01 Jun 2010
Python: Python 2.6.6

Nothing odd about it, it's just a clean install of debian ;-)

I just used this release: http://mitmproxy.org/download/mitmproxy-0.4.tar.gz

My iOS version is 4.3.3

-----Ursprüngliche Nachricht-----
Von: cortesi [mailto:reply@reply.github.com]
Gesendet: Dienstag, 24. Mai 2011 05:00
An: yannik@sembritzki.me
Betreff: Re: [mitmproxy] mitmproxy ios certificate (#1)

Hey Yannik,

That's odd - we definitely generate these certs with a far-future expiry date. I've just generated and regenerated using mitmproxy, and it works for me.

What version of OpenSSL are you using? Which platform are you on? Is there anything else odd about your configuration? Are you using a checkout from trunk?

Cheers,

Aldo

Reply to this email directly or view it on GitHub:
cortesi#1 (comment)

cortesi · 2011-06-11T03:28:32Z

Yannik,

Could you please try this with a current checkout of the code? I'm totally unable to reproduce this - I even went so far as to do a Debian install to see if it acts differently!

Aldo

Yannik · 2011-06-19T16:26:15Z

Hi,

i installed it all over again, but the 'Valid until' date is still in 1902 :(

-----Ursprüngliche Nachricht-----
Von: cortesi [mailto:reply@reply.github.com]
Gesendet: Samstag, 11. Juni 2011 05:29
An: yannik@sembritzki.me
Betreff: Re: [mitmproxy] mitmproxy ios certificate (#1)

Yannik,

Could you please try this with a current checkout of the code? I'm totally unable to reproduce this - I even went so far as to do a Debian install to see if it acts differently!

Aldo

Reply to this email directly or view it on GitHub:
cortesi#1 (comment)

Yannik · 2011-06-19T16:30:56Z

It is valid from 19.06.2011 (today) until 28.09.1902.

Any ideas?

-----Ursprüngliche Nachricht-----
Von: cortesi [mailto:reply@reply.github.com]
Gesendet: Samstag, 11. Juni 2011 05:29
An: yannik@sembritzki.me
Betreff: Re: [mitmproxy] mitmproxy ios certificate (#1)

Yannik,

Could you please try this with a current checkout of the code? I'm totally unable to reproduce this - I even went so far as to do a Debian install to see if it acts differently!

Aldo

Reply to this email directly or view it on GitHub:
cortesi#1 (comment)

Yannik · 2011-06-19T18:11:03Z

Content of the certificate:

cortesi · 2011-06-20T09:45:27Z

Hmm... Do you see the same notAfter date on the CA cert? If you do, I might send you some commands to manually generate a cert in the same way mitmproxy does, so we can try to get to the bottom of this. Thanks for helping me track this down!

Yannik · 2011-06-20T15:49:09Z

Yeah, the mitmproxy-ca.pem & mitmproxy-ca-cert.pem valid until date is completely the same.

cortesi · 2011-06-22T08:02:10Z

I do believe we've hit a 2038 overflow bug in your version of OpenSSL here.
Could you try an experiment for me? In utils.py, change all the occurances
of 9999 to something lower, say, 100, and see if that fixes things. If so,
we've hit an interesting overflow problem...

On Tue, Jun 21, 2011 at 3:49 AM, Yannik <
reply@reply.github.com>wrote:

Yeah, the mitmproxy-ca.pem & mitmproxy-ca-cert.pem valid until date is
completely the same.

Reply to this email directly or view it on GitHub:
cortesi#1 (comment)

Aldo Cortesi
www.nullcube.com
+64 210 718 900

Yannik · 2011-06-22T11:49:17Z

Nope, this did not change anything.

New utils.py: http://pastebin.com/A7DcCZSp

m4rkh · 2011-07-17T16:20:17Z

@cortesi - thanks, I'm new to the product using cygwin on windows 7, openssl 0.9.8r. Initially only mitmproxy-ca.pem was created with an expired 1902 date. Tried running openssl by hand with 9999 and sure enough the new certificates have also expired! Assuming that the bug is in openssl 0.9.8r??

Following your advice, changed each 9999 to 365 in utils.py, ran setup.py clean, setup.py install, deleted contents of ~/.mitm-proxy then reran mitmproxy. This time mitmproxy-ca-cert.p12, mitmproxy-ca-cert.pem, mitmproxy-ca.pem were created each with valid expiry dates. I'm happy!

cortesi · 2011-07-17T21:32:57Z

Mark - that's good to hear. I'll drop the default certificate expiry time to something like 3 years to try to avoid this OpenSSL bug.

Yannik - could you please re-try Mark's method and see if you still have the problem? Remember to clear the ~/.mitmproxy directory and then restart to re-create the certificates.

Yannik · 2011-07-18T09:10:00Z

Okay, I will try it again. I will inform you about the result later.

Yannik · 2011-07-20T21:41:16Z

Yep, that fixed it! I had to edit it before using setup.py. Thanks alot! Great project :-)

cortesi · 2011-07-21T23:15:41Z

Hey chaps,

Just committed a change that drops the cert expiry date to 3 years. I'm re-opening this issue because I'd like to double-check that this doesn't trigger the OpenSSL bug. Could one of you please check for me?

Thanks a lot,

Aldo

Yannik · 2011-07-22T06:57:35Z

Yep, works like a charm :-)

cortesi · 2011-07-22T07:06:14Z

Thanks, Yannik.

Merge pull request #371 from tekii/master

Fix cert generation if confdir is relative

* feat(cibuild): add buildx multi arch builds * chore: add changelog for arm64 * temporarily enable docker ci job for PRs * Update cibuild.py * Update cibuild.py * chore(cibuild): create docker-container xbuilder * chore(cibuild): fix lint * temporarily remove run check to see error message * Update cibuild.py * Update cibuild.py * Update cibuild.py * Update main.yml * Update main.yml * Update main.yml * Update cibuild.py * Update cibuild.py * Update Dockerfile * cleanup #1 * next test * move to test branch * fixup * now upload * enable armv6/7 * use multi-stage build to reduce image size * armv7? * drop armv6/armv7 Co-authored-by: Niels Hofmans <hello@ironpeak.be>

Pr 5435

Yannik closed this as completed Jul 20, 2011

cortesi reopened this Jul 21, 2011

Yannik closed this as completed Jul 22, 2011

pridkett mentioned this issue Jul 20, 2013

Connections automatically closed in transparent mode #151

Closed

m0nkeynut mentioned this issue Sep 14, 2014

terminal cursor disappears when editor is set to vim or proxy is backgrouned #357

Closed

mhils pushed a commit that referenced this issue Dec 11, 2014

Merge pull request #1 from mitmproxy/master

83b1d4e

Merge pull request #371 from tekii/master

Kriechi pushed a commit to Kriechi/mitmproxy that referenced this issue Feb 16, 2016

Merge pull request mitmproxy#1 from mhils/master

f62d5b4

Fix cert generation if confdir is relative

internety mentioned this issue Mar 24, 2016

testing for header value weird behavior #1051

Closed

stevesbrain mentioned this issue May 12, 2016

CONNECT inside an HTTP2 stream is not supported #1138

Closed

colemickens mentioned this issue Jun 23, 2016

Consider binding to localhost by default #1293

Closed

pgconlin mentioned this issue Aug 31, 2016

HttpSyntaxException during transparent proxy with ca installed on client #1516

Closed

xrd mentioned this issue Sep 8, 2016

proxapp.py from examples does not work #1538

Closed

phackt mentioned this issue Sep 15, 2016

sslstrip.py processes flow.request.content instead of flow.response.content #1555

Closed

cortesi mentioned this issue Oct 18, 2016

Better control of long output in mitmdump #1623

Closed

rafalbednarczuk mentioned this issue May 18, 2017

mitmproxy dosen't see android connections on transparent mode #2339

Closed

du-premraj mentioned this issue Aug 30, 2017

HTTPS connection did not work through proxy #2553

Closed

PhartimusMaximus mentioned this issue Jul 12, 2018

mitmproxy will not run using Python 3.7.0 #3247

Closed

Kriechi mentioned this issue Aug 7, 2018

Docs on ReadTheDocs outdated #3285

Closed

johhnry mentioned this issue Aug 16, 2019

mitmproxy is not working on Kali Linux (no attribute 'WSGIAdapter') #3618

Closed

mhils added a commit that referenced this issue Jun 15, 2021

cleanup #1

5fc09df

mhils pushed a commit that referenced this issue Nov 28, 2022

Merge pull request #1 from mhils/pr-5435

b15e760

Pr 5435

trueblablak mentioned this issue Mar 2, 2024

mitmproxy don't work with bore tunnel and own DNS server #6703

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

mitmproxy ios certificate #1

mitmproxy ios certificate #1

Yannik commented May 21, 2011

cortesi commented May 24, 2011

Yannik commented May 24, 2011

cortesi commented Jun 11, 2011

Yannik commented Jun 19, 2011

Yannik commented Jun 19, 2011

Yannik commented Jun 19, 2011

cortesi commented Jun 20, 2011

Yannik commented Jun 20, 2011

cortesi commented Jun 22, 2011

Yannik commented Jun 22, 2011

m4rkh commented Jul 17, 2011

cortesi commented Jul 17, 2011

Yannik commented Jul 18, 2011

Yannik commented Jul 20, 2011

cortesi commented Jul 21, 2011

Yannik commented Jul 22, 2011

cortesi commented Jul 22, 2011

mitmproxy ios certificate #1

mitmproxy ios certificate #1

Comments

Yannik commented May 21, 2011

cortesi commented May 24, 2011

Yannik commented May 24, 2011

cortesi commented Jun 11, 2011

Yannik commented Jun 19, 2011

Yannik commented Jun 19, 2011

Yannik commented Jun 19, 2011

cortesi commented Jun 20, 2011

Yannik commented Jun 20, 2011

cortesi commented Jun 22, 2011

Yannik commented Jun 22, 2011

m4rkh commented Jul 17, 2011

cortesi commented Jul 17, 2011

Yannik commented Jul 18, 2011

Yannik commented Jul 20, 2011

cortesi commented Jul 21, 2011

Yannik commented Jul 22, 2011

cortesi commented Jul 22, 2011