Timeline for What are some ways to ensure that a cryptography library is reliable in an ecosystem that is new to me?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 28, 2022 at 1:29 | comment | added | Mark | " Obviously, in cases where all of the cryptography services are built into a language's standard library, this is less of a problem." -- personally, I wouldn't trust the standard PHP cryptography functions as far as I could throw them. | |
| Jun 27, 2022 at 10:08 | comment | added | Steffen Ullrich | @Bergi: "... good cryptography library to have fewer updates than a bad one" - I don't think it is that simple. The number of updates is related to a) how well a library is maintained and b) how complex it is and how many features and c) how much development is going on t´in terms of new features, improved documentation ... a) and c) might result in more updates for good libraries than for bad libraries, while b) will favor small libraries compared to featureful ones. And a library which is not maintained anymore will not get any updates even it might be full of bugs. | |
| Jun 27, 2022 at 3:44 | comment | added | Bergi | I would expect a good cryptography library to have fewer updates than a bad one. | |
| Jun 27, 2022 at 2:26 | comment | added | user264392 | Unless you have a lot of time to do a full investigation the answer is simple: find someone experienced and smart. Use what they use. They probably have reasons. | |
| Jun 27, 2022 at 0:00 | history | tweeted | twitter.com/StackSecurity/status/1541209760481132544 | ||
| Jun 26, 2022 at 14:51 | history | became hot network question | |||
| Jun 26, 2022 at 7:24 | answer | added | Steffen Ullrich | timeline score: 12 | |
| Jun 26, 2022 at 6:51 | history | asked | the_endian | CC BY-SA 4.0 |