Bug 659038 - EAP_TNC is not enabled by default
EAP_TNC is not enabled by default
Product: Fedora
Classification: Fedora
Component: wpa_supplicant (Show other bugs)
Unspecified Unspecified
high Severity medium
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-12-01 15:01 EST by Avesh Agarwal
Modified: 2011-01-11 10:32 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-01-11 10:32:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Avesh Agarwal 2010-12-01 15:01:57 EST
Description of problem:
EAP_TNC support is not enabled by default in wpa_supplicant. I enabled EAP_TNC by adding CONFIG_EAP_TNC=y in wpa_supplicant.config .  

I have prepared a local TNC (trsuted network connect) testbed that requires support of EAP_TNC over 802.1X. This testbed is built using freeradius-server, 802.1x authenticator, and TNC implementation available from http://trust.inform.fh-hannover.de/joomla/index.php/projects/tncfhh . Using this testbed, I have tested that the support of EAP_TNC in wpa_supplicant works.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:
EAP_TNC is not enabled by default

Expected results:
EAP_TNC should be enabled by default

Additional info:
Comment 1 Avesh Agarwal 2010-12-01 15:04:36 EST
The latest upstream wpa_supplicant version is wpa_supplicant-0.7.3 is whereas fedora has 0.6.8. wondering what is the plan to bring this latest upstream version to the rawhide?
Comment 2 Steve Grubb 2010-12-01 16:05:19 EST
Specifically, we are trying to get TNC working and need to work closer to upstream so that feedback is more relevant. Thanks.
Comment 3 Dan Williams 2011-01-11 10:32:20 EST
Built for rawhide:


Note You need to log in before you can comment on or make changes to this bug.