Configuration not saving

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

balbers

Posts: 1
Joined: Wed Jul 22, 2009 10:16 am

Post by balbers » Wed Jul 22, 2009 10:21 am
Using Viscosity 1.0.5 on Mac OS X 10.5.7.

I have not been able to successfully connect. After going into the "Certificates" page and choosing my CA, Cert, Key, and TLS-Auth, as well as my other settings, I save my profile.

However, whenever I reopen the "Certificates" page, my chosen values are reset to the original defaults. For example, even though I selected my Cert to be a file named "client.crt", when I reopen the "Certificates" page it is right back to the default "cert.crt". Needless to say, my connection is not working. Other settings seem to persist past loading and saving the connection profile just fine.

Is there some reason why the chosen Certificate values would be reset, or not be saved?

tlewis

Posts: 1
Joined: Wed Jul 22, 2009 8:27 pm

Post by tlewis » Wed Jul 22, 2009 8:32 pm
I am experiencing the same problem as well. When looking at the console output while connecting, it shows that it is not using the keys and certificates that I enter, but reverts to using the default entries.

James

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

Post by James » Wed Jul 29, 2009 6:51 am
when I reopen the "Certificates" page it is right back to the default "cert.crt"
Viscosity should be correctly using your newly specified certificate/keys. What it is doing is copying the certificate/key file to the connection's profile folder, and then renaming the file to a generic name to avoid clashes. This process takes place when you click the Save button, so when you edit your connection the next time you'll see the generic certificate/key names again (however these are not the same certificates/keys as before).

While this system works well at avoiding clashes (during the beta period we kept running into issues where people were trying to use CA and Cert files with the same name), it does create some confusion. I'm currently looking into changing this behaviour in version 1.1 so Viscosity will only rename a certificate/key file if it detects that there will be a clash.

Cheers,
James
James Bekkema
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
3 posts Page 1 of 1