I do not know how to change "add_before" in Configure.
So I tested changing Configurations/10-main.conf as follows, not to use
"add_before",
and found make & make check passes. (need to Apply fix #4314.)
% ../openssl-1.1.0-pre3/Configure --unified solaris64-x86_64-gcc threads shared
no-ssl3
%
Hello,
For implementing the TLS Cached Info extension [1] that sends certificate
hashes in place of the full certificate (if unchanged from a previous
handshake), we need a way to check and modify the cerificate message being
sent (for server) and received (for client). The callbacks could be,
Hi Andy,
The partial-block tail code in chacha-armv4.pl also seems to have problems.
My colleague Steven and I made an attempt to debug it, but we're not
familiar enough with ARM to fix it.
>From playing with it in a debugger, it doesn't look like @t[3] contains the
length. We suspect something
Was there any movement on this issue?
--
Felipe Sere
Sent with Airmail
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4290
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Hi,
I have encrypted a free text in C++ using a EVP calls with CFB mode and 32
bytes of IV (Hex String).
Then i am passing this cipher text to my another end which is using a
python(PyCrypto library) code to decrypt a cipher text using same Key and
IV.
But i am getting error "IV must be of 16
+1.
With one exception: engine_pkcs11 has been subsumed (and merged into) libp11.
I've tested it with a few different PIV tokens (RSA and ECC), and it was great.
Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network.
Original Message
From: Nikos Mavrogiannopoulos
On Fri, 2016-02-19 at 13:12 +, Matt Caswell wrote:
> As far as I know there are some customers using the Chil engine
> > with
> > RHEL (openssl-1.0.1).
>
> How do you feel about the engine being spun out into a separate repo?
> That of course assumes that a volunteer can be found to
On Fri Feb 19 13:58:34 2016, i...@ecsystems.nl wrote:
> openssl 1.0.2f static build with nginx 1.9.12 (development version)
>
> about
>
https://github.com/openssl/openssl/commit/64193c8218540499984cd63cda41f3cd491f3f59
>
> This may solve the initial issue but creates a new one:
> SSL_shutdown()
"Salz, Rich" skrev: (19 februari 2016 15:07:42 CET)
>
>> In both cases I would like to remove these engines from 1.1.0. I'd
>like to hear
>> from the community if there is any active use of these. One option if
>there is
>> found to be some small scale use is to spin out the
> In both cases I would like to remove these engines from 1.1.0. I'd like to
> hear
> from the community if there is any active use of these. One option if there is
> found to be some small scale use is to spin out the engine into a separately
> managed repo (as has happened recently with the
openssl 1.0.2f static build with nginx 1.9.12 (development version)
about
https://github.com/openssl/openssl/commit/64193c8218540499984cd63cda41f3cd491f3f59
This may solve the initial issue but creates a new one:
SSL_shutdown() failed (SSL: error:140E0197:SSL routines:SSL_shutdown:shutdown
Matt Caswell skrev: (19 februari 2016 14:12:28 CET)
>
>
>On 19/02/16 13:03, Tomas Mraz wrote:
>> On Pá, 2016-02-19 at 11:31 +, Matt Caswell wrote:
>>
>>
>>> So it seems that for chil there may possibly be some rare use (but
>>> even
>>> the most recent evidence is 4
On 19/02/16 13:11, Jaroslav Imrich wrote:
> Hello Matt,
>
> If I don't hear from anyone I will remove these.
>
>
> I can confirm that CHIL engine is actively used with OpenSSL 1.0.* by
> the owners of nCipher/THALES nShield HSMs.
>
> I have notified vendor support about this thread.
>
Hello Matt,
If I don't hear from anyone I will remove these.
>
I can confirm that CHIL engine is actively used with OpenSSL 1.0.* by the
owners of nCipher/THALES nShield HSMs.
I have notified vendor support about this thread.
Regards, Jaroslav
--
openssl-dev mailing list
To unsubscribe:
On Pá, 2016-02-19 at 11:31 +, Matt Caswell wrote:
> So it seems that for chil there may possibly be some rare use (but
> even
> the most recent evidence is 4 years old). However the OpenSSL dev
> team
> do not have access to this hardware to maintain the engine and (as
> noted
> above) this
Hi all
The ubsec and chil engines are currently disabled in 1.1.0 and do not build.
As far as ubsec is concerned I understand that this is an engine for
broadcom cards. There has been very little activity with this engine
since it was first introduced. Google brings up some very old historic
Looks like the last suggested patch against this ticket was applied. No further
activity since 2008, so assuming this is resolved. Closing.
Matt
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=1736
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
17 matches
Mail list logo