New answers tagged

2

It's talking about the certificate of the key server, not the certificate you're trying to upload. (GnuPG itself almost never calls PGP keys "certificates", it usually reserves that name specifically just for the key signature alone (aka certification), not for the whole keyblock.) Although keys.openpgp.org accepts cleartext HKP requests (which are ...


0

This seems like it will probably make Git work, but you've missed probably the biggest security consideration of all: you're running an OS that has not received any security updates in over seven years. Your OS definitely has known security vulnerabilities, some of which may be remotely exploitable, and it is unlikely that the TLS library you're using is ...


0

You can list the private keys in your Firefox key store by using the certutil from Mozilla's NSS tools: certutil -K -d PATH_TO_YOUR_PROFILE_DIRECTORY These can be matched aginst the list of certificates from your certificate store: certutil -L -d PATH_TO_YOUR_PROFILE_DIRECTORY Thus you can find out whether you have a corresponding certificate and key by ...


1

To add just another viewpoint to a lot of very useful/interesting answers: How long will it be till every week is a different cert? Or why not every request? Then we just rely on their "trusted" authority. As soon as you trust a certificate authority, you trust all of its (non revoked) certificates. It is not very important which one specifically ...


0

you may remove EV certificate from .sys and only add Microsoft certificate. that's what WDK team suggested to me.


0

I used dseo13b.exe . Use it at your own risk, it solved question, but there is something special with it...


2

I run one of those setups that will seem to randomly change their SSL certificates for any reason. We run a cluster of servers that has one central point per environment to offload SSL, using a single certificate per environment. What that means is, for instance, that the certificate is responsible for: example1.com example2.com sub.example2.com Now, let's ...


51

But what's going on with superuser.com? They changed their cert 70 days early only to give them an extra 20 days? Why do that? It could be that you're looking at two different servers (load-balanced) which renew their certificates independently from each other. (The key point here is that the servers renew their own certificates. It's not the sysadmin ...


3

The reason you expire and replace HTTPS certs, is that in the case that the certs private key is somehow exposed, an attacker could construct plausible fakes of the websites the certificate identifies. Those sites can be used to steal user credentials, and trick users into unsafe actions. The shorter the time involved, the less damage the attackers can do, ...


12

Today renewing certificates and installing the new versions is often automated. Also, new certificates can be obtained for free from CA like Let's Encrypt. This means there is no significant cost to change certificates often. But renewing certificates long before they expire provides more robustness, because in case something goes wrong one has enough time ...


0

This issue is caused by incorrect time, in my case time was almost correct except it was set to AM when it needed to be PM. Still no clue how the time was set 12 hours off, but did notice a time server update close to when the problem started. Also saw this article on Oct 1, but don't think it was my issue.


0

For me, the root cause turned out to be that I was referencing the wrong cert file. Everything was working well, until one day ALL of my sites suddenly became Not Secure. All the certificates were valid but I was referencing the cert.pem file instead of the fullchain.pem file. In each of my server.js files I replaced: var cert_url = '/etc/letsencrypt/live/&...


2

It should be enough to install the stand-alone ISRG Root X1 certificate (as opposed to the cross-signed version). Your version of Firefox supports multiple validation paths and will recognize that this is the same X1 in both cases. (Same situation as this post, for example.) Use another browser to download the "Self-signed" ISRG Root X1 from ...


1

I just encountered a similar problem to this yesterday - my web server was only serving the site certificate, not the full certificate chain. Some computers were finding the R3 certificate and were happy, but several macOS computers were not finding the new R3 certificate, instead using an older one, which expired on 29 September (two days ago), and whose ...


-1

First of all yesterday there was many reports of this same issue on Mac and Apple in the LetsEncrypt forum. For this specific case it turned out that the issue is related to a wrong configuration in the start server script. Please see here for full details https://community.letsencrypt.org/t/net-err-cert-date-invalid/161001/19


0

Digging, I found a similar post which helped solve my Windows permission problem. Post was: Unable to use client certificates in Chrome or IE on Windows 10 Borrowing kliron's steps, here's what I did, with new screenshots: Client certificate is already installed (see certmgr screenshot above). Start -> Run -> mmc.exe File menu -> Add/Remove Snap-...


0

Force a renewal of your Let’s Encrypt certificate. You can force a renewal of your Let’s Encrypt certificate on the host and that should clear up the issue. While other answers here describe and explain the underlying issue well, a forced renewal of the certificate should clear this up. Try running this certbot command on the server that hosts www.dimsum.dk ...


1

When I try to access my website using https I receive the below error. This error only occurs from my computer regardless which browser I am using to access the home page. I am going to make the educated guess that your system time is actually accurate, but due to the time zone you are in, your system time the browser is reporting the certificate as invalid....


0

From the post Java control panel setting these settings seem to be: deployment.security.tls.revocation.check=NO_CHECK deployment.security.tls.revocation.check. Locked


0

Did you do any Google search? Cause: Github xca issues 203 Basically it’s due to a change in Debians OpenSSL package.


Top 50 recent answers are included