Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

~ not recognized als /Users/$USER #31

Closed
GoogleCodeExporter opened this issue Jul 13, 2015 · 5 comments
Closed

~ not recognized als /Users/$USER #31

GoogleCodeExporter opened this issue Jul 13, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. create an openvpn config where the location of the certificate is 
~/Library/openvpn
2. connect to that server

What is the expected output? What do you see instead?
The expected output is a successful connection, instead I get an error message 
the the certificate 
file can not be found/

What version of the product are you using? On what operating system?
3.0b9

Please provide any additional information below.
The fix is to change the ca directive in the config to /Users/username/Library 
for it to work but 
this should not be necessary.

Original issue reported on code.google.com by daen...@gmail.com on 17 Sep 2008 at 2:20

@GoogleCodeExporter
Copy link
Author

Please provide your ca line from your config file.

I have ca <cert filename> without providing the full path and things work fine.

Original comment by batman...@gmail.com on 17 Sep 2008 at 10:32

@GoogleCodeExporter
Copy link
Author

Sorry .. misread the steps. This is an openvpn quirk and not a Tunnelblick one. 
You don't need to provide the 
path to the certificate. Simply use:

ca cert_file

Original comment by batman...@gmail.com on 17 Sep 2008 at 10:34

@GoogleCodeExporter
Copy link
Author

Hah... that is seriously strange. So basicaly if the config and the ca file are 
in the same dir everything is happy?

Original comment by daen...@gmail.com on 18 Sep 2008 at 12:14

@GoogleCodeExporter
Copy link
Author

Weird ... this works for cert & key directives, but not for up -- I have to 
specify a
full path to the up script.

Original comment by zet...@gmail.com on 30 Sep 2008 at 4:58

@GoogleCodeExporter
Copy link
Author

Original comment by angelol...@gmail.com on 19 Nov 2008 at 12:47

  • Changed state: WontFix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant