-
java -jar TLS-Server.jar -port 4433 -version TLS13 -executor_type THREADED_SERVER
09:34:23 [main] INFO : ThreadedServerWorkflowExecutor - Initializing server connection end at port 4433
09:34:23 [ma…
-
# Bug Report
According to TLS1.3:
```
A server MAY request that a client present an OCSP response with its
certificate by sending an empty "status_request" extension in its
CertificateRequest mes…
-
## Description
I have been using the module with success for a while now. A change in our target solution now requires sticky sessions to some target groups. When I attempt to modify from action.ty…
-
### Suggested enhancement
I found one issue when we tested the following early data fallback 1-RTT test case:
* Client completes the initial full handshake with the server and receives NewSessionTic…
-
# Bug Report
## System Information
| Type | Version/Name |
| ------------------------ | ------------ |
| Operating System Name | Fedora |
| Operating System Version | 2…
-
### Brief description
When connecting to a TLS server using TLS1.3 that negotiates TLS_CHACHA20_POLY1305, using tlsSessions fails with `ValueError: not enough values to unpack (expected 3, got 2)`
…
-
### Suggested enhancement
[ssl_tls13_parse_new_session_ticket_exts](https://github.com/hannestschofenig/mbedtls/blob/tls13-prototype/library/ssl_tls13_client.c#L3132) no longer parses the early data …
-
Specifying the string:
`GODEBUG=tls13=1`
as environment variable setting in the debugging settings (which works perfectly well e.g. on Linux) does not save in the app, but the message that this stri…
-
In upstream Mbed TLS, there has been a major code restructuring regarding the example programs: A lot of shared code between `ssl_client2` and `ssl_server2` has been moved into a new source file.
B…
-
In local ("closed circuit") or test environment it might be desired to use a self-signed certificate.
For example, using a local email server to test `ssl_mail_client` application with TLS 1.3.
Conn…
irwir updated
2 months ago