irregula...@riseup.net writes:
Hello people,
I'm investigating how may we combine the traffic obfuscation provided by
obfsproxy+scramblesuit with OpenVPN instead of Tor.
I completely understand how this combination does not provide anonymity,
but nevertheless I think it will be of some
On 03/07/2014 12:10 AM, Yawning Angel wrote:
Looking at the OpenVPN source (src/openvpn/socks.c):
const ssize_t size = send (sd, \x05\x02\x00\x02, 4, MSG_NOSIGNAL);
The method selection request is hardcoded to always claim support for
No Auth, and Username/Password Auth in that order.
On Mon, 10 Mar 2014 03:27:12 +0200
irregula...@riseup.net wrote:
Are we sure it's an OpenVPN bug? Cause I'm getting a :
socks_handshake: server asked for username/login auth but we were not
provided any credentials
which kind of makes sense regarding the methods' priority in socks5.py
On Mon, 10 Mar 2014 01:57:11 +
Yawning Angel yawn...@schwanenlied.me wrote:
The moment the OpenVPN people fix their broken SOCKS client to not
offer to negotiate an authentication method that they can't actually
use due to missing parameters, this will work as expected.
On 03/05/2014 07:58 PM, Yawning Angel wrote:
So, while testing OpenVPN with obfsproxy and the latest patch, the vpn
client enters the authentication phase.
Yay.
Do the credentials depend on the pluggable transport in use by the
obfsproxy?
Yes. It only should happen for obfs2 (if Shared
On Thu, 06 Mar 2014 19:22:16 +0200
irregulator irregula...@riseup.net wrote:
On 03/05/2014 07:58 PM, Yawning Angel wrote:
Hey people thanks for your input,
I'm actually passing password inline while starting obfsproxy
(client-side) like that :
python pyobfsproxy.py --log-min-severity=info
Hello people,
I'm investigating how may we combine the traffic obfuscation provided by
obfsproxy+scramblesuit with OpenVPN instead of Tor.
I completely understand how this combination does not provide anonymity,
but nevertheless I think it will be of some use.
In the recent past there have been
On Wed, 05 Mar 2014 15:08:06 +0200
irregula...@riseup.net wrote:
Luckily yawning provided a patch some days ago [5], and I decided to
test it. According to patch's comments, it implements a Socks5 proxy
with authentication as in RFC 1928/RFC 1929. This authentication is
gonna serve as a means
Heya,
The company I work for is building an OpenVPN client which has obfsproxy
support, there is a branch, but it's not finished:
https://github.com/greenhost/viper/tree/obfsproxy-support
And then.. the serverside isn't pushed but it was working, it would
generate scramblesuite passwords using
