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

include shell environment variable while parsing the openssl.cnf #2

Open
boogiebug opened this issue Aug 24, 2010 · 4 comments
Open

Comments

@boogiebug
Copy link

Hi,

Just wonder if you have any plan to includ the code of expanding the $ENV:<env_name> variables while parsing the openssl.cnf file? This seem to be a standard openssl.cnf format and a lot of application using this format, including the easy-rsa that are recommended by a lot of OpenVPN's how-to document.

rgds.

@lkeijser
Copy link
Owner

Hi,

In my openssl.cnf (fedora 13) i only see the HOME variable, which is probably useless with StoneVPN. Do you mean the location of the index, serial-and crl file and directory where certificates are stored?

If so, i guess i could code it in such a way that these locations are taken from the openssl.cnf file, unless explicitly specified in stonevpn.conf. This way it would be backward compatible with previous versions of stonevpn.

But perhaps this isn't what you mean at all :) Let me know!

kind regards,

Léon

@boogiebug
Copy link
Author

Hi,

I "guess" that the following list is some of the variables those taking effect in the stoneVPN.

$ENV:KEY_DIR
$ENV:KEY_SIZE
$ENV:KEY_COUNTRY and other contact information (which are in indirectly referred to as the 'default' information)

Although they are quite static and I can manually replace them but it might be helpful for the newbie if the StoneVPN can automatically parse these variables.

Anyway, I'm o glad to know that this project is still active, thanks for the effort you have contributed to such a great tool like this. ;)

best rgds.
Chawalit

@lkeijser
Copy link
Owner

Hi,

I've added it to my TODO list and will try to get it into the next version.

Thanks for the comment, and nice to know you're happy using it :)

kind regards,

Léon

@trueneu
Copy link

trueneu commented Nov 6, 2015

I did it in my fork, in a pretty ugly way though due to the lack of time.
Thanks for such a nice piece of software, by the way!

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

No branches or pull requests

3 participants