Re: OpenSSL compilation errors in Windows

[Nagalakshmi V J <nagalakshmi.j@xxxxxxxxxx>]

Hi All,

Appreciate the response for the below query. Anyone faced the same issue?

Thanks & Regards,

Nagalakshmi V J

---

From: Nagalakshmi V J <nagalakshmi.j@xxxxxxxxxx>
Sent: 24 October 2019 03:29
To: Nagalakshmi V J <nagalakshmi.j@xxxxxxxxxx>; Matt Caswell <matt@xxxxxxxxxxx>; openssl-users@xxxxxxxxxxx <openssl-users@xxxxxxxxxxx>
Subject: Re: OpenSSL compilation errors in Windows

 

Hi Matt,

Kindly provide your inputs for the below mail.

Thanks & Regards,
Nagalakshmi V J

---

From: Nagalakshmi V J <nagalakshmi.j@xxxxxxxxxx>
Sent: 22 October 2019 10:41:40
To: Matt Caswell <matt@xxxxxxxxxxx>; openssl-users@xxxxxxxxxxx <openssl-users@xxxxxxxxxxx>
Cc: Nagalakshmi V J <nagalakshmi.j@xxxxxxxxxx>
Subject: RE: OpenSSL compilation errors in Windows

 

Hi Matt,

 

Could you please help to get any clue on the ACCESSOR APIs of the following.

 

I tried searching APIs. Not getting exact matches. Referred the below links.

 

https://www.openssl.org/docs/man1.1.1/man3/SSL_set_info_callback.html

https://www.openssl.org/docs/man1.1.1/man3/EVP_md5.html

 

Getting similar error for the below code.

 

tls1_PRF(s->ctx->md5,s->ctx->sha1,buf,(int)(p-buf),

         pGenerator->master_secret,sizeof(pGenerator->master_secret),

         km,tmp,num);

 

Struct ssl_ctx_st {

…

const EVP_MD *md5;          /* For SSLv3/TLSv1 'ssl3-md5' */

const EVP_MD *sha1;         /* For SSLv3/TLSv1 'ssl3->sha1' */

…

}

 

struct evp_md_st {

    int type;

    int pkey_type;

    int md_size;

    unsigned long flags;

    int (*init) (EVP_MD_CTX *ctx);

    int (*update) (EVP_MD_CTX *ctx, const void *data, size_t count);

    int (*final) (EVP_MD_CTX *ctx, unsigned char *md);

    int (*copy) (EVP_MD_CTX *to, const EVP_MD_CTX *from);

    int (*cleanup) (EVP_MD_CTX *ctx);

    int block_size;

    int ctx_size;               /* how big does the ctx->md_data need to be */

    /* control function */

    int (*md_ctrl) (EVP_MD_CTX *ctx, int cmd, int p1, void *p2);

} /* EVP_MD */ ;

 

 

Thanks and regards,

Nagalakshmi

 

From: Nagalakshmi V J <nagalakshmi.j@xxxxxxxxxx>
Sent: Tuesday, October 22, 2019 9:39 AM
To: Matt Caswell <matt@xxxxxxxxxxx>; Nagalakshmi V J <nagalakshmi.j@xxxxxxxxxx>; openssl-users@xxxxxxxxxxx
Subject: Re: OpenSSL compilation errors in Windows

 

Hi Matt,

Yes. Exactly we followed the same and able to resolve errors. Thank you so much for the support and guidance. I'll get back if any further errors.

Thanks & Regards,
Nagalakshmi V J

---

From: Matt Caswell <matt@xxxxxxxxxxx>
Sent: 21 October 2019 21:26:32
To: Nagalakshmi V J <nagalakshmi.j@xxxxxxxxxx>; openssl-users@xxxxxxxxxxx <openssl-users@xxxxxxxxxxx>
Subject: Re: OpenSSL compilation errors in Windows

 

** This mail has been sent from an external source **


On 20/10/2019 08:43, Nagalakshmi V J wrote:
> Hi Matt,
>
> This link is having few APIS. But for getting master_key_length, I don't
> find any API. Not sure if we need to use getMasterKey API for that.

You can use SSL_SESSION_get_master_key() for this.

Note this comment in the RETURN VALUES section:

"For the other functions, if outlen is greater than 0 then these
functions return the number of bytes actually copied, which will be less
than or equal to outlen. If outlen is 0 then these functions return the
maximum number of bytes they would copy -- that is, the length of the
underlying field."

So to discover the master_key_length call the function with outlen to
zero. You can then allocate an appropriate sized buffer and call the
function again in order to get the actual master key.

Matt


>
> I will try to use these APIs and get back.
>
> Thanks & Regards,
> Nagalakshmi V J
> ------------------------------------------------------------------------
> *From:* Matt Caswell <matt@xxxxxxxxxxx>
> *Sent:* 18 October 2019 14:48:33
> *To:* Nagalakshmi V J <nagalakshmi.j@xxxxxxxxxx>;
> openssl-users@xxxxxxxxxxx <openssl-users@xxxxxxxxxxx>
> *Subject:* Re: OpenSSL compilation errors in Windows
>
> ** This mail has been sent from an external source **
>
>
> On 18/10/2019 11:49, Nagalakshmi V J wrote:
>> Now the issue is SSL_session structure is also having accessor APIs
>> which I am not aware of. So I need to get the APIs for accessing the
>> master_key_length,etc.. given in the above code. Those are not listed
>> in the openssl link referred.
>
> On this page look a the various functions beginning with "SSL_SESSION_"
> in the name:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.openssl.org_docs_man1.1.1_man3_&d=DwICaQ&c=cxWN2QSDopt5SklNfbjIjg&r=zbjUR56YPF3jaTRTjX4KZlHM9-LmYAuR5atSqEGOnpA&m=MZhYFrTAuuHOqAirPiGbT1CY6HDdH2U_CWYq12626Ts&s=gE0JHTVoToRHQRu5h2amvKa5WzyXsortlw0IoQd3VG4&e=
>
> From the code sample you gave you are probably mostly interested in the
> functions on this page:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.openssl.org_docs_man1.1.1_man3_SSL-5FSESSION-5Fget-5Fmaster-5Fkey.html&d=DwICaQ&c=cxWN2QSDopt5SklNfbjIjg&r=zbjUR56YPF3jaTRTjX4KZlHM9-LmYAuR5atSqEGOnpA&m=MZhYFrTAuuHOqAirPiGbT1CY6HDdH2U_CWYq12626Ts&s=XTuEzS7qyBvIHc_qWJYoh3JVC4zPCzvUzNPStW_SvLI&e=
>
> Matt
>
> =====================================================
> Please refer to https://northamerica.altran.com/email-disclaimer
> for important disclosures regarding this electronic communication.
> =====================================================

=====================================================
Please refer to https://northamerica.altran.com/email-disclaimer
for important disclosures regarding this electronic communication.
=====================================================

=====================================================
Please refer to https://northamerica.altran.com/email-disclaimer
for important disclosures regarding this electronic communication.
=====================================================

=====================================================
Please refer to https://northamerica.altran.com/email-disclaimer
for important disclosures regarding this electronic communication.
=====================================================

=====================================================
Please refer to https://northamerica.altran.com/email-disclaimer
for important disclosures regarding this electronic communication.
=====================================================