Active Topics

 


Reply
Thread Tools
Posts: 150 | Thanked: 169 times | Joined on Nov 2011 @ Sweden
#1
I have all necessary files, including ivacy-client.crt, in /etc/openvpn/ - but this is the message I get trying to open the connection in xterm:

Code:
/home/user # openvpn --config /etc/openvpn/ivacy-client.ovpn
Sun Nov 27 17:01:47 2011 OpenVPN 2.2.0 arm-linux-gnueabi [SSL] [LZO2] [EPOLL] [eurephia] [MH] [PF_INET6] [IPv6 payload 20110424-2 (2.2RC2)] built on Aug 20 2011
Enter Auth Username:xxxxxxx
Enter Auth Password:
Sun Nov 27 17:02:07 2011 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Sun Nov 27 17:02:07 2011 Cannot load certificate file ivacy-client.crt: error:02001002:system library:fopen:No such file or directory: error:20074002:BIO routines:FILE_CTRL:system lib: error:140AD002:SSL routines:SSL_CTX_use_certificate_file:system lib
Sun Nov 27 17:02:07 2011 Exiting
If it is it saying that ivacy-client.crt is missing, what are the possible reasons? All the files are ANSI-coded and the file names are double-checked.

All relevant files can be found at this link if they are of any help. Please disregard the Windows XP headline, the files are not os-specific, but that's the only place to get them. I have no problem connecting to the Ivacy VPN on desktop Linux with these very same files I now put on the N900.

Last edited by bocephus; 2011-11-27 at 16:19.
 
merlin1991's Avatar
Posts: 125 | Thanked: 1,142 times | Joined on Feb 2010 @ Austria
#2
did you try with setting a full path to the cert in /etc/openvpn/ivacy-client.ovpn?
__________________
"Fog is neither water nor air, it's something between." Merlin
 
Posts: 150 | Thanked: 169 times | Joined on Nov 2011 @ Sweden
#3
No! I did now! It seems that took care of that problem! However, I got another instead:

Code:
Cannot load certificate file /etc/openvpn/ivacy-client.crt: error:0906D06C:PEM routines:PEM_read_bio:no start line: error:140AD009:SSL routines:SSL_CTX_use_certificate_file:PEM lib
No start line? That would indicate an encoding problem with the cert-file, or? It is ANSI, and this is how it starts:

Code:
  Certificate:
  Data:
  	Version: 3 (0x2)
  	Serial Number: 2 (0x2)
  	Signature Algorithm: sha1WithRSAEncryption
  	Issuer: C=RU, ST=MR, L=Moscow, O=ivacy.com, CN=ivacy.com

Last edited by bocephus; 2011-11-27 at 16:28.
 

The Following User Says Thank You to bocephus For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 05:09.