Arcadia Rose

I'm going to have to respectively disagree. I would agree that no one should be designing new protocols using these primitives. However, I feel that most users probably shouldn't even...

I could get behind the idea of adding some information to the documentation describing the risks/tradeoffs of algorithms. I would suggest that, in the opening paragraph for each primitive's documentation,...

I like that idea, @Spencer-H. I might even go a bit further and store legacy and known-insecure algorithms in an `insecure` module, and encourage people to refer to that module...

This is practically necro-posting at this point, so I appologize if anyone feels that adding to this discussion is a waste, but I'd like to throw another idea into the...

I for one have to agree with @tarcieri. MD5, SHA1, etc. are considered broken by the cryptography community and an argument that they are still somehow suitable for some applications...

@quadrupleslap Unfortunately not everyone does know this. Even if they did, I think that any library that would support legacy crypto should do its part in ensuring such functionality isn't...

Is the full spec implemented now?

`cargo test` is trying to run the example I included which uses TLS, but we don't have any setup to have that happen.

The example isn't broken, there just isn't any setup in place to have the Python server running before it runs. It doesn't compile because cargo test isn't using the `secure`...

I'd also like to know about this. @bvanderlaan