-
Poly1305 has a 128-bit authenticator, but the advantage in breaking its integrity without breaking AES is, roughly speaking, $q \cdot \ell_m \cdot 2^{-103}$ for $q$ queries where $\ell_m$ is the numbe…
daira updated
4 months ago
-
Tinc's use of Chacha20-Poly1305 predates IETF standardization of this protocol. The version in RFC 7539 has a slightly different way of handling the initialization vector. This makes tinc's built-in i…
-
I had read some issues (#5050, #541, ...) about the current ciphersuite specification and I decided to implement some improvements:
[https://github.com/OttoHollmann/openssl/tree/Improvement-of-the-ci…
-
I can't seem to find a simple ChaCha20 C implementation for RFC 7539. Most are 64bit nonce , the IETF version uses a 96 bit nonce.
Currently, encrypted payloads are Salsa20 + Poly1305.
-
## Bug description
Can't connect to Tiny SSH Server
On Android Side:
Error Key exchange was not finished, connection is closed.
Cannot negotiate, proposals do not match.
On Server Side:
tinyssh…
-
### Description
I've configured my OIDC server ([Authentik](https://docs.goauthentik.io/integrations/services/matrix-synapse/)) for Synapse using the official [guide](https://matrix-org.github.io/syn…
-
I got `PlatformException (PlatformException(UNSUPPORTED_ALGORITHM, cryptography_flutter does not support algorithm null in Android., null, null))
`
Source code
```
final pbkdf2 = FlutterPbkdf2(
…
-
### Is your feature request related to a problem?
TLSv1.2 is very vulnerable, especially this implementation because CBC RSA and SHA were statically programmed in.
Java supports TLS 1.3 even in bac…
-
求解决方案
-
It seems impossible to connect a openssl client to an openssl server when using DTLS1(.2) and a CHACHA20-POLY1305 cipher.
Investigate what's going on.
Server side:
`./openssl s_server -key CA.key -ce…