Witopia 256 Bit How To?

Got a problem with Viscosity or need help? Ask here!

Agile Eye

Posts: 2
Joined: Thu Mar 12, 2009 7:24 am

Post by Agile Eye » Thu Mar 12, 2009 7:44 am
I understand that Witopia (whose service I use) have recently enabled 256bit encryption on their servers, and there is a wiki page detailing how to enable this, but for Tunnelblick users:
http://www.wiki.witopia.net/wiki/256_bit_Encryption

Now I'm certainly no tech-head in such matters but am I right in guessing that all I have to do to enable the similar in Viscosity is to change the remote server address to 256vpn.witopia.net in the General tab in preferences and add "cipher AES-256-CBC" under the "Advanced" tab?
Any other changes that I need to make?

While I'm on it, looking through the connections details interface, I sometimes notice the following:
"WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this"
What does this mean, or, how do i make it right?

Thanks in advance from a happy Viscosity user!

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Thu Mar 12, 2009 4:49 pm
Now I'm certainly no tech-head in such matters but am I right in guessing that all I have to do to enable the similar in Viscosity is to change the remote server address to 256vpn.witopia.net in the General tab in preferences and add "cipher AES-256-CBC" under the "Advanced" tab?
Spot on. That is all you should need to do.
What does this mean, or, how do i make it right?
It means OpenVPN will store your username and/or password (if you entered any) in memory, so if the VPN connection drops out and reconnects you won't be re-asked for these details. However it does mean that if you are on a multi-user system (other users are logged in as well), it could be a potential security risk. If the other users are malicious and know what they are doing, they may be able to extract your username/password from system memory. In most cases you don't need to worry about this. However if you wish to stop the warning you can add the "auth-nocache" on a new line under the Advanced tab.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs

Agile Eye

Posts: 2
Joined: Thu Mar 12, 2009 7:24 am

Post by Agile Eye » Thu Mar 12, 2009 9:46 pm
Oh great!
Thanks very much for your speedy response.
:D
3 posts Page 1 of 1