ta.key in unified form ovpn profile?
-
- OpenVpn Newbie
- Posts: 2
- Joined: Tue Jan 22, 2013 8:31 pm
ta.key in unified form ovpn profile?
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?
-
- OpenVpn Newbie
- Posts: 2
- Joined: Wed Jan 23, 2013 12:34 am
Re: ta.key in unified form ovpn profile?
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?
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
- OpenVPN Inc.
- Posts: 169
- Joined: Thu Jan 24, 2013 12:13 am
Re: ta.key in unified form ovpn profile?
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>
-
- OpenVpn Newbie
- Posts: 2
- Joined: Wed Jan 23, 2013 12:34 am
Re: ta.key in unified form ovpn profile?
Works perfectly! Thanks for the reply.
-
- OpenVpn Newbie
- Posts: 2
- Joined: Tue Jan 22, 2013 8:31 pm
Re: ta.key in unified form ovpn profile?
Yes, that's it. Thanks a lot!