volschin / node-curve25519 Goto Github PK

View Code? Open in Web Editor NEW

This project forked from thejh/node-curve25519

6.0 4.0 12.0 341 KB

This is a binding to the curve25519-donna library for node.

License: Other

Python 1.58% C 87.92% JavaScript 7.46% C++ 3.05%

cryptography curve25519 hap node bindings

node-curve25519's Introduction

node-curve25519

This is a binding to the curve25519-donna library for node. Usage:

const curve = require('curve25519-n');

Methods

`curve.makeSecretKey(secret)`

Returns a Buffer.

`curve.derivePublicKey(secret)`

Provide it with your secret key as a 32-bytes-long Buffer and get a Buffer containing your public key as the result.

`curve.deriveSharedSecret(mysecret, hispublic)`

Derive your shared secret with someone else by giving this function two 32-bytes-long buffers containing your secret key and the other persons public key. Returns a Buffer.

Installing

npm i -S curve25519-n or yarn add curve25519-n.

Testing

yarn test

node-curve25519's People

Contributors

Stargazers

Watchers

Forkers

khaost sagyeli zilverline mystk pdlove hobbyquaker evaluation-alex aarctb scottnonnenberg-signal sjdonado felther brunohcastro

node-curve25519's Issues

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml
The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

stack Error: Can't find Python executable "python", you can set the PYTHON env variable

I am using Windows 7 OS with
$ node -v
v10.15.3
when I am trying to install node-curve25519. I am getting below error.

unable to install node-curve25519 globally (npm install -g)

Hello,
i'm trying to install your package globally with command
npm install curve25519-n -g

but no matter what i'm doing i'm getting errors like this:

gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/lib/node_modules/curve25519-n/.node-gyp/8.11.1"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/lib/node_modules/curve25519-n/.node-gyp"
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/lib/node_modules/curve25519-n/.node-gyp/8.11.1"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/lib/node_modules/curve25519-n/.node-gyp"

and at same time, without -g(e.g. in root home directory or in user's home directory) package always installs successfully.

my env:
ubuntu 16.04/nodejs 8.11.1/npm 5.6.0

No compatibility with nodejs v12

At the moment the travis ci build with the newly integrated nodejs v12 fails and need to be further investigated. Don't update to v12 until the problem ist solved.

Fails to install on Debian testing

I am trying to build Signal-Desktop on Debian testing, and (I think) this package fails to build (but I know next to nothing about npm so if my analysis is wrong here please tell me):

error /home/r/src/android/Signal-Desktop/node_modules/curve25519-n: Command failed.
Exit code: 1
Command: node-gyp rebuild
Arguments: 
Directory: /home/r/src/android/Signal-Desktop/node_modules/curve25519-n
Output:
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp info find Python using Python version 2.7.18 found at "/usr/bin/python"
gyp info spawn /usr/bin/python
gyp info spawn args [
gyp info spawn args   '/usr/share/nodejs/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/r/src/android/Signal-Desktop/node_modules/curve25519-n/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/share/nodejs/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/include/nodejs/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/usr/include/nodejs',
gyp info spawn args   '-Dnode_gyp_dir=/usr/share/nodejs/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/usr/include/nodejs/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/home/r/src/android/Signal-Desktop/node_modules/curve25519-n',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
Traceback (most recent call last):
  File "/usr/share/nodejs/node-gyp/gyp/gyp_main.py", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3251, in <module>
    @_call_aside
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3235, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3264, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 583, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 900, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 786, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'gyp==0.1' distribution was not found and is required by the application
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/share/nodejs/node-gyp/lib/configure.js:355:16)
gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Linux 5.6.13
gyp ERR! command "/usr/bin/node" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /home/r/src/android/Signal-Desktop/node_modules/curve25519-n

My guess is that the problem has to do with something here using legacy Python 2. I have the "gyp" and "node-gyp" packages installed, but "gyp" depends on "python3-pkg-resources" and I had to install the Python 2 version python-pkg-resources to even get this far (I got a different error message before).

Is there anything I can do to still build Signal-Desktop? Which component needs to be updated to stop using an unsupported old Python version?

An in-range update of nan is breaking the build 🚨

The dependency nan was updated from `2.13.2` to `2.14.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

nan is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 11 commits.

1dcc61b 2.14.0
36f4db8 Prepare for 2.14.0
d105809 add electron to travis test matrix (#848)
4e96248 Add missing methods to Nan::Maybe (#852)
8b2b384 Merge pull request #855 from 0xflotus/master
87c5f4e Merge pull request #2 from 0xflotus/patch-2
6487f2b Update asyncworker.md
2337191 Merge pull request #1 from 0xflotus/patch-1
58b87c7 Update README.md
e512f92 Add node 12 support
3bd8b1b Remove sudo: false from .travis.yml (#847)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

The automated release is failing 🚨

🚨 The automated release from the `master` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀