Crypto algorithm
See original GitHub issueGood morning, I see you have merged the latest crypto functionality updates. An apology is warranted, it seems the algorithm for the latest updates in the Readme.md file also needs to change. The default is now aes-256-gcm. The remaining verbiage can be removed as well. Have a good afternoon.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Cryptographic Algorithm - an overview | ScienceDirect Topics
Cryptographic algorithms are used for important tasks such as data encryption, authentication, and digital signatures, but one problem has to be solved to ......
Read more >Summary of cryptographic algorithms - according to NIST
Understanding the three classes cryptographic algorithms (hash functions, asymmetric algorithms, symmetric algorithms) in the context of their ...
Read more >How a single-strategy crypto algorithm turned $100 into ...
How a single-strategy crypto algorithm turned $100 into $36,205 in 10 months ... rather than an actual way to make money in crypto...
Read more >What is Cryptography? Types of Algorithms & How ... - Intellipaat
Cryptographic algorithms or ciphers are mathematical functions that are combined with keys, such as phrase, digit, word, etc., to encrypt text.
Read more >What is Cryptography? | Cryptographic Algorithms - Edureka
In Cryptography, a transposition cipher is a method of encryption by which the positions held by units of plaintext (which are commonly ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Thanks for the notice. It’s still wip, was planning to refresh readme along with package meta and version, but the info come in handy!
Readme updated, reflecting the change mentioned here.