Planned software infrastructure

[aloisklink]

On the BRSKI server, we'll have:

• One Hostapd instance running with no password/PSK, that hosts the BRSKI server code
• BRSKI Pledge-Registrar from https://github.com/nqminds/brski
• BRSKI Registrar-MASA from https://github.com/nqminds/brski
  • TODO: could put this on a fourth device, if we have time
• One Hostapd instance with a PSK, that can only be logged into after going through the BRSKI protocol
• One NIST BRSKI demo webapp, containing buttons/info about resetting the BRSKI clients
• We DO NOT plan on using any edgesec code, since we're under a pretty tight deadline, and fixing/merging PR https://github.com/nqminds/edgesec/pull/358 will take far too long.

Each BRSKI client will:

1. Connect to the open WiFi AP
2. Run the BRSKI code in https://github.com/nqminds/brski
3. After getting the certificate from the BRSKI process, we'll calculate the hash of the certificate, and use that as the PSK to connect to the secured Wifi AP

Discussed with @mereacre on call on 2023-06-02