In message <6126f3d3-91a0-02b3-20e8-ab26dbf8b...@gmail.com> on Sun, 2 Sep 2018
06:48:09 -0500, Jim Dutton said:
> It appears that the (PHP) openssl_encrypt function will accept a string of
> random bytes as the encryption key in place of a generated private key. It
> works without any errors or
What's Windows? Why doesn't it work like my Mac?
(I wasnt serious but thanks for being a sport)
On Sep 2, 2018 5:02 PM, "Salz, Rich" wrote:
- Gotcha. But why doesn't it work on Mac?
The CAPI engine uses Microsoft libraries that are part of windows.
--
openssl-users mailing list
To
On Sep 2, 2018, at 20:02, Salz, Rich via openssl-users
wrote:
> Gotcha. But why doesn't it work on Mac?
>
> The CAPI engine uses Microsoft libraries that are part of windows.
Gotcha. In that case why does it get built on Mac? I.e., why doesn’t the build
process exclude it automatically?
* Gotcha. But why doesn't it work on Mac?
The CAPI engine uses Microsoft libraries that are part of windows.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
I have been using the examples given in the PHP-openssl_encrypt documentation
for AEAD with PHP 7 or a suitable emulation of that using HMAC with PHP 5. Being
very familiar with security issues and functionality I automatically started
using an elliptical curve private key as the "key" after
> On Sep 2, 2018, at 6:51 PM, Jim Dutton wrote:
>
> It is interesting to note that the openssl_private_encrypt function appears
> to require a "true" private key and either expects or defaults to RSA.
Not surprising, given the name and brief documentation.
> In both cases neither
OK - thanks for the feedback. It is interesting to note that the
openssl_private_encrypt function appears to require a "true" private key and
either expects or defaults to RSA. In both cases neither PHP-OpenSSL nor
OpenSSL documentation make these distinctions between the two "encrypt"
Gotcha. But why doesn't it work on Mac?
On Sun, Sep 2, 2018, 2:22 PM Salz, Rich via openssl-users <
openssl-users@openssl.org> wrote:
> *>*The capi engine is still broken, however
>
>
>
> That is windows-only, using the MSFT CryptoAPI.
> --
> openssl-users mailing list
> To unsubscribe:
> On Sep 2, 2018, at 7:48 AM, Jim Dutton wrote:
>
> It appears that the (PHP) openssl_encrypt function will accept a string of
> random bytes as the encryption key in place of a generated private key.
This is an interface to data encryption with the OpenSSL *symmetric*
encryption algorithms,
>This begs the question: what does openssl_encrypt actually do with just a
> string
of random bytes passed as the "key". I can't find anything in the OpenSSL or
PHP/openssl source code that clearly identifies any particular action
There is no such name (git grep -I openssl_encrypt)
>The capi engine is still broken, however
That is windows-only, using the MSFT CryptoAPI.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
It appears that the (PHP) openssl_encrypt function will accept a string of
random bytes as the encryption key in place of a generated private key. It
works without any errors or warnings. So does the openssl_decrypt function.
This begs the question: what does openssl_encrypt actually do with just
Never mind. My binding entry point was misbehaving.
The capi engine is still broken, however.
On Sun, Sep 2, 2018 at 1:51 AM Thomás Inskip wrote:
> Hi.
>
> I am trying to develop an engine for OpenSSL. To this effect I have built
> OpenSSL 1.1.0i for Darwin. However, when I try to load any
Hi.
I am trying to develop an engine for OpenSSL. To this effect I have built
OpenSSL 1.1.0i for Darwin. However, when I try to load any engine,
including capi, which is installed as part of OpenSSL, I get the following:
*openssl* engine -t -c capi
140735831704448:error:260B606D:engine
14 matches
Mail list logo
