-
**Edit: the "no .NET Framework support for ASP.NET Core 2.0" plan has been officially cancelled and running ASP.NET Core 2.0 on .NET Desktop will be supported in the next previews.** For more informat…
-
Hi,
I've been evaluating Salt today and I really like a lot that I've been seeing. I have two questions about the crypto design choices. A selling point of salt is speed but it appears that you are u…
ghost updated
9 years ago
-
A couple times now, I've seen people asking for things currently available in userland to be adopted into core. Some notable examples are:
- Ship websockets in core #1010
- Feature Request: HTTP2 #4
…
-
Currently we have the ability to store private environment variables in the database. I'd like to expand this capability to store encrypted environment variables in the yaml itself, similar to travis.…
-
There are many places where the Let's Encrypt client will generate cryptographic keys or parameters, or set or use cryptographic parameter or algorithm defaults (including defining key sizes and ciphe…
-
Allow the developer to specify which algorithms are used under the covers: BCrypt, managed types, etc.
-
We've previously made the decision not to distribute any crypto with Rust at all, but this is probably not tenable since crypto is used everywhere. My current opinion is that we should not distribute …
brson updated
9 years ago
-
NIST recommends not to use SHA-1 since 2006 http://csrc.nist.gov/groups/ST/hash/policy_2006.html
and even Microsoft decided to get rid of SHA-1 (in TLS certificates) https://www.schneier.com/blog/arch…
-
|[](https://github.com/glyph)| @glyph reported|
|-|-|
|Trac ID|trac#5446|
|Type|enhancement|
|Created|2012-01-05 00:19:07Z|
|Branch|https://github.com/twisted/twisted/tree/trusted-ca-openssl-defaults-…