Viscosity 1.9 breaks ability to connect to VPN Server

[dustin.whitlow]

All,

I upgraded to the latest 1.9 release today and am on macOS 10.15.7 latest. This release has broken my ability to connect to remote VPN server. As soon as I revert to 1.8.6 I can connect totally fine. The specific error thrown is the following:

Code: Select all

ERROR: could not read Auth username/password/ok/string from management interface

The VPN server I am connecting to is a bit outdated but I am wondering if this is a client side issue, or very well could be the need to upgrade something like the VPN server operating system as well as VPN version itself. The VPN server is running Pritunl 1.29.2209.0. On the server side I am getting:

Code: Select all

ERROR User auth failed "Invalid OTP code"

Also note that I use the combination of username/password followed by rotating OTP code as secondary authentication. I would appreciate any help with this.

Thanks,
Dustin

[James]

Hi Dustin,

It sounds likely your connection was set to use OpenVPN 2.3 previously. Please see:
https://www.sparklabs.com/support/kb/ar ... envpn-2-4/

Cheers,
James

[nicholas.laird]

So to workaround the issue (since I can reproduce it) you need to put your OTP code in the password field concatenated together like you would with a client that doesn't support asking for OTP separately.

This doesn't fix the issue but helps narrow down where it's occurring.

I tested with Viscosity 1.9 and injected OpenVPN 2.3 instead of the built in version 2.4. Didn't help.
I also tried the en/feth/vtap adapter options and they didn't impact the problem either.

Connecting on the command line works as expected but it doesn't prompt for OTP separately so you have to concatenate them. It was at this point I tried it in the GUI and it connected. Eureka!

It appears to literally be a OTP auth failure due to some mishandling of OTP. Sidestepping by doing Password+OTP sorta confirms this.