anodejs/node-ssltunnel

SSL tunnel for node

node-ssltunnel's Issues

set keepalive of in cli

log with error verbosity on errors

support ANY port (when local port 0 is provided)

connect and end logs should be with same level

remove the commented code on cleartext server keepalive

NPN support

OpenSSL 1.0.1+ ships with Next Protocol Negotiation (NPN) support, which is required for SPDY protocol negotiation.

node-spdy supports this already, but it would be great to have this support baked right into node-ssltunnel and then deliver the frames over a regular TCP stream.

Error is not shown and have error level at log

Using client mode with log level. I am able to get it listening on a port and says it will forward request and most likely i have a cert issue but I can't tell because it reports this back:

Error communicating with the server. Error: {}
connection to server was closed

I need more info if possible

"node run_ssltunnel.js ..." encounter error

hi.

node run_ssltunnel.js --role client --proxy_port 54080 --server_port 64443 --server_host my-vps-ip --srv_pub_cert ~/node_modules/ssltunnel/gen-certs/server-public.pem --clt_pub_cert ~/node_modules/ssltunnel/gen-certs/client-public.pem --clt_prv_cert ~/node_modules/ssltunnel/gen-certs/client-private.pem
Running 'client' role. Listening on 54080, encrypting and forwarding to ssltunnel's server on my-vps-ip:64443
ssltunnel's client is listening on port: 54080

Connected to the real BE server
/Users/brite/node_modules/ssltunnel/lib/ssltunnel.js:141
log.info('Error communicating with the server. Error: ' + JSON.stringify(exception));
^

TypeError: Converting circular structure to JSON
--> starting at object with constructor 'Object'
--- property 'issuerCertificate' closes the circle
at JSON.stringify ()
at TLSSocket. (/Users/brite/node_modules/ssltunnel/lib/ssltunnel.js:141:70)
at TLSSocket.emit (events.js:208:15)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at processTicksAndRejections (internal/process/task_queues.js:77:11)

how to fix it?

occasional crash on crypto stream

tls.js:96
throw new Error('CryptoStream is not writable');
^
Error: CryptoStream is not writable
at CleartextStream.write (tls.js:96:11)
at Socket. (C:\Users\dimast.MIDDLEEAST\node_modules\ssltunnel\lib\ssltunnel.js:82:27)
at Socket.emit (events.js:67:17)
at TCP.onread (net.js:347:14)