Skip to content
[bug] key-direction not imported
Suggestions/comments/criticisms are welcome here
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.
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.
- Posts: 1
- Joined: Sun Jan 26, 2020 5:49 am
I can confirm this issue still affects me, with Viscosity version 1.8.4 (1528), under macOS Catalina 10.15.2.
3 posts
Page 1 of 1