ssl

问题 Have recently updated application from Oracle Java 9 to AdoptJDk 11.0.6 and I am now seeing errors of the form this code: public static String convertWikidataUrl(String wikidataUrl) { String qPage = wikidataUrl.substring(wikidataUrl.lastIndexOf('/') + 1); String apiUrl = WIKIDATA_IMAGE_API_URL + qPage; try { URL url = new URL(apiUrl); HttpURLConnection uc = (HttpURLConnection) url.openConnection(); int responseCode = uc.getResponseCode(); if (responseCode != HttpURLConnection.HTTP_OK) {

问题 I try to compile/build scala project with sbt, there are two plugins mentioned in project/plugins.sbt: addSbtPlugin("com.typesafe.play" % "sbt-plugin" % "2.6.17") addSbtPlugin("com.typesafe.sbt" % "sbt-native-packager" % "1.3.4") Error while importing sbt project: [error] sbt.librarymanagement.ResolveException: download failed: com.typesafe.play#sbt-plugin;2.6.17!sbt-plugin.jar [error] download failed: com.typesafe.sbt#sbt-native-packager;1.3.4!sbt-native- packager.jar Seems that problem in

问题 Why am I getting an error when trying to import ssl in python3 ? Python 3.7.4 (default, Jul 9 2019, 18:13:23) [Clang 10.0.1 (clang-1001.0.46.4)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import ssl Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/Cellar/python/3.7.4/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py", line 98, in <module> import _ssl # if we can't import it, let the error propagate

问题 OK, so I used to be able to change the SSL port number in the project properties dialog, but after the asp.net 5 RC1 update, the SSL field is read-only: It ignores the SSLPort value when I attempt to edit the .xproj directly: <PropertyGroup> <SchemaVersion>2.0</SchemaVersion> <DevelopmentServerPort>17204</DevelopmentServerPort> <SSLPort>44303</SSLPort> </PropertyGroup> And it also resets the port in my app host config file ($[solutionDir].vs\config\applicationhost.config) back to the original

问题 OK, so I used to be able to change the SSL port number in the project properties dialog, but after the asp.net 5 RC1 update, the SSL field is read-only: It ignores the SSLPort value when I attempt to edit the .xproj directly: <PropertyGroup> <SchemaVersion>2.0</SchemaVersion> <DevelopmentServerPort>17204</DevelopmentServerPort> <SSLPort>44303</SSLPort> </PropertyGroup> And it also resets the port in my app host config file ($[solutionDir].vs\config\applicationhost.config) back to the original

问题 I am using Jetty client to send outgoing requests. Code that runs perfectly under Java 10 suddenly gets the following exception under Java 11: javax.net.ssl.SSLException: No PSK available. Unable to resume. at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:129) at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:308) at java.base/sun.security.ssl.TransportContext.fatal

问题 I've installed Anaconda and had SSL problems when trying to do API calls via Jupyter Notebooks: import requests import certifi r = requests.get('https://github.com/') print(r) This first produced a SSL connection error. Which I could solve after extensive search and the help of our IT department. The solution here was to add the company root certificate to certifi cert storage. Now for other requests unfortunately I still have the same problems. Example code calling the Google Analytics API

问题 Recently deployed a Windows 2016 Standard Server, with Active Directory and Exchange 2016. We have disabled SSL 1.0, 2.0 and 3.0 for both Server and Client, and have disabled TLS 1.0 and TLS 1.1. We are repeatedly getting the following entry in our system log. What is causing this, and how can I fix it. 回答1: Basically we had to enable TLS 1.2 for .NET 4.x . Making this registry changed worked for me, and stopped the event log filling up with the Schannel error. More information on the answer

问题 Recently deployed a Windows 2016 Standard Server, with Active Directory and Exchange 2016. We have disabled SSL 1.0, 2.0 and 3.0 for both Server and Client, and have disabled TLS 1.0 and TLS 1.1. We are repeatedly getting the following entry in our system log. What is causing this, and how can I fix it. 回答1: Basically we had to enable TLS 1.2 for .NET 4.x . Making this registry changed worked for me, and stopped the event log filling up with the Schannel error. More information on the answer

问题 There are numerous posts on SO about this and I have scoured them, but still don't have a solution. I am hoping that someone can point me in the right direction. We have a requirement now to use TLS 1.2 to connect to a remote provider. So I have installed Windows Server 2016 and configured it as needed: I know the remote server is running TLS 1.2 and that it supports the highlighted cipher. We connect to the remote end point using C# proxy class generated by the WSDL provided by the provider