ta.key in unified form ovpn profile?

[Specky]

We converted the openvpn profile by integrating ca.crt, client.crt and client.key using the XML-syntax. But our configuration is needing the ta.key, too. Is there a way to integrate it into the profile? If yes, how?

[jjwebster]

I am having the same issue. <ca>, <cert>, and <key> tags work fine. It accepts <tls-auth>, but without the direction directive, the connection fails. In other instances on Mac/Windows, I have used:

tls-auth [inline] 1

prior to the <tls-auth> tag... but that causes the import to fail within the iOS app with an error that the tls-auth file does not exist.

How does one specify tls direction using unified form?

[jamesyonan]

There is a key-direction directive you can use to specify the key direction when the tls-auth key is inline. For example:

Code: Select all

key-direction 1

<tls-auth>
-----BEGIN OpenVPN Static key V1-----
. . .
-----END OpenVPN Static key V1-----
</tls-auth>

[jjwebster]

Works perfectly! Thanks for the reply.

[Specky]

Yes, that's it. Thanks a lot!