Is your feature request related to a problem? Please describe
The current way (usage of password file) for connecting remote clients is clunky and not user friendly.
Describe the solution you'd like
A pairing API.
This API would be available under pair.
Upon receiving the server would keep the connection alive and keep track of the pairing request, similar to how device-streams work.
A pairing request must be approved within N seconds.
A new command will be added to list and approve pairing requests.
The approve and list commands talk to another new endpoint pairings with paramters list or approve.
These APIs are only callable from localhost.
At a later stage a gui for this can be figured out (See also #6 (comment))
Upon approval a random password is generated, stored in an sqlite.db and sent ro the client.
The pairing connection closes.
Is your feature request related to a problem? Please describe
The current way (usage of password file) for connecting remote clients is clunky and not user friendly.
Describe the solution you'd like
A pairing API.
This API would be available under
pair.Upon receiving the server would keep the connection alive and keep track of the pairing request, similar to how device-streams work.
A pairing request must be approved within N seconds.
A new command will be added to list and approve pairing requests.
The approve and list commands talk to another new endpoint
pairingswith paramterslistorapprove.These APIs are only callable from localhost.
At a later stage a gui for this can be figured out (See also #6 (comment))
Upon approval a random password is generated, stored in an sqlite.db and sent ro the client.
The pairing connection closes.