self-signed

问题 AFAIK, it was a common scenario to buy a production SSL certificate for mydomain.com, and use a self-signed certificate (eg using java's keytool) for CN localhost to use during development. In the interests of security, it seems that very recent versions of Firefox (33) and Chrome (39) may forbid this approach. Is that correct? If so, what is the new-fangled approach these browsers expect you to take during development? 回答1: Yes, self-signed certificates are still supported by most mayor web

问题 We've been running CI with Xcode 5.0 for some time with no issue. Now iOS 7.1 has been released it seems to install the products that the CI produces you need to be on https but it seems that self signed certs are ok. I have switched to https (self-signed) which loads the bot page fine, but when you go to install the product from the link it says cannot connect to server Trying to install it on http causes the error Cannot install applications because the certificate for 'server' is not valid

问题 I recently generated self signed certificate using OpenSSL with common name as 'localhost' it works fine. I tried using IP address instead of localhost, which Chrome browser rejected saying ERR_CERT_COMMON_NAME_INVALID , because IP address is not resolved to common name. How can I fix it? 来源： https://stackoverflow.com/questions/49685462/how-to-use-ip-address-as-common-name-in-selfsigned-certificate

问题 I've generated a self-signed certificate for my Java app using keytool. However, when I go to the site in a browser it always pops up with a warning - saying this site does not own the certificate - is there a way to self-sign/doctor a certificate so I won't get these warnings in a browser? Both server and browser are located on the same host and I navigate to the site using "http://localhost/". I do not want to add an exception to the browser because I have tests which run on a big build

问题 I want to communicate with a POP3 server with ssl and port 995 with my client app the certificate of server is self-signed and while running the app the error that received is: The certificate is self-signed, and untrusted A part of code is: socket = new QSslSocket(this); QFile certfile("D:\\hani\\cert\\localhost.localdomain.pem"); Q_ASSERT(certfile.open(QIODevice::ReadOnly)); QList<QSslCertificate> certList; QSslCertificate cert(&certfile,QSsl::Pem); certList.append(cert); socket-

问题 I'm trying to make my app communicate with my server via https. As I don't want to pay to get my server certificate signed by a trusted CA, the solution is to use a self signed certificate. So, I've created my caconfig.cnf as follows: [ ca ] default_ca = CA_default # The default ca section [ CA_default ] dir = ./demoCA # top dir database = $dir/index.txt # index file. new_certs_dir = $dir/newcerts # new certs dir certificate = $dir/cacert.pem # The CA cert serial = $dir/serial # serial no

问题 I'm using Grunt with grunt-nwabap-ui5uploader plugin to deploy an application to NW ABAP server, I have written a upload task in Gruntfile and trying to execute it, but having an error about self signed certificate, which aborts the task. I have tried to use option --force to ignore the warning but it seems that this task isn't executed: > Running "nwabap_ui5uploader:upload_webapp" (nwabap_ui5uploader) task > Warning: Error: self signed certificate (undefined) Used --force, continuing. > >

问题 I'm currently getting this "SSL error" on the simulator of my app. Error Screenshot I have my own self-signed certificate. And this problem can be solved by installing the cert file manually on the simulator. However, we are trying to avoid manually installing the certificate to the simulator (drag and drop) every time after building the app. And instead, I want to find a way to import the certificate file into our ios app bundle. I followed this article and tried with the following way, but

问题 I run WCF service exposes API on local machine (https://localhost:8080/MyApi), self signed SHA-256 certificate registered on local machine, executed " netsh http add sslcert ipport=0.0.0.0:8080 certhash=... appid=... " and when browsing to https://localhost:8080/MyApi from Chrome it shows ERR_CONNECTION_RESET. Now the funny part: Works fine with Chrome v41. Happened only after upgrading to Chrome v69 (and same on v71). Browsing from IE works well. Calling the API from PowerShell web-invoke

问题 I can't get android to trust my self-signed cert/ca. I tried the following in this video: Generate CA and cert for m.m with the script as shown (and below). Reload nginx with the new cert file (may not be necessary) Copy the CA to my local device Install the CA Confirm it is installed and 'trusted' under user certificates Try to go to m.m Cert is not trusted I have read several guides that say I should be able to generate a CA, install/trust the CA on the device, then anything the CA signs