ability to do OpenSSL initialization outside of luacrypto

[mkottman]

ability to do OpenSSL initialization outside of luacrypto

[mkottman]

Hi, that's a good idea, however I am thinking on how to implement this in such a way that existing code using this library is not affected. There are several possibilities:

• Add a function called init() which calls OpenSSL_add_all_digests() and OpenSSL_add_all_ciphers(). However, existing code would need to be changed and simple one-liners would need to be extended, something I want to avoid.
• Use an environment variable such as OPENSSL_INITIALIZED, which if set to anything, the module would not call the initialization functions.
• Detect if any digests/ciphers are available (something like: if #crypto.list('digests') + #crypto.list('ciphers') == 0 then ... end), and call the functions if no ciphers/digests are available.

Which do you think would be best?

[IlyaM]

- Add a function called init() which calls OpenSSL_add_all_digests() and OpenSSL_add_all_ciphers(). However, existing code would need to be changed and simple one-liners would need to be extended, something I want to avoid.

I don't like this option as well. For simple use cases luacrypto library should just work out of box.

- Use an environment variable such as OPENSSL_INITIALIZED, which if set to anything, the module would not call the initialization functions.

Not sure if I like this option. Normally environment variables are used to configure behavior of application by users and not configure behavior of library by application. Details of openssl initialization is application logic which shouldn't be configurable by user.

- Detect if any digests/ciphers are available (something like: `if #crypto.list('digests') + #crypto.list('ciphers') == 0 then ... end`), and call the functions if no ciphers/digests are available.

On the first glance it should work assuming that OpenSSL's internal table of digest algorithms and ciphers is expected to be completely empty without explicit initialization.

Which do you think would be best?

Another simple option is to make this behavior configurable at compile time. At least for me having simple #ifdef around OpenSSL_add_all_digests() and OpenSSL_add_all_ciphers() calls would work.

[mkottman]

Another simple option is to make this behavior configurable at compile time. At least for me having simple #ifdef around OpenSSL_add_all_digests() and OpenSSL_add_all_ciphers() calls would work.

Okay, honestly I was only thinking of runtime options. Because this is so simple, I will add a compile flag that will add external initialization of OpenSSL.