#667: Changeset 1627 - CONFIG_CRYPTO errors in Makefile
-------------------------------------+--------------------------------------
Reporter: anonymous | Owner: mentor
Type: defect | Status: new
Priority: minor | Milestone:
Component: madwifi: makefiles | Version:
Resolution: | Keywords:
Patch_attached: 0 |
-------------------------------------+--------------------------------------
Changes (by mentor):
* status: reopened => new
* owner: => mentor
Comment:
Sorry, this was my commit. It should be
{{{
@if [ -z "$(CONFIG_CRYPTO_AES)" ] || [ -z "$(CONFIG_CRYPTO_AES_586)" ];
then \
}}}
Which is what I commited from my local copy. The CCMP crypto module needs
the kernel AES support to initialise properly, even if there is hardware
support. As the module is always compiled and we alwayss depend on CRYPTO
support, I thought this was a reasonable hard dependency.
I'm working on fixing this stuff properly, but I'm confused by the key
setup process, which appears to be inconsistent (notably, hostapd has a
comment about this).
I'm going to try and recommit properly.
--
Ticket URL: <http://madwifi.org/ticket/667>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
