Page 1 of 1

Problem with obfs2

Posted: Sat Sep 21, 2019 5:58 am
by diman-pro
Hello! I'm having trouble connecting to OpenVPN using obfs2. Obfs2 requires a shared-key on the server, but it cannot be specified in the Viscosity client. I also tried to make obfs2 run via bat script before connecting:
START "Obfs" C:\obfsproxy\obfsproxy.exe obfs2 --shared-key ... --dest ... client 127.0.0.1:2022
The problem is that Viscosity does not connect to the server until obfsproxy running.
How can I fix this problem?

Re: Problem with obfs2

Posted: Mon Sep 23, 2019 11:26 am
by Eric
Hi diman,

I'm afraid obfs2 and obfs3 don't support shared-secrets within Viscosity, we recommend updating to scamblesuit or obfs4 if you wish to use a shared secret.

If your only option is obfs2 and you need a shared secret, you can start your version of obfsproxy manually and then set your client address (i.e. 127.0.0.1, port 2022) in Viscosity as a SOCKS proxy in the Transport tab.

We'll investigate if we can add shared-secret support to the older obfs protocols in a future release.

Regards,
Eric

Re: Problem with obfs2

Posted: Tue Sep 24, 2019 3:58 am
by diman-pro
At the moment, the only option for me is obfs2. And I wanted to add shared-secret to it.
Can I make obfsproxy start automatically when I connect to VPN? I tried to implement a script that would do this, but the problem is that Viscosity waits for obfsproxy to complete before connecting to the server.

Re: Problem with obfs2

Posted: Tue Sep 24, 2019 10:32 am
by Eric
Hi diman,

Using the Batch Start command will launch obfsproxy without waiting before the batch script continues. For e.g.

start "C:\path\to\obfsproxy" obfs2 .....

Regards,
Eric