/explore
|
You are here 
|
gist.github.com | ||
| | | | |
crpt.fyi
|
|
| | | | | Issues for organizations and discussions, repo for debriefs and resources - Call For Proposal · francep2p/community Wiki | |
| | | | |
jaylittle.com
|
|
| | | | | Today's post is going to examine an ethical grey area that I currently find to be very relevant. Is it ever okay to ignore responsible disclosure standards for security related issues? Spoiler alert: I'm going to argue that there are cases in which ignoring these standards is not only permissible but the only real ethical course of action. Okay so lets start with some sample code. The below code represents a simple . | |
| | | | |
github.com
|
|
| | | | | A C# / .NET client driver for RethinkDB. Contribute to mfenniak/rethinkdb-net development by creating an account on GitHub. | |
| | | | |
blog.0x7d0.dev
|
|
| | | The AES algorithm is widely used today, whether it's for encrypting a connection to a website, encrypting data on your hard drive, or storing passwords in your favorite password manager. It has been battle-tested for many decades and is still recommended as one of the most secure algorithms. In this article, I explain how AES encryption works and how the algorithm is implemented. | ||
