Error On Line 117 Of Openssl.cnf
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Specialised Support Ubuntu Servers, Cloud and Juju Server Platforms Open VPN cannot run ./build-ca Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 11 Thread: Open VPN cannot run ./build-ca Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode April 22nd, 2014 #1 dcorwin822 View Profile View Forum Posts Private Message Visit Homepage First Cup of Ubuntu Join Date May 2007 Beans 11 DistroUbuntu 7.04 Feisty Fawn Open VPN cannot run ./build-ca When I try to run I get the following error: Code: error on line 198 of /etc/openvpn/easy-rsa/openssl-1.0.0.cnf 140224783447712:error:0E065068:configuration file routines:STR_COPY:variable has no value:conf_def.c:618:line 198 line 198 of openssl-1.0.0.cnf reads: Code: subjectAltName=$ENV::KEY_ALTNAMES Adv Reply April 22nd, 2014 #2 dcorwin822 View Profile View Forum Posts Private Message Visit Homepage First Cup of Ubuntu Join Date May 2007 Beans 11 DistroUbuntu 7.04 Feisty Fawn Re: Open VPN cannot run ./build-ca I'm a idiot. I just added the following line to the vars file. working correctly now. export KEY_ALTNAMES="something" Adv Reply May 21st, 2014 #3 jeremiah-l-marks View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date May 2014 Beans 1 Re: Open VPN cannot run ./build-ca you may call yourself an idiot, but your comment certinaly helped me. Thank you. Adv Reply June 19th, 2014 #4 Jacob_Tennant View Profile View Forum Posts Private Message 5 Cups of Ubuntu Join Date Sep 2013 Location Morgantown,WV Beans 24 DistroUbuntu Re: Open VPN cannot run ./build-ca I have the same problem and tried adding exportKEY_ALT
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow https://ubuntuforums.org/showthread.php?t=2218935 Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up OpenSSL and error in reading openssl.conf file up vote 71 down vote favorite 26 I am running windows xp 32bit I just downloaded Openssl from http://stackoverflow.com/questions/7360602/openssl-and-error-in-reading-openssl-conf-file the following URL and installed it. http://www.slproweb.com/products/Win32OpenSSL.html and then i tried to create a self signed certificate by using the following command openssl req -x509 -days 365 -newkey rsa:1024 -keyout hostkey.pem -nodes -out hostcert.pem then it started giving the following error Unable to load config info from /usr/local/ssl/openssl.cnf Then after googling sometime i changed the above command to openssl req -config C:\OpenSSL\bin\openssl.conf -x509 -days 365 -newkey rsa:1024 -keyout hostkey.pem -nodes -out hostcert.pem But now i get the following error in the command prompt error on line -1 of C:\OpenSSL\bin\openssl.conf 4220:error:02001002:system library:fopen:No such file or directory:.\crypto\bio\bss_file.c:126:fopen('C:\OpenSSL\bin\openssl.conf','rb') 4220:error:2006D080:BIO routines:BIO_new_file:no such file:.\crypto\bio\bss_file.c:129: 4220:error:0E078072:configuration file routines:DEF_LOAD:no such file:.\crypto\conf\conf_def.c:197: Please help. Thanks in advance. windows configuration openssl environment-variables share|improve this question edited Mar 29 at 10:57 jww 35.4k21112224 asked Sep 9 '11 at 10:55 Sreeram 1,37242143 2 check exact filename: openssl.conf ---> openssl.cnf –Mark Oct 15 '14 at 22:33 1 the file extension
Sign in Pricing Blog Support Search GitHub This repository Watch 18 Star 132 Fork 29 mistydemeo/tigerbrew Code Issues https://github.com/mistydemeo/tigerbrew/issues/117 100 Pull requests 3 Projects 0 Wiki Pulse Graphs New http://commandlinefanatic.com/cgi-bin/showarticle.cgi?article=art030 issue error with openssl and a workaround #117 Open ppcluddite opened this Issue Sep 8, 2013 · 12 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 2 participants ppcluddite commented Sep 8, 2013 Hi, error on I'm trying to set up openvpn and generate private keys with the easy-rsa scripts (In other package managers, easy-rsa comes with openvpn by default, but with Tigerbrew I had manually download and copy it to my /private/etc/openvpn folder). When running one of the scripts, ./build-key-server servername, I get this error: Using configuration from /private/etc/openvpn/easy-rsa/2.0/openssl.cnf error on line sha256 is an unsupported message digest type 314:error:02001002:system library:fopen:No such file or directory:bss_file.c:104:fopen('/private/etc/openvpn/easy-rsa/2.0/keys/index.txt.attr','rb') 314:error:2006D080:BIO routines:BIO_new_file:no such file:bss_file.c:107: 314:error:0E064072:configuration file routines:CONF_load:no such file:conf_def.c:197: Some googling led me to believe it's an openssl issue, and also to edit /private/etc/openvpn/easy-rsa/2.0/openssl.cnf, replacing both instances of "default_md = sha256" with "default_md = sha1", and now it works. But from what I know, sha1 isn't as secure as sha256, so how do I get it to use sha256? Is this a Homebrew issue? 'Cause when I tested the scripts in Debian and with Macports, I didn't get the error. Any insights? Also, another error I encountered with the Tigerbrew version that I didn't see in Debian or Macports: /private/etc/openvpn/easy-rsa/2.0 root# . ./vars No /private/etc/openvpn/easy-rsa/2.0/openssl.cnf file could be found Further invocations will fail Googling led me to fix this by creating a symlink from /private/etc/openvpn/easy-rsa/2.0/openssl-1.0.0.cnf to /private/etc/openvpn/easy-rsa/2.0/openssl.cnf. Hence all the references above to openssl.cnf. Here's the Ubuntu thread that showed the fix, including a more comprehensive
internet servers and clients. OpenSSL, however, in addition to providing a library for integration, includes a useful command line tool that can be used for effectively every aspect of SSL/PKI administration. It's a bit under-documented though; this post doesn't aim to fully document it, but I've come across some fairly useful shortcuts that I thought I'd share with you, in "cookbook" style format. Get help on OpenSSL subcommands The OpenSSL command-line application is a wrapper application for many "sub-programs". When you invoke OpenSSL from the command line, you must pass the name of a sub-program to invoke such as ca, x509, asn1parse, etc. However, if you want information on these sub-programs, the OpenSSL man page isn't going to be much help. Instead, each one has its own man page, so to see the options available for openssl x509, type:
$ man x509See the raw structure of an ASN.1 file SSL is an implementation of a Public-Key Infrastructure (PKI) and as such, deals quite a bit with certificates. In fact, it's safe to say that if something goes wrong with an SSL setup, there's a 90% probability that a misconfigured certificate will end up being the root cause. Certificates (X.509 certificates, to be precise) are described in a formal language called "ASN.1" or Abstract Syntax Notation (.1). (ASN.1 is somewhat similar, at least in concept, to XML or JSON). There are quite a few different sorts of file associated with certificates, and there are no standards on exactly how they should be named or what extensions they should use. When presented with a mysterious PKI-related file, viewing the raw structure can be helpful in determining what exactly you're dealing with or possibly what's gone wrong with it. However, if you open one up in, say, a text editor, it probably looks something like:
MIICbDCCAioCAQAwaDELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlRYMQ4w