Hi Avinash,
Sorry for late reply, but I didn't follow the emails
on weekend.
You sent:
.
Key for HMAC_MD5 = server_auth_key
Input msg to MAC algorithm
{
seq no = 0x00 (8bytes)
Type = 0x23 (application data)
version = 0x0301
Length = 0x05
Data = 0x01 0x07 0x00 0x05 0x01
}
, September 21, 2004 12:11 AM
To: [EMAIL PROTECTED]
Subject: RE: TLS application data MAC
Hi Avinash,
Sorry for late reply, but I didn't follow the emails
on weekend.
You sent:
.
Key for HMAC_MD5 = server_auth_key
Input msg to MAC algorithm
{
seq no = 0x00 (8bytes)
Type
:38 AM
Subject: RE: TLS application data MAC
Hi Arvinash,
I think you have now exactly the same kind of problem
I had when I implemented the client: the first TLS app
data message the client was sending to the server
(after FINISHED messages) couldn't be decoded
correctly by the the server
Look at the Appendix -- Sample Code in http://www.ietf.org/rfc/rfc2104.txt
Avinash Agarwal wrote:
Hello all,
I'm trying to figure out how to generate the MAC for application data in TLS
v1.
The rfc (2246) says at ยง F.2 protecting application data
Outgoing data is protected with a MAC before
Hi Avinash,
The paragraph you mentioned is little bit vague,
better look at 6.2.3.1 from the same RFC; below is a
fragment from 6.2.3.1 paragraph:
..
The MAC is generated as:
HMAC_hash(MAC_write_secret, seq_num +
TLSCompressed.type +
TLSCompressed.version +
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of dragos liciu
Sent: Thursday, September 16, 2004 12:07 AM
To: [EMAIL PROTECTED]
Subject: Re: TLS application data MAC
Hi Avinash,
The paragraph you mentioned is little bit vague,
better look at 6.2.3.1 from the same RFC
