IIRC, the initial cert for MiaB is a self-signed cert and the LE or other certs are added after logging into the dashboard.
The question is about verifying the self-signed cert using the fingerprint provided in the setup process.
The fingerprint is the SHA-256 hash and the hash reported in the Windows browsers thus far have have all been the (correct) SHA-1 hash while the indicated preference is to verify using the SHA-256 hash.
I don’t have a Windows machine to figure out how to navigate to an SHA-256 hash.
Is it possible that you hit the blue provision button and just didn’t realize it? Because that is really about the only plausible scenario. In either case, you have a valid certificate currently installed rather than the self-signed certificate, so I would say that you are good to go.
Regarding your initial query - I hadn’t read the thread closely enough as @openletter so kindly pointed out.
You raise a valid point that I do not know the answer to. I can quite conceivably see MiaB running the script during the nightly maintenance and replacing the self-signed cert … though I have never left it overnight to see personally.
No, it’s fine. Not to worry. I am going to scratch this install and start over as i feel uneasy about it. Before i even log into any fresh install, i always check the fingerprint. This case was no exception.
Based on the two timestamps the LE looks like when i logged in the first time to investigate what was going wrong.
Yes I finally was able to manage doing this by looking at the brave browser screenshot listed in this thread , as it turns out the fingerprint was identical to the one cited remotely . Edit: Sorry for the lack of clarification, the screenshot listed in this thread that shows the brave bowser fingerprint was created by me
Prior to this thread were you aware that was the correct SHA-1 hash for the SHA-256 hash? Even though the numbers matched, you would also need to know the different algorithm’s correct value.
The hash you provided in the initial post in the text document was SHA-256 and I had assumed that was what MiaB printed for you at the end of the install. The GRC hash and other in-browser hashes in your screenshots were all SHA-1.
It is configuring standard mail server tools and other useful administrative tools for you and then installing a dashboard admin interface that is custom to the project. I’m guessing that setup process would normally take an admin between 4 and 20 hours, depending on the experience of the admin.
If any terms I or others use you are not familiar with, please feel free to either post or send a message. Generally speaking, anyone who takes the time to help someone out in a forum post would be willing to do the same in a PM.
