self-signed

In the previous months I developed a sandbox Java applet for an academic project. I wasn't able to sign it with a trusted Certificate Authority because of the restricted budget. With the release of Java 1.7.51 I found that the new security restrictions forbid the execution of the applet, because of the lack of signature. Until now, I have found two rough solutions to this problem: ask the user to include the applet page on his/her exception lists; ask the user to set the Java security level to "Medium" (which, of course, is a risky manoeuvre). Is there a way to overcome the restrictions

I have a WCF service that is ONLY every used between two server machines. It will NEVER be used publicly. I was hoping I could use SSL with a self signed certificate for security. I created a certificate using IIS7, installed it on the client machine using IE and the MMC (Personal, TrustedRoot, Third-Party & TrustedPeople). I still can't get to the service, either from code or via IE8, without it questioning the certificate. From IE I get the usual "There is a problem with this website's security certificate." From code I get the error: "Could not establish trust relationship for the SSL/TLS

I'm trying to communicate with a service over powershell but I am failing miserably. I suspect it is the certificate and I have googled for the answer and found two options, none of which worked for me. I have also tried to combine the two unsuccessfully. Option 1: add-type @" using System.Net; using System.Security.Cryptography.X509Certificates; public class TrustAllCertsPolicy : ICertificatePolicy { public bool CheckValidationResult( ServicePoint srvPoint, X509Certificate certificate, WebRequest request, int certificateProblem) { return true; } } "@ [System.Net.ServicePointManager]:

I'm trying to create a self-signed wildcard SSL certificate for use on a number of development and test servers running IIS 6. Following various guides has led to a couple ways of generating the certificates, but I haven't had any luck getting it to work. The most successful ways I've had were following this OpenSSL guide and using makecert.exe like so: makecert.exe -r -b 01/01/2009 -e 01/01/2042 -sr LocalMachine -ss MY -a sha1 -n CN="*.example.com" -sky exchange -pe -eku 1.3.6.1.5.5.7.3.1 -sy 12 -sp "Microsoft RSA SChannel Cryptographic Provider" wildcard.cer Both of which generate

How to create self-signed root certificate and intermediate CA to be imported in Java keystore? We will use this for SSL and TLS, and later for Client certificate based CLIENT-AUTH authentication. Using OpenSSL and KeyTool. tuomassalo Just a side note for anyone wanting to generate a chain and a number of certificates. Refining @EpicPandaForce's own answer, here's a script that creates a root CA in root-ca/ , an intermediate CA in intermediate/ and three certificates to out/ , each signed with the intermediate CA. #!/bin/bash -x set -e for C in `echo root-ca intermediate`; do mkdir $C cd $C

For various reasons I have created a simple HTTP server, and added SSL support via OpenSSL. I'm using self-signed certificates. IE, Firefox and Chrome happily load content as long as I add the CA to the trusted root CAs. However, wget (even when using the --no-check-certificate flag) reports: OpenSSL: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure If I run the OpenSSL client against my server using: openssl s_client -connect dnvista:82 -debug I get back: verify error:num=19:self signed certificate in certificate chain verify return:0 and then 5852:error:14094410:SSL

I am using libcurl in my C application to communicate with an HTTPS server that I have set up. I generated a self-signed certificate on that server that I wish to use with curl. I am aware of setting CURLOPT_SSL_VERIFYPEER to 0 to bypass the SSL verification, but I wish to add the generated certificate to curl's "valid" CA certificates. I have tried setting CURLOPT_CAPATH and CURLOPT_SSLCERT to the location of the server SSL public key, but it fails to pass the verification. How can I add my own CA/Self-signed certificate so that libcurl will successfully validate it? To add a self-signed

I try to generate a self-signed certificate for a custom local domain pointing to 127.0.0.1: # /etc/hosts 127.0.0.1 subdomain.domain.local I've generated a self-signed certificate using openssl and remember that everything worked in the past. But it seems that since Chrome 58, there are far more restrictions on using self-signed certificates. My attempts conclude with " Your connection is not private " following with one of the below errors: " security certificate is not trusted " if I proceed like in the past. " not a certification authority " when trying to import it into Chrome. " subject