as opposed to this:$VAR1 = 'dbi:mysql:database=database;host=localhost;port=3306;mysql_ss +l=1;mysql_ssl_ca_file=GLOB(0x1008060e8);mysql_ssl_client_key=GLOB(0x1 +0082e750);mysql_ssl_client_cert=GLOB(0x100806268)';
I'm currently using File::Temp, but it writes temp files out to the filesystem, which I'm trying to avoid. Having these certs in the source and present in the running process is one thing. I'm trying to avoid introducing another vector by writing them out to a third location. I'm looking into the named pipe solution, which will be tricky given that we're wrapping this code into a binary using PerlApp, and that it needs to run on Solaris, Linux and Windows.$VAR1 = 'dbi:mysql:database=database;host=localhost;port=3306;mysql_ss +l=1;mysql_ssl_ca_file=/path/to/my/ca-cert.pem;mysql_ssl_client_key=/p +ath/to/my/client-key.pem;mysql_ssl_client_cert=/path/to/my/client-cer +t.pem';
In reply to Re^2: DBD::mysql w/SSL certs extracted from variables
by wwinfrey
in thread DBD::mysql w/SSL certs extracted from variables
by wwinfrey
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |