SSL context options for in memory cert and pk

[lunter2]

Description

It is dangerous to store certificates and privateKeys (without a password) on the disk. Unfortunately, this is needed to load the * .p12 file into stream_context_create.

Please, add the option to set certificates and privateKeys from string content or at least from Data URLs, instead the file path only.

// Using string content
// --------------------

openssl_pkcs12_read(file_get_contents('cert.p12'),$certificates,'pass');

$stream_context = stream_context_create(
[ 'ssl' => [ 'local_cert' => $certificates['cert'],
             'local_pk'   => $certificates['pkey']
           ]
]);

// Using Data URLs
// ---------------

openssl_pkcs12_read(file_get_contents('cert.p12'),$certificates,'pass');

$stream_context = stream_context_create(
[ 'ssl' => [ 'local_cert' => 'data:,'.$certificates['cert'],
             'local_pk'   => 'data:,'.$certificates['pkey']
           ]
]);

// Hack: temp files
// ----------------

openssl_pkcs12_read(file_get_contents('cert.p12'),$certificates,'pass');

file_put_contents('cert.temp',$certificates['cert']);
file_put_contents('pkey.temp',$certificates['pkey']);

$stream_context = stream_context_create(
[ 'ssl' => [ 'local_cert' => 'cert.temp',
             'local_pk'   => 'pkey.temp'
           ]
]);

Expected result: Reading certificates and privateKeys without temp files.
Actual result: Reading certificates and privateKeys only with temp files.

PHP Version

PHP 8.1.1

Operating System

All

[cmb69]

This doesn't look like a bug; it's more a feature request, and makes sense as such.

[bukka]

This is actually addressed by this PR: #6860 that adds support for PKCS#11 - It's kind of a side effect of those changes. However the fact that it's using engines and there's no PKCS#11 provider is causing the PR is currently being delayed. If that doesn't change for some time (meaning if there's no provider for long time), we might consider extracting those changes.

[vjardin]

Things are delayed for years because the next feature is expected (aka "providers"). Even libp11 is not there yet OpenSC/libp11#432 (comment)

I do not want to rework these topics, I spent too much time, I moved to something else, but I feel it is the "Holy Grail". It would be more pragmatic to use engines since it is a well understood practice and then to add/extend with provider.

[cognitus]

any news? OpenSC/libp11#432 (comment) seem closed

[vjardinMisc]

I do not understand the status on libp11/openssl 3.0. Maybe @dengert can provide a proper summary.

Then, as I stated, my proposal was properly set using engines. Anyone is welcomed to update it using providers.