{"push_id":2889513304,"size":1,"distinct_size":1,"ref":"refs/heads/improved-socks-support","head":"81347808e065909c5820bd21c06cfa1621b8e5e6","before":"aa5a7d3d02d2b94eef11928a969b75d90a9fd19b","commits":[{"sha":"81347808e065909c5820bd21c06cfa1621b8e5e6","author":{"name":"Björn Kautler","email":"74e2ee7aa8c396759a26a42a85f2923ab73a4ea5@Kautler.net"},"message":"Provide SOCKS4 and SOCKS4a support and improve SOCKS5 support (#528, #529, #531)\n\n- when acting as SOCKS5 proxy, provide the ability to require username / password authentication (#529)\n- use a replaying decoder for the protocol detection to get as many bytes as needed (#531)\n- support SOCKS4 and SOCKS4a instead of only SOCKS5 (#528)\n- only select auth methods the client offered in the SOCKS5 initial response (#529)\n- detect SOCKS protocols before SSL, as valid SOCKS messages can be recognized as SSL messages erroneously\n- do not try to decode the amount of SOCKS5 auth schemes as auth scheme which will fail if there are more than 2 auth methods available\n- do not treat SOCKS4, SOCKS4a and SOCKS5 equally when determining protocol, as their messages are quite different (#528)","distinct":true,"url":"https://api.github.com/repos/Vampire/mockserver/commits/81347808e065909c5820bd21c06cfa1621b8e5e6"}]}
{"actor":{"display_login":"Vampire"}}