Layer2auth

[maxliu2001]

I've implemented layer 2 authentication in this pull request. The changes pertains to pscheduler-test-dot1x and pscheduler-tool-umichwpa. Packaging rules have been configured accordingly. Major changes have been made to accommodate secure handling of user credentials to execute the command. In order to execute the task, SSID, interface, and key-management options are required. They are required because this information is essential to generating the config file for wpa_supplicant.

In addition to taking in the most necessary parameters, an additional layer is added to check whether the username and password is supplied to the program. If username and password options are not supplied, a token option can be used to search for a corresponding line with matching identifier in the format of <identifier> <username> <password>. The program would then take in username and password in the program.

The program would initialize the wpa_supplicant interface if it doesn't already exist. After that, the program would rewrite the config file with new information regarding the login credentials. The program would then reconfigure the interface with the most up-to-date login credentials. However, the program can only auth to enterprise network (eg. eduroam) for now. In the future, key-management option may specify for an open network and config files can be generated separately.

After reconfiguration, the program would iteratively check for the wpa_state. The authentication process is only completed once wpa_state is completed. If any state fails in between, the program would timeout and returns an error. Otherwise, the program would print the information when the state is completed.