Search found 12 matches

Search found 12 matches Page 1 of 2
by sbarnea
Fri May 06, 2022 5:40 pm
Forum: Viscosity Support (Mac Version)
Topic: Unable to add auth-user-pass entry to commands (regression)
Replies: 1
Views: 3255

It appears that latest versions of Viscosity are no longer allowing us to add `auth-user-pass <filename>` to custom commands and instead is just removing them without any warning. This prevents use of external scripting for dynamic credential entering. I am sure that this worked for 5+ years but it ...
by sbarnea
Thu Mar 22, 2018 2:24 am
Forum: Viscosity Support (Mac Version)
Topic: --auth-user-pass fails with '...' Permission denied
Replies: 3
Views: 5652

It seems that recently Viscosity --auth-user-pass stopped option stopped working and i am not sure if this was caused by a change in Viscosity 1.7.8b3 or MacOS 10.13.3. Connection fails silently and on the logs I can see this error: Options error: --auth-user-pass fails with '/Users/johndoe/.cache/....
by sbarnea
Thu Dec 07, 2017 7:54 pm
Forum: Viscosity Support (Mac Version)
Topic: After upgrading to 1.7.3 viscosity lost auth-user-pass
Replies: 4
Views: 12149

all the "auth-user-pass" sections were removed from the VPN config files. Viscosity represents this option with the "Use Username/Password authentication" checkbox. Use of a password text file for storing authentication details is not supported - Viscosity supports storing crede...
by sbarnea
Mon Aug 07, 2017 8:37 pm
Forum: Viscosity Support (Mac Version)
Topic: After upgrading to 1.7.3 viscosity lost auth-user-pass
Replies: 4
Views: 12149

Sorry to say it but it seems that I reached an "enough-is-enough" kind of moment, I am going to look for Viscosity replacements because it seems that Sparklabs has little interest in fixing its problems. One thing is clear and I reported it several times: Adding "auth-user-pass" ...
by sbarnea
Mon Jul 10, 2017 6:27 pm
Forum: Viscosity Support (Mac Version)
Topic: After upgrading to 1.7.3 viscosity lost auth-user-pass
Replies: 4
Views: 12149

It seems that you totally missed the 2FA use-case, where the only way to implement a reliable (self-restoring) VPN connection is to use the "auth-user-pass" file in combination with before-connect-script which generates the one-time-password in that file. This is a standard use case of Ope...
by sbarnea
Tue Jul 04, 2017 11:32 pm
Forum: Viscosity Support (Mac Version)
Topic: After upgrading to 1.7.3 viscosity lost auth-user-pass
Replies: 4
Views: 12149

Upgrading from 1.7.1 to 1.7.3 seems to be a complete disaster: * all the "auth-user-pass" sections were removed from the VPN config files. * Adding the file manually works, one time because the directive is removed and next time you connect viscosity will not have it * the clean-log option...
by sbarnea
Thu Feb 23, 2017 11:52 pm
Forum: Viscosity Support (Mac Version)
Topic: How to disable hostname reconfiguration on vpn connection
Replies: 2
Views: 9886

It seems that once Viscosity for Mac establish a connection the hostname is reconfigured to something like "OVPN-117-91" which is picked based on the IP address of the VPN. I do want to disable this functionality as I want to keep my hostname stable and to float to random values on each VP...
by sbarnea
Tue Jan 17, 2017 10:17 pm
Forum: Viscosity Support (Mac Version)
Topic: 1.6.8 for MacOS breaking changes
Replies: 1
Views: 3016

It seems that 1.6.8 upgrade which I made few minutes ago does lose the status of the "run unsafe commands", breaking some VPNs. You can always re-enable it but the point is that the setting is lost on upgrade.
by sbarnea
Fri Dec 09, 2016 10:50 pm
Forum: Viscosity Support (Mac Version)
Topic: Forum Support
Replies: 1
Views: 2857

I would rather post to the forum because I do like to share my experience and eventually to help (or get help from) other customers. Sometimes that best solutions do come from other users :) The big question is if you do actively monitor your support forum ? Do we also have to raise support ticket a...
by sbarnea
Fri Dec 09, 2016 10:40 pm
Forum: Viscosity Support (Mac Version)
Topic: Broken DNS resolver configuration after failed login
Replies: 4
Views: 5880

I think I hit the same bug where /etc/resolv.conf is not updated after you connect to the VPN, while using Viscosity 1.6.7 Doing a cat on the file exposes only the old-dns server (before the VPN connection was established). Instead `scmutil --dns` reports all DNS servers. I can confirm that due to t...
Search found 12 matches Page 1 of 2