Hi isie2Xo,
That’s fine. That is simply Viscosity adjusting it’s permissions the first time it is run. This includes things like changing the permissions on the Tun/Tap drivers and loading them, locking down the ViscosityHelper process, etc.
Cheers,
James
Build Notice: Viscosity 1.3.4b1 Now Available
Build Notice: Viscosity 1.3.4b4 Now Available
You can subscribe to this topic by clicking on the “Subscribe topic” link at the bottom of the page to receive email notifications of new beta versions.
Build Notice: Viscosity 1.3.5b1 Now Available
You can subscribe to this topic by clicking on the “Subscribe topic” link at the bottom of the page to receive email notifications of new beta versions.
Build Notice: Viscosity 1.3.5b2 Now Available
You can subscribe to this topic by clicking on the “Subscribe topic” link at the bottom of the page to receive email notifications of new beta versions.
Build Notice: Viscosity 1.3.5b3 Now Available
You can subscribe to this topic by clicking on the “Subscribe topic” link at the bottom of the page to receive email notifications of new beta versions.
Build Notice: Viscosity 1.3.5b4 Now Available
You can subscribe to this topic by clicking on the “Subscribe topic” link at the bottom of the page to receive email notifications of new beta versions.
Build Notice: Viscosity 1.3.5b9 Now Available
You can subscribe to this topic by clicking on the “Subscribe topic” link at the bottom of the page to receive email notifications of new beta versions.
Running the 1.3.5b9 beta now. It seem to have fixed that runtime error (YES! THANK YOU!) but i have a question about cosmetics. When I put the menubar icon on the right there are these big gaps between icons – bigger than in the 1.3.4 release
Official release: http://dl.dropbox.com/u/2178780/Viscosity134.png
Beta version: http://dl.dropbox.com/u/2178780/Viscoscitybeta.png
It’s just something that caught my eye right away. I’d like to have those icons closer together since all other menubar icons don’t have such big spaces between them and it looks out of place. Maybe it’s on purpose though since in the current official release one gap is bigger than the other?
I know it’s nit-picky. sorry 
Hi MBHockey,
This was actually intentional on our part. If you enter Lion’s full-screen mode with Viscosity’s icon on the right-hand side, you’ll notice the icon gets cut off. This appears to be a bug with Lion, however as icons are not supposed to be placed over on the right hand side (we are using a “hackish” technique to pull it off) I doubt Apple will be in a hurry to address it. As a temporary workaround we’ve increased the space around the icon under Lion so this doesn’t occur. Obviously we’ll remove this extra space if Apple resolve the problem or we find a better way to workaround the issue.
Cheers,
James
Build Notice: Viscosity 1.3.5b10 Now Available
You can subscribe to this topic by clicking on the “Subscribe topic” link at the bottom of the page to receive email notifications of new beta versions.
Interesting! Thanks for the reply.
Keep up the great work. This is a wonderful piece of software
Build Notice: Viscosity 1.3.5b11 Now Available
You can subscribe to this topic by clicking on the “Subscribe topic” link at the bottom of the page to receive email notifications of new beta versions.
Is there a specific reason Viscosity is using so much ram? Version 1.3.5b10 (1042)
Hi MBHockey,
Wow! No, Viscosity should not be using anywhere near that. Thanks for the report - there must be a memory leak somewhere in the beta. We’ll track it down and release an update.
Cheers,
James
Build Notice: Viscosity 1.3.5rc1 Now Available
You can subscribe to this topic by clicking on the “Subscribe topic” link at the bottom of the page to receive email notifications of new beta versions.
Build Notice: Viscosity 1.4b2 Now Available
You can subscribe to this topic by clicking on the “Subscribe topic” link at the bottom of the page to receive email notifications of new beta versions.
When I try to connect I get the following error
Jul 11 06:41:31: TLS_ERROR: BIO read tls_read_plaintext error: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Jul 11 06:41:31: TLS Error: TLS object → incoming plaintext read error
Jul 11 06:41:31: TLS Error: TLS handshake failed
Jul 11 06:41:31: Fatal TLS error (check_tls_errors_co), restarting
Jul 11 06:41:31: SIGUSR1[soft,tls-error] received, process restarting
Is it a client problem or a server problem???
Hi Jambaleia,
You’ll typically get that error message if the ca/certificate/key files you are using don’t match what the server is using, or they are invalid. Try generating new files for your connection, and then replace the files your connection is using with these (under the Authentication tab when editing your connection in Viscosity).
Cheers,
James
In general I would say yes. But this happens only with the BETA version. If I take the 1.3 version everything is fine.
But the beta version which should work with Mountain lion is not working really good.
I want to use it with the Astaro / Sophos UTM SSL VPN. In the past everything was fine. But now if a DNS Server is entered for remote access the client will connect but will than stop the internet connection.
And the BETA version of the client has the TLS Cert problem. The point is the certs have not changed.
