tls1.2

问题 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 am working with a client app in Xamarin on Android and I need TLS 1.2 and NTLM. So far, I have been using the regular System.Net.HttpClientHandler and it has worked fine - it looks like this: new System.Net.Http.HttpClientHandler() { Credentials = credentials }; But now I have a new customer and I need TLS 1.2. So I made this code for Android: new Xamarin.Android.Net.AndroidClientHandler() { Credentials = credentials }; With the environment variable: XA_HTTP_CLIENT_HANDLER_TYPE=Xamarin

问题 I have a WCF service which sends an outgoing request. Currently it is using SSL 3.0 or TLS 1.0 . The service I am sending the request to now only accepts TLS 1.2 . I can set the SecurityProtocolType just before the request (and for each request), but I would like it to use TLS 1.2 for all outgoing requests without having to specify it for each request. This code sets it correctly for the request: <OperationContract(), WebGet(UriTemplate:="...")> Public Function SomeService() System.Net

问题 I have uploaded a client certificate to Azure and are trying to make a post to a api method with this certificate. My code works when I am debugging on my local computer but it fails when I run it on Azure as a App Service. System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.Http.WinHttpException: A security error occurred at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter

问题 I developed a .net web service in .net framework 4.0 and deployed in widows server 2008 R2. Customers are able to consume the web service without any issues. Recently we upgraded the SSL certificate protocol from SSL 3.0 to TLS 1.2. The customers are unable to consume the web service after my protocol upgrade. I gone through some forums i found .net 4.0 doesn't support TLS 1.2 protocol so can anyone suggest the best solution to overcome this without upgrading the .NET framework? 回答1: TLS 1.2

问题 I am trying to connect to Azure using Powershell. When I try the command Login-AzureRmAccount, I get a pop-up to enter my credentials. But, immediately after that I get an error: Login-AzureRmAccount : Service returned error. Check InnerException for more details: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. At line:1 char:1 + Login-AzureRmAccount + ~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : CloseError: (:) [Add-AzureRmAccount],

问题 In my jetty configuration file I am using ExcludeCipherSuites tag to exclude some protocols and everything works fine and my jetty server supports all TLS versions (1.0, 1.1, 1.2). However when instead of excluding bad ciphers, I use IncludeCipherSuites to include only supported ciphers, my jetty server starts supporting only TLS 1.2. Other TLS versions (1.0 and 1.1) are becoming not supported. I even tried to whitelist all possible ciphers using IncludeCipherSuites like below: <Set name=

问题 I have created a self signed certificate with openssl and sha 256 like the following: openssl req -x509 -nodes -sha256 -days 365 -newkey rsa:2048 -keyout server.key -out server.crt and I've installed it correctly in my AMPPS server by configuring httpd-ssl.conf file. If I try to perform, on a web browser: https://localhost I correctly see that connection uses TLS 1.2. When I run my app under iOS 9 simulator, I guess that error (9813) is raised because my certificate is self signed. Is there a

问题 I'm trying to migrate an HTTPS server from Express to Hapi. The server is running fine on Express, but when I try to run it in Hapi I get messages saying "Invalid server options" and "TLS is not allowed". This is my (simplified) code with Express: var fs = require('fs'); var https = require('https'); var app = require('express')(); var options = { key: fs.readFileSync('server.key'), cert: fs.readFileSync('server.crt') }; app.get('/', function (req, res) { res.send('Hello World!'); }); https

问题 I've changed to this settings, but TLSv1.0 is still appearing on the testing. Can anyone help please? cat /etc/letsencrypt/options-ssl-nginx.conf ssl_session_cache shared:le_nginx_SSL:1m; ssl_session_timeout 1440m; ssl_protocols TLSv1.2; ssl_prefer_server_ciphers on; ssl_ciphers "ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256