-
Hey there,
I tested my site -> nginx 1.15.1 using Openssl 1.1.1 pre release 8 on
> https://dev.ssllabs.com/
with the following cipher list:
`TLS13-CHACHA20-POLY1305-SHA256:TLS13-AES-256-GCM-S…
-
## Bug Report
#### Current Behavior
I came across this issue when I updated any package, for example, `vscode` and `oh-my-posh`
I have tried PowerShell (7.4.5) and Cmd, and the outputs …
-
https://github.com/openssl/openssl/pull/6746 updated us to the https://tools.ietf.org/html/draft-ietf-tls-tls13-vectors-06 test vectors; we might as well take the https://tools.ietf.org/html/draft-iet…
kaduk updated
5 months ago
-
We have mbedtls_tls_prf_types which is not very proper for the tls1.3 types.
An example:
When we call ssl->f_export_keys(), in mbedtls_ssl_tls13_generate_handshake_keys(), we have not proper type…
-
### What is the issue?
UPDATE: This appears to affect any service trying to communicate with NATS over a linkerd mesh. As long
as the pod initiating the request to NATS is in linkerd mesh and `con…
-
## Expose ALB Listener's SSL Policy As A Manifest Parameter
I want to restrict the minimum TLS version that my clients talk to my service with... for compliance-related reasons.
The problem is tha…
-
klin@asus:~$ linstor n l
```
+--------------------------------------------------------+
| Node | NodeType | Addresses | State |
|==============================================…
-
**Describe the bug**
使用域名代理模式按照官方文档配置Nginx +http_proxy _port
本地https 网站报502
其他http网站都正常、、
nps配置档：
#HTTP(S) proxy port, no startup if empty
http_proxy_ip=0.0.0.0
http_proxy_port=9999
http…
-
Hi, has anyone seen a stack like this from a go panic? This is using version 1.22.5-1
```
SIGSEGV: segmentation violation
PC=0x7faddcc4acb1 m=5 sigcode=1 addr=0x40
signal arrived during cgo exec…
-
Quote:
> As you may have noticed, we released version 3.15.0 of wolfSSL. One of the features in this release was TLS 1.3 Draft 28 support! Draft 28 is the latest version of the TLS 1.3 specification…