Tag Info

New answers tagged

1

The public key is - like it's name suggests - public. It can thus not alone be used for authorization, since everybody knows it. But only the owner of the private key is able to sign some random challenge and this signature can then be verified by everybody having access to the public key - in this case the server which has sent this challenge to the client. ...


0

It should be mx.example.com and to find it out, you can use openssl s_client -connect mx.example.com:465 (smtps) to recreate the secure delivery of an email. Anyways, you need a wildcard ssl certificate that will accept all *.example.com type of subdomains.


0

Probably still unsupported. Try asn1parse. The <unsupported> output was the regular result in 2010. My guess: this is still the case. An OpenSSL dev said this on the mailing list (Archived here.): Steven Hensen, 2010-01-02: Currently OpenSSL doesn't display any otherName values. It can't know the precise meaning of that field in general ...


0

Try using the -config parameter. Please check out the TechNet page for more details on the options included in certreq.exe and certutil.exe. https://technet.microsoft.com/en-us/library/dn296456.aspx I know I am too late to answer this, but hopefully this will help someone else.


1

I think you are looking for a template you can publish in your Windows CA so when someone needs to request an ADFS certificate they can select that template at issuance. If so, I think this is what you are looking for: https://technet.microsoft.com/en-us/library/Dn781428.aspx (note: the title says just getting a certificate but the instructions walk you ...


0

Not sure about a "template", but this question offers a number of ways to generate the certificate - makecert, openssl, and SelfSSL: https://stackoverflow.com/questions/14464441/how-to-create-a-self-signed-x509-certificate-with-both-private-and-public-keys


0

I was also facing similar sort of ssl certificate verification error. Setting verify-certificate to 'no' worked for me. Example: lftp -c 'set ftps:initial-prot ""; set ftp:ssl-force true; set ftp:ssl-protect-data true; set ssl:verify-certificate no; open -u Usename,Password 208.82.204.46; put uploadfilename;'


-1

Do you have any AV or security software installed on the host? Have all Windows Updates been applied? Open properties for Virtualbox.exe in Program Files, go to 'Digital Signatures', 'View Certificate', 'Certification Path'. You should see 3 certs here, all trusted (from root, Verisign, VeriSign Class 3 Code Signing 2010 CA, Oracle Corporation). Confirm ...


0

My problem was that the new Java update didn't remove the old DeploymentRuleSet.jar which was used only by some previous versions, and which in my case resides at: C:\Windows\Sun\Java\Deployment\DeploymentRuleSet.jar The file in this folder does not depend on where the Java installation folder is, and even after Oracle removed Sun name from Java (and, ...


0

It's possible this question will get moved onto another StackExchange site, but I'll supply an answer nonetheless. Little bit of PowerShell magic should make this fairly simple. PowerShell can navigate the certificate store as if it were any other drive (like navigating the file system.) To list all certificates on the system: Get-ChildItem -Path Cert:\ ...


0

This is possible depending on both the Apache version and the OpenSSL version. Running ECC & RSA certificates in parallel on Apache using different intermediate certificates requires Apache 2.4.8+ and OpenSSL 1.0.2+. The sslcertificatefile entry added support for intermediates as of Apache 2.4.8. OpenSSL adds the ability to load intermediates on a ...


1

From GloablSign's ECC Compatibility list it looks like the following are compatible: Browsers: Safari 4 Chrome 1.0 IS 7 (On Vista) Firefox 2.0 Operating Systems: Apple OS X 10.6 Android 4.0 Windows Vista They have Red Hat Linux listed as 6.5. Not sure what it would be for other distros.


2

Microsoft position is correct, but needs a clarification: generally you need to deploy a separate CA server for each *forest*. For example, you don't need to deploy a separate CA in the corp.domain1.com domain, for example. Eventually, there are two supported solutions: like Microsoft said, you have to deploy a separate CA in the each acquired AD forest. ...



Top 50 recent answers are included