cipher
Here are 547 public repositories matching this topic...
Currently, testssl prints a big red warning when a server has no server preferred cipher order.
Mozilla recently relaxed their recommendations regarding cipher order. If only strong cipher suites are supported anyway, why not deciding according to the client's preferences. Maybe it's a phone that wants to optimize for performance on low hardware. Additionally, often browsers are better maintain
Preface: I am not an expert in encryption, so sorry for any inaccuracies with how I am describing the issue here.
In the documentation, it states:
// Note: CBC and ECB modes use PKCS#7 padding as default
Is it possible to configure what padding is used? I am working with a system where they are not expecting padding. Is that something that even makes sense/is possible?
-
Updated
May 18, 2020 - JavaScript
-
Updated
Jul 10, 2019 - Python
-
Updated
Apr 17, 2020 - Java
-
Updated
May 21, 2020 - JavaScript
-
Updated
Feb 9, 2020 - Python
-
Updated
May 10, 2020 - C
-
Updated
May 6, 2020 - Dart
-
Updated
Nov 12, 2019
-
Updated
May 21, 2020 - Assembly
-
Updated
Apr 9, 2019 - Swift
-
Updated
May 30, 2019 - C++
-
Updated
Jan 14, 2020 - Python
-
Updated
Mar 5, 2020 - Ruby
-
Updated
Nov 30, 2016 - C
-
Updated
Apr 28, 2019 - Java
-
Updated
Apr 4, 2020 - C
-
Updated
Jul 28, 2019 - C++
-
Updated
Apr 30, 2020 - C
-
Updated
Apr 24, 2020 - Rust
Improve this page
Add a description, image, and links to the cipher topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the cipher topic, visit your repo's landing page and select "manage topics."
It doesn't seem intuitive to me that Aes is a stateless object. You can create an instance of it with a BlockMode, which seems to imply to me that several encrypt/decrypt of the same data would produce different results each time.
If Aes is going to remain stateless, it would be nice to be explicity about this in the docs.