I recently installed version 2.2 and was trying to generate some certificates but keep getting ssl error. I installed an OpenSSL for windows but that didn't help either. This is the error i'm getting: [quote]WARNING: can't open config file: c:\openssl/ssl/openssl.cnf error on line 150 of openssl.cnf 1812:error:0E065068:configuration file routines:STR_COPY:variable has no value:. \crypto\conf\conf_def.c:618:line 150[/quote] Any suggestions?

[quote="janjust"]did you run [code]vars[/code] prior to running an openssl command? I must say that I haven't tested the openssl commands on win7 64bit yet...[/quote] I did yes. Just followed the instruction to the certificate creation portion on the how-to. Perhaps OpenSSL is incompatible with 64 bit systems?

[quote="comcar"][quote="mmason5004"]Exact same thing here. Searched everywhere. Running Win7 X64 Pro. Just made an attempt @ this today. Not sure if this is the issue, but look @ this file system address listed in the error output: "WARNING: can't open config file: c:\openssl/ssl/openssl.cnf" Can that even be a valid NTFS address? Also, nowhere in the tutorial does it say to install SSL on your server/client. This would seem necessary since the batch file is looking for the SSL config file @ an address like that.[/quote] I switched to version 2.14 which doesn't have any problems with this. Maybe install 2.14 first and then upgrade to 2.2 later today, first i need the certs.[/quote] I'll try this first. [quote="sprintf"]I hit the same problem. I think it is due to these lines in openssl.cnf: [code] organizationalUnitName_default = $ENV::KEY_OU commonName_default = $ENV::KEY_CN name_default = $ENV::KEY_NAME ... MODULE_PATH = $ENV::PKCS11_MODULE_PATH PIN = $ENV::PKCS11_PIN [/code] All of these lines refer to environment variables that probably do not exist in your system, hence why openssl barfs. This is probably either a bug in the sample openssl.cnf or a bug in vars.bat. If someone could open up a bug report, that would be great. I worked around the issue by commenting out the lines with #. Thanks.[/quote] And this second... if the first doesn't work. :D Thanks for the advice guys.

Hi. Just for the record... I have the same problem on Windows XP. Runned: 1) init-config 2) vars 3) clean-all 4) build-ca Where build-ca contains the OpenSSl call that gives the error: [i][color=#0000FF]4132:error:0E065068:configuration file routines:STR_COPY:variable has no value:.\crypto\conf\conf_def.c:618:line 150[/color][/i] /Krissi

I was able to get [b]openssl[/b] to work if I put quote marks around the path arguments. However, I DID have a problem with [b]openssl[/b] not recognizing the [b]-config[/b] argument. So for me, I created a directory at c:\openssl\ssl, and have copied my openssl-1.0.0.cnf file to there, renaming it to openssl.cnf: [color=#BF00FF]mkdir c:\openssl\ssl copy openssl-1.0.0.cnf c:\openssl\ssl\openssl.cnf[/color] And then I put quote marks around the arguments in the build-ca.bat file: [color=#0040FF]openssl req -days 3650 -nodes -new -x509 -keyout "%KEY_DIR%\ca.key" -out "%KEY_DIR%\ca.crt" [/color] And that seemed to work.

OpenSSL error Win7 x64

comcar

I recently installed version 2.2 and was trying to generate some certificates but keep getting ssl error.

I installed an OpenSSL for windows but that didn't help either.

This is the error i'm getting:

WARNING: can't open config file: c:\openssl/ssl/openssl.cnf
error on line 150 of openssl.cnf
1812:error:0E065068:configuration file routines:STR_COPY:variable has no value:.
\crypto\conf\conf_def.c:618:line 150

Any suggestions?

mmason5004

Exact same thing here. Searched everywhere. Running Win7 X64 Pro. Just made an attempt @ this today.

Not sure if this is the issue, but look @ this file system address listed in the error output:
"WARNING: can't open config file: c:\openssl/ssl/openssl.cnf"

Can that even be a valid NTFS address? Also, nowhere in the tutorial does it say to install SSL on your server/client. This would seem necessary since the batch file is looking for the SSL config file @ an address like that.

comcar

mmason5004 wroteExact same thing here. Searched everywhere. Running Win7 X64 Pro. Just made an attempt @ this today.

Not sure if this is the issue, but look @ this file system address listed in the error output:
"WARNING: can't open config file: c:\openssl/ssl/openssl.cnf"

Can that even be a valid NTFS address? Also, nowhere in the tutorial does it say to install SSL on your server/client. This would seem necessary since the batch file is looking for the SSL config file @ an address like that.

I switched to version 2.14 which doesn't have any problems with this.

Maybe install 2.14 first and then upgrade to 2.2 later today, first i need the certs.

janjust

did you run

vars

prior to running an openssl command?

I must say that I haven't tested the openssl commands on win7 64bit yet...

mmason5004

janjust wrotedid you run

vars

prior to running an openssl command?

I must say that I haven't tested the openssl commands on win7 64bit yet...

I did yes. Just followed the instruction to the certificate creation portion on the how-to. Perhaps OpenSSL is incompatible with 64 bit systems?

sprintf

I hit the same problem. I think it is due to these lines in openssl.cnf:

organizationalUnitName_default = $ENV::KEY_OU
commonName_default = $ENV::KEY_CN
name_default = $ENV::KEY_NAME
...
MODULE_PATH = $ENV::PKCS11_MODULE_PATH
PIN = $ENV::PKCS11_PIN

All of these lines refer to environment variables that probably do not exist in your system, hence why openssl barfs. This is probably either a bug in the sample openssl.cnf or a bug in vars.bat. If someone could open up a bug report, that would be great.

I worked around the issue by commenting out the lines with #.

Thanks.

mmason5004

comcar wrote
mmason5004 wroteExact same thing here. Searched everywhere. Running Win7 X64 Pro. Just made an attempt @ this today.

Not sure if this is the issue, but look @ this file system address listed in the error output:
"WARNING: can't open config file: c:\openssl/ssl/openssl.cnf"

Can that even be a valid NTFS address? Also, nowhere in the tutorial does it say to install SSL on your server/client. This would seem necessary since the batch file is looking for the SSL config file @ an address like that.
I switched to version 2.14 which doesn't have any problems with this.

Maybe install 2.14 first and then upgrade to 2.2 later today, first i need the certs.

I'll try this first.

sprintf wroteI hit the same problem. I think it is due to these lines in openssl.cnf:
organizationalUnitName_default = $ENV::KEY_OU
commonName_default = $ENV::KEY_CN
name_default = $ENV::KEY_NAME
...
MODULE_PATH = $ENV::PKCS11_MODULE_PATH
PIN = $ENV::PKCS11_PIN
All of these lines refer to environment variables that probably do not exist in your system, hence why openssl barfs. This is probably either a bug in the sample openssl.cnf or a bug in vars.bat. If someone could open up a bug report, that would be great.

I worked around the issue by commenting out the lines with #.

Thanks.

And this second... if the first doesn't work. 😃

Thanks for the advice guys.

Krissi

Hi.

Just for the record... I have the same problem on Windows XP.

Runned:
1) init-config
2) vars
3) clean-all
4) build-ca

Where build-ca contains the OpenSSl call that gives the error:
4132:error:0E065068:configuration file routines:STR_COPY:variable has no value:.\crypto\conf\conf_def.c:618:line 150

/Krissi

Krissi

Hi all.

Two things:

1)
You might need to add this to the "vars.bat" file:
set KEY_OU=""
set KEY_CN=""
set KEY_NAME=""
set PKCS11_MODULE_PATH=dummy
set PKCS11_PIN=dummy

2)
It looks to me that OpenSSL doesn't handle spaces in the DIR name. So if you have installed OpenVPN under a "Program Files" directory it can help to use a path that is defined with the short name convention and not the long name. In Windows you can always see the short name of a file or directory by using "dir /X".

Example based on a program directory at "C:\Program Files\" where the short name is "C:\PROGRA~1\"

build-ca.bat contains the line:
openssl req -days 3650 -nodes -new -x509 -keyout %KEY_DIR%\ca.key -out %KEY_DIR%\ca.crt -config %KEY_CONFIG%

replace this with:
openssl req -days 3650 -nodes -new -x509 -keyout C:\PROGRA~1\OpenVPN\easy-rsa\keys\ca.key -out C:\PROGRA~1\OpenVPN\easy-rsa\keys\ca.crt -config C:\PROGRA~1\OpenVPN\easy-rsa\openssl.cnf

Note:
you might also need to do this for the other BAT files as "build-key-server.bat"

This worked for me... hope it helps U2.

/Krissi

mumbles

I was able to get openssl to work if I put quote marks around the path arguments. However, I DID have a problem with openssl not recognizing the -config argument.

So for me, I created a directory at c:\openssl\ssl, and have copied my openssl-1.0.0.cnf file to there, renaming it to openssl.cnf:
mkdir c:\openssl\ssl
copy openssl-1.0.0.cnf c:\openssl\ssl\openssl.cnf

And then I put quote marks around the arguments in the build-ca.bat file:
openssl req -days 3650 -nodes -new -x509 -keyout "%KEY_DIR%\ca.key" -out "%KEY_DIR%\ca.crt"

And that seemed to work.

radiocolin

3 years later and they still haven't fixed this issue.

I've been fighting with the implementation on DD-WRT for 2 days, thought I'd try 64 bit Windows instead. This error still happens.

Tried the 32 bit version, and clean-all.bat empties the easy-rsa directory of all the scripts.

What a joke.

stuyu

The easiest way it works for me was to add one simple line in all build-wathever batch files:
call vars.bat

And put some extra lines in init-config.bat:

if not exist keys mkdir keys
mkdir c:\etc\ssl
for /f "tokens=5" %%i in ('dir ^| findstr openssl') do set CONF=%%i
mklink /H "c:\etc\ssl\openssl.cnf" "%ProgramFiles%\OpenVPN\easy-rsa\%CONF%"
echo link to %CONF% created for openvpn unix like behavior