Joris Vink c463ecb3cb Changes to the event loop inside of Kore.
Now anyone can schedule events and get a callback to work as long
as the user data structure that is added for the event begins
with a kore_event data structure.

All event state is now kept in that kore_event structure and renamed
CONN_[READ|WRITE]_POSSIBLE to KORE_EVENT_[READ|WRITE].
2018-10-09 19:34:40 +02:00
..
2015-12-02 21:52:26 +01:00
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