Configuration file committed to public source control, what to change?

Started by Inventor4life, Today at 10:12:45 AM

Previous topic - Next topic
Hello!

I committed my configuration XML file to a github repo that will eventually be made public. Wireguard was the only thing configured. I had the foresight to store the wireguard instance private key elsewhere, but I saw that the encrypted root password and certificate private key were committed. Is there anything I should do in addition to regenerating the certificate and changing the root password? Wireguard peer public keys and endpoint names/addresses were committed, but I think those are fine for the most part?

Thanks