Gayathri Sundar wrote:
> Thanks jimmy..I realised that much, the update is happening from ssl3_mac
> defined in s3_enc.c, some "s2n" of the length is called, followed by a
> digestupdate(md, 2)..in case of READ, md is an empty array..why do we copy
> the ssl record length into a temp var "p" and th
Thanks jimmy..I realised that much, the update is happening from ssl3_mac
defined in s3_enc.c, some "s2n" of the length is called, followed by a
digestupdate(md, 2)..in case of READ, md is an empty array..why do we copy
the ssl record length into a temp var "p" and then do a s2n followed by an
dige
Gayathri Sundar wrote:
> Can someone give me inputs on the function ssl3_mac, especially where it
> is called s->method->ssl3_enc->mac(s,&(p[wr->length]),1);
>
> I need to know what p[wr->length] is pointing to and why we do a digest
> update of 2 bytes from that.
>
> The code is taken from s3_pk
Can someone give me inputs on the function ssl3_mac, especially where it
is called s->method->ssl3_enc->mac(s,&(p[wr->length]),1);
I need to know what p[wr->length] is pointing to and why we do a digest
update of 2 bytes from that.
The code is taken from s3_pkt.c function ssl3_write_bytes.
Thank
