aboutsummaryrefslogtreecommitdiffstats
path: root/src/eap_peer/eap_tnc.c
Commit message (Collapse)AuthorAgeFilesLines
* EAP peer: Simplify EAP method registration callJouni Malinen2016-01-131-5/+1
| | | | | | | | | Free the allocated structure in error cases to remove need for each EAP method to handle the error cases separately. Each registration function can simply do "return eap_peer_method_register(eap);" in the end of the function. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
* EAP-TNC peer: Remove dead code related to fragmentationJouni Malinen2015-12-241-5/+0
| | | | | | | | | The data->state == WAIT_FRAG_ACK case is already handling all cases where data->out_buf could be non-NULL, so this additional check after the WAIT_FRAG_ACK steps cannot be reached. Remove the duplicated dead code. Signed-off-by: Jouni Malinen <j@w1.fi>
* EAP-TNC peer: Allow fragment_size to be configuredJouni Malinen2015-12-241-1/+6
| | | | | | | Previously, a fixed 1300 fragment_size was hardcoded. Now the EAP profile parameter fragment_size can be used to override this. Signed-off-by: Jouni Malinen <j@w1.fi>
* EAP-TNC: Limit maximum message buffer to 75000 bytes (CID 62873)Jouni Malinen2014-06-131-1/+2
| | | | | | | | | | Since there is a limit on the EAP exchange due to maximum number of roundtrips, there is no point in allowing excessively large buffers to be allocated based on what the peer device claims the total message to be. Instead, reject the message if it would not be possible to receive it in full anyway. Signed-off-by: Jouni Malinen <j@w1.fi>
* Remove the GPL notification from files contributed by Jouni MalinenJouni Malinen2012-02-111-8/+2
| | | | | | | Remove the GPL notification text from the files that were initially contributed by myself. Signed-hostap: Jouni Malinen <j@w1.fi>
* Remove unnecessary include file inclusionJouni Malinen2011-11-131-1/+0
| | | | Signed-hostap: Jouni Malinen <j@w1.fi>
* EAP-TNC: Add Flags field into fragment acknowledgementJouni Malinen2010-02-141-1/+2
| | | | | | | | | | | TNC IF-T is somewhat unclear on this are, but draft-hanna-nea-pt-eap-00.txt, which is supposed to define the same protocol, is clearer on the Flags field being included. This change breaks interoperability with the old implementation if EAP-TNC fragmentation is used. The old version would not accept the acknowledgement message with the added Flags octet while the new version accepts messagss with with both options.
* EAP-TNC: Accept fragment ack frame with Flags fieldJouni Malinen2010-02-131-1/+1
| | | | | | | | | | TNC IF-T specification is unclear on the exact contents of the fragment acknowledgement frame. An interoperability issue with the tncs@fhh implementation was reported by Arne Welzel <arne.welzel@stud.fh-hannover.de> due to the different interpretations of the specification. Relax EAP-TNC server/peer validation rules to accept fragmentation acknowledgement frames to include the Flags field to avoid this issue.
* TNC: Fix a stray pointer that could cause segfault on error pathMasashi Honma2009-03-161-3/+8
| | | | | | | On "eap_tnc_process" function error case, data->in_buf keeps reference to a local scope variable. For example this will cause segmentation fault in "eap_tnc_deinit" function "wpabuf_free(data->in_buf)" statement.
* Renamed MSG to PROC_MSG to avoid conflicts with MinGW winuser.hJouni Malinen2008-08-101-5/+5
|
* Fixed EAP-TNC not to include extra EAP header and TNC flagsJouni Malinen2008-07-161-7/+5
| | | | | | | | The change to support fragmentation added extra function to generate the EAP header, but forgot to remove the original code and ended up getting two EAP headers and TNC flags field in the generated message. These header fields need to be added only in the function that builds the final message (and if necessary, fragments the data).
* Added fragmentation support for EAP-TNCJouni Malinen2008-05-261-14/+224
|
* Re-initialize hostapd/wpa_supplicant git repository based on 0.6.3 releaseJouni Malinen2008-02-281-0/+220