New answers tagged certificate
The protocol itself does not allow you to host two SSL certificates on the same port on the same IP. From the Tomcat SSL Configuration HOW-TO: Using name-based virtual hosts on a secured connection can be problematic. This is a design limitation of the SSL protocol itself. The SSL handshake, where the client browser accepts the server certificate, must ...
While replying parties consume your AD FS service, you cannot control how the replying party applications work. You need to work with them to reduce service down time. http://www.maplelanetechnologies.com/Blog/Post/6/ADFS-3-0--Token-Signing-Certificate-Renewal-and-Service-Downtime
I don't know why would you ever need a script that generates certs? Once puppet generates the cert that should be good for as long as you have the client (agent). Unless you removed the client and create a new client machine with the same hostname. If you run puppet, it will complain saying that there is private key mismatch. Instead you should clean out the ...
Certificates are public. Private keys are private. The private key you generated before requesting the cert is what you need to be careful with.
You can controll what CA should be trusted by NPS by configuring its Trusted Root Certificate Authority. Simply Remove all "soft" CA from the store. I am not aware of any other options.
I contacted Comodo and downloaded a bundle.crt file from them. I renamed it to ssl.ca, as per this server's setup, and now the cert passes all tests. Chain issues = Contains anchor isn't a problem (see below) Worth noting: the widely regarded as most complete test now shows Chain issues = Contains anchor, whereas before it used to show Chain issues = None ...
If the chain is sufficient depends on the CA store of the client. It looks like Firefox and Google Chrome have included the certificate for "COMODO RSA Certification Authority" end of 2014. For Internet Explorer it probably depends on the underlying OS. The CA might not yet be included in trust stores used by non-browsers, i.e. crawlers, mobile applications ...
The fqdn of the puppetmaster needs to be defined in the puppet.conf that resides on the agent. /etc/puppet/puppet.conf [main] logdir = /var/log/puppet ... [agent] server=fqdn_puppetmaster Once the server has been specified and puppet is run again the issue should be solved. In order to check whether the fqdn has been changed the command ...
After days of researching I haven't found the reason at the lowest meaningful level but slightly higher than tat. The script worked when the user it was logging in as was already logged in interactively on the machine. If I sign out of the machine, then the script stops working. This was a problem with WinRM and one of the workarounds was to use CredSSP ...
The idea behind a CA is to share trust to multiple actors. If you are to just communicate with two of your own computers, you can set up personal certificate (you can even self-sign them, could be preferable since many certificate-able application try to check signatures), then you add this certificate into the approved certificate list of the client. ...
I have read man pages and found solution. Create file ~/.lftp/rc and add there next line: set ssl:check-hostname false;
Top 50 recent answers are included