kore/tls-proxy at c68eb0c7055f36e0ab97d8bb8192447b64f01685 - kore

History

Joris Vink e98a4ddab5 Change how routes are configured in Kore. Routes are now configured in a context per route: route /path { handler handler_name methods get post head validate qs:get id v_id } All route related configurations are per-route, allowing multiple routes for the same path (for different methods). The param context is removed and merged into the route context now so that you use the validate keyword to specify what needs validating.		2021-09-15 11:09:52 +02:00
..
conf	Change how routes are configured in Kore.	2021-09-15 11:09:52 +02:00
src	use name instead of c->ssl->session things	2019-04-30 21:06:27 +02:00
.gitignore	Add TLS proxy example.	2015-12-02 21:52:26 +01:00
README.md	kore -> kodev where appropriate	2017-03-06 11:00:53 +01:00

Kore as a TLS-proxy.

Edit src/proxy.c and add your backends to the backends[] data structure.

If you want to reduce attack surface you can build Kore with NOHTTP=1 to completely remove the HTTP component and only run the net code.

Run:

	$ kodev run

Test:

	Connect to the server and notice that it proxies data between you
	and your destination.

	$ openssl s_client -connect 127.0.0.1:8888