OpenVPN: 'Private key password verification failed' with verified config
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
0
down vote
favorite
I installed OpenVPN with:
$ sudo apt-get install openvpn
I then run the client with the config file I received from my company.
$ sudo openvpn --config myconfig.ovpn
The config has been verified working on a colleague's machine. But one exception: My colleague is using a Windows system, I'm using Debian.
Error
Fri Jul 27 11:33:34 2018 OpenVPN 2.4.0 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 18 2017
Fri Jul 27 11:33:34 2018 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.08
Fri Jul 27 11:33:34 2018 Error: private key password verification failed
Fri Jul 27 11:33:34 2018 Exiting due to fatal error
Prerequisites
- Debian Stretch LXDE (latest)
- No server environment installed
- No Pre-VPN environments installed
Contents of the config
client
dev tun
proto udp
remote example.com 1194
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
tls-version-min 1.2
verify-x509-name server_pZFAVxw3z2VPJhKI name
cipher AES-256-CBC
auth SHA256
compress lz4
verb 3
<ca>
-----BEGIN CERTIFICATE-----
<<base64>>
-----END CERTIFICATE-----
</ca>
<cert>
-----BEGIN CERTIFICATE-----
<<base64>>
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,C6B57204A2ECC239
<<base64>>
-----END RSA PRIVATE KEY-----
</key>
<tls-crypt>
#
# 2048 bit OpenVPN static key
#
-----BEGIN OpenVPN Static key V1-----
<<base64>>
-----END OpenVPN Static key V1-----
</tls-crypt>
The official OpenVPN manual recommends my way of trying to run it. So I'm out of knowledge what the problem could be and seeking for help.
What could be the reason for the error?
debian openvpn
add a comment |Â
up vote
0
down vote
favorite
I installed OpenVPN with:
$ sudo apt-get install openvpn
I then run the client with the config file I received from my company.
$ sudo openvpn --config myconfig.ovpn
The config has been verified working on a colleague's machine. But one exception: My colleague is using a Windows system, I'm using Debian.
Error
Fri Jul 27 11:33:34 2018 OpenVPN 2.4.0 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 18 2017
Fri Jul 27 11:33:34 2018 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.08
Fri Jul 27 11:33:34 2018 Error: private key password verification failed
Fri Jul 27 11:33:34 2018 Exiting due to fatal error
Prerequisites
- Debian Stretch LXDE (latest)
- No server environment installed
- No Pre-VPN environments installed
Contents of the config
client
dev tun
proto udp
remote example.com 1194
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
tls-version-min 1.2
verify-x509-name server_pZFAVxw3z2VPJhKI name
cipher AES-256-CBC
auth SHA256
compress lz4
verb 3
<ca>
-----BEGIN CERTIFICATE-----
<<base64>>
-----END CERTIFICATE-----
</ca>
<cert>
-----BEGIN CERTIFICATE-----
<<base64>>
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,C6B57204A2ECC239
<<base64>>
-----END RSA PRIVATE KEY-----
</key>
<tls-crypt>
#
# 2048 bit OpenVPN static key
#
-----BEGIN OpenVPN Static key V1-----
<<base64>>
-----END OpenVPN Static key V1-----
</tls-crypt>
The official OpenVPN manual recommends my way of trying to run it. So I'm out of knowledge what the problem could be and seeking for help.
What could be the reason for the error?
debian openvpn
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I installed OpenVPN with:
$ sudo apt-get install openvpn
I then run the client with the config file I received from my company.
$ sudo openvpn --config myconfig.ovpn
The config has been verified working on a colleague's machine. But one exception: My colleague is using a Windows system, I'm using Debian.
Error
Fri Jul 27 11:33:34 2018 OpenVPN 2.4.0 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 18 2017
Fri Jul 27 11:33:34 2018 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.08
Fri Jul 27 11:33:34 2018 Error: private key password verification failed
Fri Jul 27 11:33:34 2018 Exiting due to fatal error
Prerequisites
- Debian Stretch LXDE (latest)
- No server environment installed
- No Pre-VPN environments installed
Contents of the config
client
dev tun
proto udp
remote example.com 1194
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
tls-version-min 1.2
verify-x509-name server_pZFAVxw3z2VPJhKI name
cipher AES-256-CBC
auth SHA256
compress lz4
verb 3
<ca>
-----BEGIN CERTIFICATE-----
<<base64>>
-----END CERTIFICATE-----
</ca>
<cert>
-----BEGIN CERTIFICATE-----
<<base64>>
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,C6B57204A2ECC239
<<base64>>
-----END RSA PRIVATE KEY-----
</key>
<tls-crypt>
#
# 2048 bit OpenVPN static key
#
-----BEGIN OpenVPN Static key V1-----
<<base64>>
-----END OpenVPN Static key V1-----
</tls-crypt>
The official OpenVPN manual recommends my way of trying to run it. So I'm out of knowledge what the problem could be and seeking for help.
What could be the reason for the error?
debian openvpn
I installed OpenVPN with:
$ sudo apt-get install openvpn
I then run the client with the config file I received from my company.
$ sudo openvpn --config myconfig.ovpn
The config has been verified working on a colleague's machine. But one exception: My colleague is using a Windows system, I'm using Debian.
Error
Fri Jul 27 11:33:34 2018 OpenVPN 2.4.0 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 18 2017
Fri Jul 27 11:33:34 2018 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.08
Fri Jul 27 11:33:34 2018 Error: private key password verification failed
Fri Jul 27 11:33:34 2018 Exiting due to fatal error
Prerequisites
- Debian Stretch LXDE (latest)
- No server environment installed
- No Pre-VPN environments installed
Contents of the config
client
dev tun
proto udp
remote example.com 1194
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
tls-version-min 1.2
verify-x509-name server_pZFAVxw3z2VPJhKI name
cipher AES-256-CBC
auth SHA256
compress lz4
verb 3
<ca>
-----BEGIN CERTIFICATE-----
<<base64>>
-----END CERTIFICATE-----
</ca>
<cert>
-----BEGIN CERTIFICATE-----
<<base64>>
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,C6B57204A2ECC239
<<base64>>
-----END RSA PRIVATE KEY-----
</key>
<tls-crypt>
#
# 2048 bit OpenVPN static key
#
-----BEGIN OpenVPN Static key V1-----
<<base64>>
-----END OpenVPN Static key V1-----
</tls-crypt>
The official OpenVPN manual recommends my way of trying to run it. So I'm out of knowledge what the problem could be and seeking for help.
What could be the reason for the error?
debian openvpn
edited Aug 2 at 16:58
slmâ¦
232k65479649
232k65479649
asked Jul 27 at 9:53
codekandis
5511
5511
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
After some trying with another Linux-System I found out there was of course a problem with the used private key password d;.Jo$HhqA2l7yMd :Wx
.
If one ever creates a configuration the private key inside <key></key>
should be extracted in a separate file and then verified with openssl rsa -in client.key -check
afterwards.
I don't know what exactly caused the password to fail. I tried several new configurations with random passwords and neither a $
nor a whitespace caused a fail again.
Interesting is also the fact that on a windows system the password was accepted.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
After some trying with another Linux-System I found out there was of course a problem with the used private key password d;.Jo$HhqA2l7yMd :Wx
.
If one ever creates a configuration the private key inside <key></key>
should be extracted in a separate file and then verified with openssl rsa -in client.key -check
afterwards.
I don't know what exactly caused the password to fail. I tried several new configurations with random passwords and neither a $
nor a whitespace caused a fail again.
Interesting is also the fact that on a windows system the password was accepted.
add a comment |Â
up vote
0
down vote
accepted
After some trying with another Linux-System I found out there was of course a problem with the used private key password d;.Jo$HhqA2l7yMd :Wx
.
If one ever creates a configuration the private key inside <key></key>
should be extracted in a separate file and then verified with openssl rsa -in client.key -check
afterwards.
I don't know what exactly caused the password to fail. I tried several new configurations with random passwords and neither a $
nor a whitespace caused a fail again.
Interesting is also the fact that on a windows system the password was accepted.
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
After some trying with another Linux-System I found out there was of course a problem with the used private key password d;.Jo$HhqA2l7yMd :Wx
.
If one ever creates a configuration the private key inside <key></key>
should be extracted in a separate file and then verified with openssl rsa -in client.key -check
afterwards.
I don't know what exactly caused the password to fail. I tried several new configurations with random passwords and neither a $
nor a whitespace caused a fail again.
Interesting is also the fact that on a windows system the password was accepted.
After some trying with another Linux-System I found out there was of course a problem with the used private key password d;.Jo$HhqA2l7yMd :Wx
.
If one ever creates a configuration the private key inside <key></key>
should be extracted in a separate file and then verified with openssl rsa -in client.key -check
afterwards.
I don't know what exactly caused the password to fail. I tried several new configurations with random passwords and neither a $
nor a whitespace caused a fail again.
Interesting is also the fact that on a windows system the password was accepted.
edited Aug 4 at 15:04
answered Aug 4 at 13:03
codekandis
5511
5511
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f458800%2fopenvpn-private-key-password-verification-failed-with-verified-config%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password