Secure Client for node.js. Connect to a secure service via TLS (aka SSL). Also enables multiplexing a single port with multiple protocols via SNI. https://telebit.cloud/sclient
Go to file
AJ ONeal f14708495a v1.0.4: typo fix in docs and cURL example 2018-08-06 17:36:07 -06:00
bin v1.0.0: initial release 2018-08-06 12:27:33 -06:00
LICENSE v1.0.0: initial release 2018-08-06 12:27:33 -06:00
README.md v1.0.4: typo fix in docs and cURL example 2018-08-06 17:36:07 -06:00
index.js v1.0.0: initial release 2018-08-06 12:27:33 -06:00
package.json v1.0.4: typo fix in docs and cURL example 2018-08-06 17:36:07 -06:00

README.md

sclient.js

Secure Client for exposing TLS (aka SSL) secured services as plain-text connections locally.

Also ideal for multiplexing a single port with multiple protocols using SNI.

Unwrap a TLS connection:

$ sclient whatever.com:443 localhost:3000
> [listening] whatever.com:443 <= localhost:3000

Connect via Telnet

$ telnet localhost 3000

Connect via netcat (nc)

$ nc localhost 3000

cURL

$ curl http://localhost:3000 -H 'Host: whatever.com'

A poor man's (or Windows user's) makeshift replacement for openssl s_client, stunnel, or socat.

Install

macOS, Linux, Windows

First download and install the current version of node.js

npm install -g sclient
npx sclient example.com:443 localhost:3000

Usage

sclient <remote> <local> [-k | --insecure]
  • remote
    • must have servername (i.e. example.com)
    • port is optional (default is 443)
  • local
    • address is optional (default is localhost)
    • must have port (i.e. 3000)

Examples

Bridge between telebit.cloud and local port 3000.

sclient telebit.cloud 3000

Same as above, but more explicit

sclient telebit.cloud:443 localhost:3000

Ignore a bad TLS/SSL/HTTPS certificate and connect anyway.

sclient badtls.telebit.cloud:443 localhost:3000 -k