unit: Fix TTLS test

Single AVP should not be padded with zeros as padding is only
used to separate AVPs in a sequence.

RFC 5281 Section 10.2.  AVP Sequences

   Data encapsulated within the TLS record layer must consist entirely
   of a sequence of zero or more AVPs.  Each AVP must begin on a four-
   octet boundary relative to the first AVP in the sequence.  If an AVP
   is not a multiple of four octets, it must be padded with zeros to the
   next four-octet boundary.

   Note that the AVP Length does not include the padding.
This commit is contained in:
Tim Kourt 2018-10-10 15:09:14 -07:00 committed by Denis Kenzior
parent 8f8a214fbd
commit 949e672b75
1 changed files with 1 additions and 1 deletions

View File

@ -3123,7 +3123,7 @@ static const uint8_t eap_ttls_eap_md5_challenge_avp[] = {
static const uint8_t eap_ttls_eap_md5_response_avp[] = {
0x00, 0x00, 0x00, 0x4f, 0x40, 0x00, 0x00, 0x1e, 0x02, 0xbb, 0x00, 0x16,
0x04, 0x10, 0x10, 0xcc, 0x62, 0x4c, 0x98, 0x2b, 0x82, 0xbd, 0x13, 0x4a,
0x81, 0xcb, 0x70, 0x78, 0xcd, 0xc2, 0x00, 0x00
0x81, 0xcb, 0x70, 0x78, 0xcd, 0xc2,
};
struct eapol_8021x_eap_ttls_test_state {