librerouterorg / soporteremoto Goto Github PK

Create and step for the first boot wizard in which we explain what to do with the pen drive holding the certificate for ephemeral keys, and a button to finish setup.

Implement an endpoint in the federated-server that return information about other soporteremoto servers announced over shared state from which this instance has been noticed about.
It will be used by soporteremoto fbw to show soporteremoto network data to the user as feedback of successful synchronization.

Implement a dummy express web-server with a Dockerfile, so we can start building the endpoints over it

Implement what ever is needed to allow user navigate to some easy to remember url and be redirected to the soporteremoto firstbootwizard.

Implement an initialization form in fbw. Asking for community name and soporteremoto api-key.
Submit to soporte-remoto /init_community_support endpoint.

Add a script to soporteremoto pi-gen project that installs tinc and configures librenet6 network with the current ip and public rsa key.
See more at http://docs.altermundi.net/LibreNet6

It may be the case that there is no connection to the shared-state network when the soporteremoto config is ready.
Implement some job that ensures that this configuration will be published in shared-state when the rpi get's into the network.

We need a bot/script to trigger a pull request to https://github.com/libremesh/librenet6-hostkeys that receives a rsa_public key and a host_name, community name, and creates a PR with them and a brief generic description.
We also need and enpoint in the web-server that receives this data.

Implement the necessary wizard steps to guide user in the process of copying the certificate for validating ephemeral keys into a pen drive.

Implement an endpoint in the federated-server that returns the list of pen drives that are currently plugged in into the rpi.

After initializing the soporteremoto service for the community an admin password is returned and it should be shown to the user.
Implement wizard step for it.

It may be the case that the rpi has no internet connection on the FBW process. Implement a job that ensures that the rpi will hit the registering endpoint of the soporteremoto tier when possible.
The body of the request should contain:
community name,
rsa public key (tinc credential),
and host_name

Note: Please set the host_name to:
soporteremoto + _ + community_name + _ + device_name

It's needed that an instance of soporteremoto server gets started when the os start.

Implement the needed functionality to open an access point in order to allow users to enter the support dashboard from a web browser.

The package should implement:

• Installation of public certificate on pendrive plug.
• Acceptance or rejection of ephemeral ssh keys announced on shared-state.
• Contemplate persistence of soporteremoto configuration. We don't want to lose this configuration if the rpi gets broken. Maybe distributing and persisting the config on each node will help.

Implement and endpoint that copies the certificate for ephemeral keys into the previously plugged pen drive

Implement an endpoint in the federated server that receives data from initialization form, being community data and api key, and configure for the first time a soporteremoto service on the community.

• It should configure the api key.
• It should configure an ssb unique id.
• It should generate a certificate for ephemeral keys.
• It should should generate credentials for tinc/librenet6 (Not mandatory for first iteration).
• It should generate an admin password for the soporteremoto services in the community.
• It should publish all of the above encrypted with the admin password.
• It should return the generated admin password.

It should request for support to the tier server for every pending issues,
When being able to get a responde from the tier server, it should mark them as waiting for support and publish the public key on shared stated signed with the rpi certificate