tls

Which TLS version does Netty support? TLS 1.0, 1.1 or 1.2?

匿名 (未验证) 提交于 2019-12-03 07:50:05
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: Which TLS version does Netty support? TLS 1.0, 1.1 or 1.2? I looked at http://netty.io/5.0/xref/io/netty/handler/ssl/SslHandler.html but it doesn't say which version exactly. 回答1: It may depend upon a few things. For example: 1) What version of java are you using and are you using Netty as a client or server? Java 1.7 enables TLS 1.2 in server mode but disables it in client mode by default. See https://blogs.oracle.com/java-platform-group/entry/java_8_will_use_tls for reference. 2) Are you using the Java or OpenSSL JNI providers? That java

Android - SSL/TLS and ECC (Elliptic curve cryptography)

匿名 (未验证) 提交于 2019-12-03 07:50:05
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I'm developing an android application which communicates with a web server. We use HTTPS for this communication and we have also a client certificate inside the android application for authentication. We created SSL certificates using ECC (ANSI x9.62) in order to have very small certificates so we can reduce the transmission cost during handshake. The source code for the communication is more or less like this: InputStream keystoreIs = getResources().openRawResource(R.raw.client_bks); KeyStore keystore = KeyStore.getInstance("BKS"); keystore

SSLHandshakeException: Handshake failed on Android N/7.0

匿名 (未验证) 提交于 2019-12-03 07:50:05
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I'm working on an app for which the (power)users have to set up their own server (i.e. nginx) to run the backend application. The corresponding domain needs to be configured in the app so it can connect. I've been testing primarily on my own phone (sony z3c) and started developing for 5.1. Later I received an update for 6.0 but still maintained a working 5.1 inside the emulator. Not too long ago, I started to work on an AVD with an image for 7.0 and to my suprise it won't connect to my server, telling me the ssl handshake failed. My nginx

Java SSL SSLHandshakeException handshake_failure

匿名 (未验证) 提交于 2019-12-03 07:36:14
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I am using java 8 and requesting with SSLSocket this url: https://www.flixbus.de/sites/default/files/6_jetzt_buchen_button_tiny.png I always get a handshake error. socket.setEnabledProtocols() to force use of a specific protocol didn't help. Btw, all other web servers work fine. So it's probably not related to my code. This error also occurs without any ssl/tls protocol restriction. Any ideas? The output with option "javax.net.debug=all" is as follows: DEBG getSecureScocket: Supported protocols: - SSLv2Hello - SSLv3 - TLSv1 - TLSv1.1 - TLSv1

SSL与TLS的不同

陌路散爱 提交于 2019-12-03 04:03:13
SSL 与 TLS 1 SSL (Secure Socket Layer,安全套接字层) SSL为Netscape所研发,用以保障在Internet上数据传输之安全,利用数据加密(Encryption)技术,可确保数据在网络上之传输过程中不会被截取,当前为3.0版本。 SSL协议可分为两层: SSL记录协议(SSL Record Protocol):它建立在可靠的传输协议(如TCP)之上,为高层协议提供数据封装、压缩、加密等基本功能的支持。 SSL握手协议(SSL Handshake Protocol):它建立在SSL记录协议之上,用于在实际的数据传输开始前,通讯双方进行身份认证、协商加密算法、交换加密密钥等。 2 TLS (Transport Layer Security,传输层安全协议) 用于两个应用程序之间提供保密性和数据完整性。 TLS 1.0是IETF(Internet Engineering Task Force,Internet工程任务组)制定的一种新的协议,它建立在SSL 3.0协议规范之上,是SSL 3.0的后续版本,可以理解为SSL 3.1,它是写入了 RFC 的。该协议由两层组成: TLS 记录协议(TLS Record)和 TLS 握手协议(TLS Handshake)。较低的层为 TLS 记录协议,位于某个可靠的传输协议(例如 TCP)上面。 3 SSL

Mutual authentication in SSL/TLS

匿名 (未验证) 提交于 2019-12-03 03:11:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I am new to SSL authentication and I have a requirement to authenticate two architectural components over a trust boundary with SSL (I have control over both components). I think I will need two way SSL authentication with both the server and client having certificates. Can the certificates be self-signed? (ie. signed by the vendor, and this won't nullify using SSL in the first place? Or do I need a third party verification service to ensure the identity of the certificate?) How does the handshake work in terms of public and private keys for

Why ServicePointManager.SecurityProtocol default value is different on different machines?

匿名 (未验证) 提交于 2019-12-03 03:06:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: Currently I have an issue and can't find strict answer on it. I have ASP.NET MVC 5 application targeting 4.6.1 framework and its goal is to work with third party API's that are secured by TLS 1.1/TLS 1.2 protocols. I have tried to run my application on 2 environments: my local machine Windows 10 with .NET 4.6.2 Framework, IIS Express; server machine Windows Server 2012 with .NET 4.6.1, IIS 8.0; The issue is in that when I start it locally ServicePointManager.SecurityProtocol default value is set to Ssl3, Tls , so I can't target API's and

What does this TLS Alert mean?

匿名 (未验证) 提交于 2019-12-03 03:03:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I am looking at a Microsoft Network Monitor capture of an HTTPS "GET" request which mysteriously never completes if performed by .NET HttpWebRequest . I have found that the Server Hello contains an Alert entry which looks like this: I have these questions: Is this alert really encrypted? I read that alerts do come encrypted if sent after a key exchange, but as you can see, this occurs very early in the negotiation stage, at Server Hello. If not encrypted, is it malformed? The first byte, 01 , suggests it's a warning, but the 70 ("Protocol

Am I trying to connect to a TLS-enabled daemon without TLS?

匿名 (未验证) 提交于 2019-12-03 02:52:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I'm trying to learn about Docker , but I keep getting cryptic (to me) error messages. Possibly the simplest example of this is trying to print the version of Docker I installed: $ sudo docker version Client version: 1.4.1 Client API version: 1.16 Go version (client): go1.3.3 Git commit (client): 5bc2ff8 OS/Arch (client): darwin/amd64 FATA[0000] Get http:///var/run/docker.sock/v1.16/version: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS? I've just been going through

What does the DOCKER_TLS_VERIFY and DOCKER_CERT_PATH variable do?

匿名 (未验证) 提交于 2019-12-03 02:52:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 由 翻译 强力驱动 问题: I am new to Docker, using boot2docker on Windows 7. While I was trying to configure Docker build through spotify maven plugin, I was asked to set below env variables : DOCKER_HOST DOCKER_CERT_PATH DOCKER_TLS_VERIFY Configuration was successful but am not sure What does the DOCKER_TLS_VERIFY and DOCKER_CERT_PATH variables do ? 回答1: As mentioned in the README : By default, boot2docker runs docker with TLS enabled . It auto-generates certificates and stores them in /home/docker/.docker inside the VM. The boot2docker up command will