update auth mechanisms
use_auth allows the newer auth mechanisms to be optional changes and fixes to support TODO: need to get a bot that would connect on XMPP or get sniffed traffic to see the login details
This commit is contained in:
parent
d316862120
commit
0a5d93b099
6 changed files with 306 additions and 166 deletions
|
|
@ -149,9 +149,13 @@ So far two protocols have been identified that various models of EcoVacs robots
|
|||
----
|
||||
### Login/Authentication/RestAPI
|
||||
|
||||
***Bumper*** provides a fully simulated central server that handles login/authentication for the app/clients. At this time no authentication layer is implemented and you can use any e-mail/password when logging in. Future versions should add additional options here for security.
|
||||
***Bumper*** provides a fully simulated central server that handles login/authentication for the app/clients.
|
||||
|
||||
This means however, that once a robot has been configured to access your WiFi it never needs to communicate with EcoVac's servers again.
|
||||
The EcoVacs app encrypts the username/password with the public key of EcoVacs when authenticating. Since we don't have the private key to decrypt, there is no way to provide true security and authentication.
|
||||
|
||||
Future versions may add additional options here for security.
|
||||
|
||||
Bots have no authentication and once a robot has been configured to access your WiFi it never needs to communicate with EcoVac's servers again.
|
||||
|
||||
----
|
||||
### XMPP
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue