Ideas for https certificate for dpanel

[DivineGod]

A few features in dpanel would benefit from being served in a secure web context.

Besides enabling web features needing a secure context, the ability to make sure the connection between the users computer and the dogebox is secure will prevent issues if the local network isn't fully secure, especially during setup when various sensitive information is passed between back-end and front-end.

To support this, we would need to be able to serve the front-end over https with a valid certificate for a predictable hostname.

We are currently using mDNS to resolve dogebox.local to the IP address of the dogebox on the local network. We would need to come up with a way to serve a certificate that is able to verify this domain. This might involve a self-signed certificate that the user would then need to trust manually in the browser. On every hostname change the certificate would be re-generated with the new details and be re-trusted.

Another way could be to deploy a reverse dns service that would allow us to have wild-card domain certificates and a root CA we control to do the certificates with. This would require the use of more unique hostname mappings to the reverse dns tool so we don't have overlaps.

I am not sure if those two approaches are well thought out and there might also be other, better options. I just had these ideas in my head and needed to get them out in writing