aes-encryption
Here are 496 public repositories matching this topic...
-
Updated
Feb 19, 2020 - JavaScript
-
Updated
Dec 19, 2017 - Java
-
Updated
Apr 5, 2020 - JavaScript
-
Updated
Nov 12, 2018 - Java
-
Updated
May 23, 2020 - JavaScript
-
Updated
Jun 23, 2020 - Python
-
Updated
Jun 30, 2020 - PHP
-
Updated
Jun 11, 2020 - Java
-
Updated
Jan 7, 2018 - Objective-C
-
Updated
Feb 10, 2020 - Swift
-
Updated
Jan 20, 2020 - Objective-C
-
Updated
Mar 19, 2020 - Python
-
Updated
Apr 10, 2017 - Java
-
Updated
Jun 10, 2017 - Python
-
Updated
Jun 30, 2019 - Shell
-
Updated
Jun 24, 2020 - TypeScript
-
Updated
May 21, 2020 - Python
-
Updated
Dec 18, 2018 - Java
-
Updated
Sep 24, 2019 - PowerShell
-
Updated
Nov 10, 2019 - JavaScript
-
Updated
Apr 30, 2020 - C
Everything is currently in pixcryption.core.lib but I feel some functions might be better in a helper namespace to help readability of the code. This is a good first issue if you'd like to refactor/clean up the code base!
-
Updated
May 7, 2020 - Go
-
Updated
Aug 2, 2019 - Java
-
Updated
Jun 8, 2018 - Java
-
Updated
Jan 27, 2020 - C++
Output from $ nimble install nimaes
`
Downloading https://github.com/jangko/nimAES using git
Warning: File inside package 'nimAES' is outside of permitted namespace, should be named 'nimAES.nim' but was named 'test.nim' instead. This will be an error in the future.
Hint: Rename this file to 'nimAES.nim', move it into a 'nimAES/' subdirectory, or prevent its installation by adding
-
Updated
Nov 16, 2018 - PHP
Improve this page
Add a description, image, and links to the aes-encryption topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the aes-encryption topic, visit your repo's landing page and select "manage topics."
Discussing with Mexicoleaks it has been identified valuable to add a feature to make it possible for an admin to add instructions to be provided to users when downloading files.
This could be useful to always provide documentation to users part of the project; this documentation is expected to be used for training users about risks related to malware and metadata.
The idea is that any file d