On 26/09/2019 10:26, ratheesh kannoth wrote:
>> I assume you are using OpenSSL 1.0.2?
>>
>> s->s2 has nothing to do with TLSv1.2. That's for SSLv2 and has been removed
>> from
>> later versions. In 1.0.2 you need to be looking at s->s3->write_sequence and
>> s->s3->write_sequence. It's changed
> I assume you are using OpenSSL 1.0.2?
>
> s->s2 has nothing to do with TLSv1.2. That's for SSLv2 and has been removed
> from
> later versions. In 1.0.2 you need to be looking at s->s3->write_sequence and
> s->s3->write_sequence. It's changed location in later releases.
>
> Matt
>
Sorry for conf
On 26/09/2019 06:42, ratheesh kannoth wrote:
> Hi list,
>
> i am trying to understand write sequence number and read sequence
> number. Setup is simple client server with tls v1.2.
>
> when i made write sequence number to 0 (ssl/t1_enc.c -->
> s->s2->write_sequence to 0). i commented out all
On 25/09/2019 19:32, Thomas Uban via openssl-users wrote:
> I am using the openssl 3.0.0 library in an embedded environment and added a
> unit
> test for RSA based on test/rsa_mp_test.c:test_rsa_mp().
>
> When the test is run, I see:
>
> 1. crypto/rsa/rsa_pk1.c:RSA_padding_check_PKCS1_ty
On 25/09/2019 18:41, Ian Sinclair wrote:
> Thanks for the detailed investigation. I don't know if we have a BIO callback
> or
> modified any BIO code. I'll have to dig into our version of Asterisk to see
> if I
> can tell.
>
> The version confusion is mine. We really are running 1.0.1e 58 fro
On 25/09/2019 18:02, Mark Hack wrote:
> This was on 1.0.2 and I just checked 1.1.1, and for libssl I still only
> see the call for libcrypto. I can recompile and confirm later in the
> day to be 100% certain.
The call to OPENSSL_cpuid_setup() in 1.1.1 is inside ossl_init_base in
libcrypto. That
