Daniel Araújo Miranda

Hello @drbo and @zsck, it did cross my mind to flag these weak algorithms somehow. I have no idea, however, on how to establish a threshold for that kind of...

Hello, @zsck. I made a suggestion on issue #296 to add that information to a table alongside other implementation metadata. I believe that would be most useful not only to...

Hi @horrorho, this is the suggestion I made here and on issue #296: 1. Document the implementation status of the various ciphers in a table in readme.md (actually @tarcieri's suggestion,...

Now to the core of this issue, maybe we could settle on three arguments: a) Whether the obsolete/flawed/unsafe algorithms should be removed. I am also strongly opinionated that the primitives...

@zsck brings an interesting point in that we are discussing this issue for some time already. In the name of simplicity, I propose the following actions for solving this issue:...

By the way, I also think the **unsafe** keyword should not be used for guarding against using obsolete primitives. And, @zsck, posting to an active issue, even if it's old,...

Hi everyone, I submitted pull request #388 to include a warning about known vulnerabilities in readme.md. Suggestion for possible steps from here (volunteers needed): - You may submit a pull...

That implementation is licensed only under MIT. Is that acceptable? Maybe a more senior contributor to this project can get in touch with bryant about changing the license if necessary.

Hello, I like @tarcieri's idea of implementing a table. I would like to suggest that this table: - Is built automatically from documentation strings inside the implementation itself, and a...

Hi @scottm73, here is what I have seen so far. General checklist: - License is OK. It is an exact copy of the one in the aes.rs file (dual MIT...