Secure Client for exposing TLS (aka SSL) secured services as plain-text connections locally, and for multiplexing a single port with multiple protocols using SNI
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
AJ ONeal 224d005a90 v1.0.0: first working version 1 year ago
LICENSE v1.0.0: first working version 1 year ago
README.md v1.0.0: first working version 1 year ago
sclient-cli.go v1.0.0: first working version 1 year ago
sclient.go v1.0.0: first working version 1 year ago

README.md

sclient.go

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] telebit.cloud:443 <= localhost:3000

Connect via Telnet

$ telnet localhost 3000

Connect via netcat (nc)

$ nc localhost 3000

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

Install

macOS, Linux, Windows

For the moment you’ll have to install go and compile sclient yourself:

git clone
go build sclient*.go
rsync -av sclient-cli /usr/local/bin/sclient
go run sclient*.go 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