Skip to content
This repository has been archived by the owner. It is now read-only.

Secure Beekeeper Web API (GSoC 2013) #89

johnnykv opened this issue Jun 9, 2013 · 1 comment


None yet
2 participants
Copy link

commented Jun 9, 2013

The web application should use SSL.

  • The keys and certificate should be created on first startup.
  • The certificate fingerprint should be stored in the clients configuration file.
  • Clients (feeders/hives) should refuse to transmit data if they detect a invalid certificate.

Submission of data from clients should be password protected

  • When creating a new client (hive/feeder) the corresponding credentials should also be created.
  • When deleting a new client (hive/feeder) the corresponding credentials should also be deleted.
  • Username would be client ID
  • Password would be generated, preferably a UUID.

@ghost ghost assigned czardoz Jun 15, 2013


This comment has been minimized.

Copy link
Member Author

commented Jul 14, 2013

closed with #107

@johnnykv johnnykv closed this Jul 14, 2013

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.