node-sodium | Port of the lib sodium encryption library to Node.js | Encryption library

by paixaop C Version: 3.0.2 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | node-sodium Summary

node-sodium is a C library typically used in Security, Encryption, Nodejs applications. node-sodium has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Port of the lib sodium encryption library to Node.js

Support

Quality

Security

License

Reuse

Support

node-sodium has a low active ecosystem.

It has 351 star(s) with 121 fork(s). There are 11 watchers for this library.

It had no major release in the last 12 months.

There are 13 open issues and 73 have been closed. On average issues are closed in 242 days. There are 5 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of node-sodium is 3.0.2

Quality

node-sodium has 0 bugs and 0 code smells.

Security

node-sodium has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

node-sodium code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

node-sodium is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

node-sodium releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 160 lines of code, 0 functions and 102 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of node-sodium

Get all kandi verified functions for this library.

node-sodium Key Features

No Key Features are available at this moment for node-sodium.

node-sodium Examples and Code Snippets

No Code Snippets are available at this moment for node-sodium.

Community Discussions

Trending Discussions on node-sodium

What am I misunderstanding about password hashing?

QUESTION

What am I misunderstanding about password hashing?

Asked 2017-Feb-21 at 13:26

It is my understanding that a hash function will always return the same results when fed the same data. But I've been using libsodium (via node-sodium) and that is not what is happening.

I have this in my schema:

...

ANSWER

Answered 2017-Feb-21 at 12:57

As the name alludes, the output is salted. This means that a random string was added to the password before hashing, and also included in the output value separately.

The purpose of this is to defeat dictionary attacks. By adding a random string to each password before hashing, you ensure that the same password will hash differently, forcing the attacker to crack every password separately.

Source https://stackoverflow.com/questions/42367551

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install node-sodium

Tested on Mac, Linux, Windows and IllumOS Systems. node-sodium depends on libsodium, so if libsodium does not compile on your platform chances are npm install sodium will fail.
Windows installs will automatically attempt to download LibSodium binary distribution, and include files, from my repo. You MUST set the msvs_version npm config variable to the appropriate Microsoft Visual Studio version you have installed before you run npm install on Windows.
Node Sodium includes the source of libsodium, so the normal install will try to compile libsodium directly from source, using libsodium's own build tools. This is the prefered method of compiling node sodium. If you can't compile libsodium from source in your platform you can download a pre-compiled binary and copy the libsodium.* library files to ./deps/build/lib folder. and copy all the include files to ./deps/build/include.

Support

Please read the work in progress documentation found under docs/. You should also review the unit tests as most of the high level API is "documented" there. Don't forget to check out the examples as well. The low level libsodium API documentation is now complete. All ported functions have been documented in low-level-api.md with code examples. Please be patient as I document the rest of the APIs, or better still: help out! :).

Find more information at: