Windows 10: Adding Self Signed Cert to Chrome ?

Hi

I run a local linux web server and it has a self signed certificate on it.
Every few days when I access it I get:

Your connection is not private Attackers might be trying to steal your information from 192.168.0.100 (for example, passwords, messages, or credit cards). Learn moreNET::ERR_CERT_AUTHORITY_INVALID

If I proceed, then it's fine for a few days.
Access is only available to this server from internal devices, it's not Internet facing.

Is there any way I can add that cert to Chrome so I no longer get these warnings ?
If so... How ?

Thanks

:)

 

How to add self-signed certificate to my PC?

My PC is Windows 10 Pro x64 and I have Edge and Chrome browsers installed.

I installed my firewall's Certificate Authority into the windows certificate store by going to MMC, adding Certificates, and adding it to the Trusted Root CA. I now see my firewall root CA as (firewallCA).

Now I created a CNAME in my DNS to access my firewall as fw.example.com which only resolves internally. I then generated on my firewall a self-signed certificate. Once created, I downloaded the certificate and also added it to the MMC->Certificates.

I can now open IE or Edge and go to https://fw.example.com and not get a certificate error. However, if I use Chrome, I still get the error. I went to the Chrome advanced settings and see the firewallCA listed, but not the self-signed cert. I guess I have to add it manually, but I want it to apply to any user on this PC. How can I add the self-signed cert to Chrome for all users?

 

Cert is self-signed, not expired.

The certificate is not expired. In fact, it was issued October 2, 2015 and expires September 29, 2025. The problem is that it is self signed, issued to (and by) GreenWave Systems.

Apparently GreenWave is big enough to supply routers nationwide for Verizon, but they can't afford to pay a legitimate CA for a real cert.

Maybe Verizon should charge us more for their service. They could pass a little of that money to GreenWave so they could protect us like a real business does.

 

Creating a self-signed cert and trusting it for windows RDP (no domain)

I can use windows RDP to remote control my home PC (through a VPN), but I always get this warning:





Do I need to manually generate a self signed cert and install it?

Or has this already happened and can I trust the one that it is already providing?

Does "Don't ask me again for connections to this computer" do this?, or does this just check the name and bypass checking the certificate at all?

I still want to use the self signed certificate for verification. I just want my laptop to trust the self-signed cert.

I'm on windows 10.