Yet Another Intercepting Proxy

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tag: Branch: Tree: master

master

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'master'

${ noResults }

YAIP/tests

History

Jonathan Hodgson dd71d26245 Initial https proxy work ... The proxy can now sit between a client and a https web server. It does this by looking for a CONNECT request that conventional proxies use to open a tunnel between a client and an https server. Instead of opening an opaque tunnel, yaip immediately sends bacck a "connection established" response. This tells the client (browser normally) to proceed and initiate an HTTPS connection. I use the host that was send in the connect request to set up a fake SSL server. If we have seen the domain before, we re-use the certificate, otherwise we generate a new one and sign it using YAIP's built in certificate authority. I still need to do work on forwarding the request upstream. This is my next job. Currently, yaip responds with a valid response of "it worked". ``` $ curl https://example.com --cacert ~/.config/yaip/cert.pem It worked ``` Notice, we don't get any certificate errors because we are telling curl to trust the authority that yaip uses		2 years ago
..
munit@fbbdf1467e	Adds µnit submodule for tests	2 years ago
all.test.c	Now working for simple, non-encrypted requests	2 years ago
config.test.c	Starts work on https as well as some moving about	2 years ago
request.test.c	Initial https proxy work	2 years ago
requestresponse.test.c	Moves some logic out of proxy and into main	2 years ago
response.test.c	Moves some logic out of proxy and into main	2 years ago
ssl.test.c	Initial https proxy work	2 years ago
util.test.c	Early SSL Certificates creation work done	2 years ago