beameio / beame-sdk Goto Github PK

View Code? Open in Web Editor NEW

87.0 87.0 17.0 6.61 MB

HTTPS Server without a public/static IP. TLS Tunnels with decentralized credentials.

Home Page: https://www.beame.io

JavaScript 98.03% Shell 1.17% HTML 0.14% PowerShell 0.38% Makefile 0.28%

beame-sdk's People

Contributors

Stargazers

Watchers

Forkers

shoedog yuliroth zglozman eniac888 gvsurenderreddy elimisteve ralfuhlig maniacs-ops zenit1 alexzxela eiwuert ldenis2 ro9ueadmin lamnot nataliamarzec tenda-dev rn9820

beame-sdk's Issues

Use child_process.execFile instead of child_process.exec

... eliminating potential quoting bugs

Had issue generating sub-sub-domain token

$ beame.js creds getCreds --regToken eyJhdXRoVG9rZW4iOiJ7XCJzaWduZWREYXRhXCI6e1wiY3JlYXRlZF9hdFwiOjE0ODQ3OTQwMjIsXCJ2YWxpZF90aWxsXCI6MTQ4NDc5NDMyMixcImRhdGFcIjpcIntcXFwiZnFkblxcXCI6XFxcImczcjdsN3h5cjk0c3J3cTguZHpjam8zbm5pZnFyc2c4Ny52MS5wLmJlYW1laW8ubmV0XFxcIn1cIn0sXCJzaWduZWRCeVwiOlwiZHpjam8zbm5pZnFyc2c4Ny5wdHh3ZndxejM2NHRwMHdxLnYxLnAuYmVhbWVpby5uZXRcIixcInNpZ25hdHVyZVwiOlwic0M5a20xT3p5TFdCdUk3THJPTDZqSVJjYmU5S1owNzJoMWRpK21STmNSUmswS2dpWFdvNlQ4dk1FclV2UUc1dk4yWHYxd2lNdXR3TnIzOXRjQ3Nhb1hESW9IYVh4RHVkMEVGdUZVazNnYXNZemY0dkVDcDJ2M0dQNHBhUXMvNDdCTE5iN2RFMjBib0ZEWUdtQU45OGNQUWg0RWNTNnBNQzM0N2xLT1VYdW1oNFZKVnV0MFR4Y255VkJ0SVM2dzI0UElnTE1NRUtlWjZ4L3JkOGVhU2d4d2VyZENkdG9TMkY3THpNOWtBWm0xVFRPdEJmMjlQS3lZS3JPZnVPLy9oQW95eHhhUU02UFFKWVgzUlBMWVR6QktIR1lucTg0eUE5dmVNeHFKbUtQUWpiOXVGRU1CUXhJRjZyeGpxaC8zS1BSVVg0SkVRRGRRZ3l0N1RyWHVHOTRRPT1cIn0iLCJuYW1lIjoiemVuYm9va19zdWIiLCJlbWFpbCI6bnVsbCwidHlwZSI6IlJlcXVlc3RXaXRoRnFkbiJ9
[2017-01-18 18:47:20] [BeameStore] INFO: Credential retrieving auth server creds of dzcjo3nnifqrsg87.MY_DOMAIN...
[2017-01-18 18:47:20] [BeameStore] INFO: Signature signed by dzcjo3nnifqrsg87.MY_DOMAIN verified successfully
[2017-01-18 18:47:20] [BeameStore] INFO: Credential auth server creds received for dzcjo3nnifqrsg87.MY_DOMAIN ...
[2017-01-18 18:47:20] [BeameStore] INFO: Credential generating CSR on g3r7l7xyr94srwq8.dzcjo3nnifqrsg87.v1.p.beameio.net...
[2017-01-18 18:47:20] [BeameStore] INFO: Credential CSR for  g3r7l7xyr94srwq8.dzcjo3nnifqrsg87.v1.p.beameio.net created successfully...
[2017-01-18 18:47:20] [BeameStore] INFO: Requesting certificates for credential g3r7l7xyr94srwq8.dzcjo3nnifqrsg87.v1.p.beameio.net ...
[2017-01-18 18:48:23] [BeameStore] ERROR: Cannot insert duplicate key row in object 'dbo.BEAM_Entities' with unique index 'UQ_BeameEntityFqdnSegment'. The duplicate key value is (g3r7l7xyr94srwq8).
The statement has been terminated.
[2017-01-18 18:48:23] [ProvisionApi] FATAL: Cannot insert duplicate key row in object 'dbo.BEAM_Entities' with unique index 'UQ_BeameEntityFqdnSegment'. The duplicate key value is (g3r7l7xyr94srwq8).

src/services/Crypto.js has class CryptoServices

zero level metadata corrupted

Corrupted zero level metadata.json maybe from running the tests
Confirm and fix

test

Using Beame CLI functionality in your own Node.js project

I use a node based secure storage system called solid. It runs locally or on a server using X.509 certificates.

https://github.com/solid/node-solid-server

It does not yet provide a way to tunnel on a home computer or mobile device.

I was wondering if beame sdk could be re-used for this purpose

[CLI] Unclear how I tell beame.js which port to listen on

Or does the created (sub-)domain point to my machine in general, and once once I run the tunnel 8080 http is a specific port specified?

createAtomService missing

are there any atom service for use? according to the sample https://github.com/beameio/beame-sdk/blob/master/example/index.js @ilyash

"beame token validate" displays unrelated error on failure

TypeError: Cannot read property 'signedData' of null

( in beame-sdk/src/cli/token.js:40:24 )

"Provision Api response error" for any network request

[Question] When I register a new token, how am I supposed to know which URL to register with?

Is there one Beame one I'm supposed to use? Is it not ieoateielwkqnbuw.tl5h1ipgobrdqsj6.v1.p.beameio.net? Thanks!

HTTPS servers stalls at [BeameCreds] INFO: Creating edge client for Atom xn...

Previous message:

[BeameServer] INFO: Just created atom with host:xn...

[CLI] Add automated tests for "creds importLiveCredentials"

logger.fatal() should throw an exception

While exiting with non-zero exit code in logger.fatal() is fine for CLI, it's not OK when the code is used as a library.

[CLI] migrate to beame-cli

Eliminate unused arguments
Make per-function settings (some arguments are required for some functions but optional for others)

[CLI] Deduplicate _obj2base64() and move to CommonUtils

[CLI] Add automated tests for "crypto aesEncrypt" and "crypto aesDecrypt"

[CLI] show alt names in "creds list" and "creds show"

test

Suggestion for more intuitive readme

hi guys,

please take a look on my suggestion for more clear README.

Tab comletion for PowerShell

I'm working on this feature

Replace SSL with TLS

It is 2016. SSL is dead. Let's bury it.

s/SSL/TLS/g

Review log files for moving errors to warning or info

Deprecation warning in pem module (node v7.0.0)

node --trace-deprecation beame-insta-ssl create ...
Produces

(node:17427) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
    at makeCallback (fs.js:103:12)
    at Object.fs.unlink (fs.js:979:14)
    at /usr/local/n/versions/node/4.4.0/lib/node_modules/beame-insta-ssl/node_modules/beame-sdk/node_modules/pem/lib/pem.js:1028:16
    at Array.forEach (native)
    at /usr/local/n/versions/node/4.4.0/lib/node_modules/beame-insta-ssl/node_modules/beame-sdk/node_modules/pem/lib/pem.js:1027:15
    at /usr/local/n/versions/node/4.4.0/lib/node_modules/beame-insta-ssl/node_modules/beame-sdk/node_modules/pem/lib/pem.js:939:13
    at testOpenSSLPath (/usr/local/n/versions/node/4.4.0/lib/node_modules/beame-insta-ssl/node_modules/beame-sdk/node_modules/pem/lib/pem.js:1100:9)
    at spawnOpenSSL (/usr/local/n/versions/node/4.4.0/lib/node_modules/beame-insta-ssl/node_modules/beame-sdk/node_modules/pem/lib/pem.js:919:5)
    at spawnWrapper (/usr/local/n/versions/node/4.4.0/lib/node_modules/beame-insta-ssl/node_modules/beame-sdk/node_modules/pem/lib/pem.js:1026:5)
    at execOpenSSL (/usr/local/n/versions/node/4.4.0/lib/node_modules/beame-insta-ssl/node_modules/beame-sdk/node_modules/pem/lib/pem.js:1043:5)

TCP over TLS tunnel using beame-insta-ssl

I don't really get how to do this, if anyone can simplify it. I need to access the server's terminal.
I didn't understand how it was done here https://github.com/beameio/beame-insta-ssl#advanced-tcp-over-tls-tunnel-using-beame-insta-ssl

Changing hostname (fqdn)

Is there any way to change the given hostname ?