Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Network Connectivity: Add key management interface #2253

Closed
sfoster1 opened this issue Sep 12, 2018 · 0 comments
Closed

Network Connectivity: Add key management interface #2253

sfoster1 opened this issue Sep 12, 2018 · 0 comments
Labels
api Affects the `api` project feature Ticket is a feature request / PR introduces a feature medium
Milestone
Connectivity: Man...

Comments

@sfoster1
Copy link
Member

Some kinds of EAP-secured networks require key files for connecting. These can be private keys or certificates to validate the server against. They can be reasonably large so we should have a separate API interface for managing them.
@sfoster1 sfoster1 added feature Ticket is a feature request / PR introduces a feature api Affects the `api` project medium labels Sep 12, 2018
@sfoster1 sfoster1 added this to the Expand Network Connectivity milestone Sep 12, 2018
sfoster1 added a commit that referenced this issue Sep 12, 2018
@sfoster1
feat(api): Add wifi key upload endpoints
1f448b1 
/wifi/keys allows GET to list and POST to add a new keyfile (of arbitrary type and size). These are
hashed and stored in /data/user_storage/opentrons_data/network_keys in individual folders by sha256
hash of the contents. This hash is used as a URI for later deletion of the keys, or specification in
/wifi/configure eapol options that require key files.

Closes #2253
@sfoster1 sfoster1 mentioned this issue Sep 12, 2018
Merged
sfoster1 added a commit that referenced this issue Sep 13, 2018
@sfoster1
feat(api): Add wifi key upload endpoints
55467b4 
/wifi/keys allows GET to list and POST to add a new keyfile (of arbitrary type and size). These are
hashed and stored in /data/user_storage/opentrons_data/network_keys in individual folders by sha256
hash of the contents. This hash is used as a URI for later deletion of the keys, or specification in
/wifi/configure eapol options that require key files.

Closes #2253
sfoster1 added a commit that referenced this issue Sep 13, 2018
@sfoster1
feat(api): Add wifi key upload endpoints
5098567 
/wifi/keys allows GET to list and POST to add a new keyfile (of arbitrary type and size). These are
hashed and stored in /data/user_storage/opentrons_data/network_keys in individual folders by sha256
hash of the contents. This hash is used as a URI for later deletion of the keys, or specification in
/wifi/configure eapol options that require key files.

Closes #2253
sfoster1 added a commit that referenced this issue Sep 13, 2018
@sfoster1
feat(api): Add wifi key upload endpoints
02427b9 
/wifi/keys allows GET to list and POST to add a new keyfile (of arbitrary type and size). These are
hashed and stored in /data/user_storage/opentrons_data/network_keys in individual folders by sha256
hash of the contents. This hash is used as a URI for later deletion of the keys, or specification in
/wifi/configure eapol options that require key files.

Closes #2253
sfoster1 added a commit that referenced this issue Sep 13, 2018
@sfoster1
feat(api): Add wifi key upload endpoints
f51b91d 
/wifi/keys allows GET to list and POST to add a new keyfile (of arbitrary type and size). These are
hashed and stored in /data/user_storage/opentrons_data/network_keys in individual folders by sha256
hash of the contents. This hash is used as a URI for later deletion of the keys, or specification in
/wifi/configure eapol options that require key files.

Closes #2253
sfoster1 added a commit that referenced this issue Sep 13, 2018
@sfoster1
feat(api): Add wifi key upload endpoints
7e479de 
/wifi/keys allows GET to list and POST to add a new keyfile (of arbitrary type and size). These are
hashed and stored in /data/user_storage/opentrons_data/network_keys in individual folders by sha256
hash of the contents. This hash is used as a URI for later deletion of the keys, or specification in
/wifi/configure eapol options that require key files.

Closes #2253
sfoster1 added a commit that referenced this issue Sep 14, 2018
@sfoster1
Network connectivity: Add key management for EAP secured networks (#2254
250101c 
)

* feat(api): Add wifi key upload endpoints
* refactor(api): Add types to nmcli

/wifi/keys allows GET to list and POST to add a new keyfile (of arbitrary type and size). These are
hashed and stored in /data/user_storage/opentrons_data/network_keys in individual folders by sha256
hash of the contents. This hash is used as a URI for later deletion of the keys, or specification in
/wifi/configure eapol options that require key files.

 In addition, the nmcli and wifi endpoint modules are now fully typed.

Closes #2253
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api Affects the `api` project feature Ticket is a feature request / PR introduces a feature medium
Projects
None yet
Milestone
Connectivity: Manage Robot Connection
Development

No branches or pull requests
1 participant
@sfoster1