Page 1 of 1

[bug] key-direction not imported

Posted: Wed Nov 28, 2018 9:41 am
by ratness
Mac 1.7.13b2

Using a config with 'tls-auth ta.key 1' imports fine, and (Preference, connectionname, Authentication) shows ta.key and Direction 1. Good.

Using a config with 'tls-auth [inline] 1' and a '<tls-auth>keygoeshere</tls-auth>' section imports fine, and )Preference, connectionname, Authentication) shows ta.key and Direction 1. Good.

Using a config with 'key-direction 1' and a '<tls-auth>keygoeshere</tls-auth>' imports fine, but (Preference, connectionname, Authentication) shows ta.key and Direction 'Default' instead of '1'. Not good. Shuffling 'key-direction' around in the import file, like putting the line after the inline file, doesn't change anything.

Upon import, the config.conf has 'tls-auth ta.key' and 'key-direction 1'

If I edit the connection in the gui and save the Direction as '1', config.conf cuts over to 'tls-auth ta.key 1' and 'key-direction 1'

I have no indication that this is a regression. i just discovered it while messing with prospective configs. Once imported, I can change it, which makes this different than a report from last year, I think.

Re: [bug] key-direction not imported

Posted: Wed Nov 28, 2018 1:11 pm
by James
Hi ratness,

Thanks for the detailed report. We'll make sure this is fixed in the next beta update.

Thanks,
James

Re: [bug] key-direction not imported

Posted: Sun Jan 26, 2020 5:50 am
by jamessnell
I can confirm this issue still affects me, with Viscosity version 1.8.4 (1528), under macOS Catalina 10.15.2.