TLSCLIENT(1)

πŸ“¦ version 1.7, in nixos 26.05, nixpkgs unstable

πŸ’… TLSCLIENT(1) β€” 9front tls client πŸ¦‹

okay bestie, this one is from the General Commands Manual, and it’s giving secure-tunnel realness. let’s get into it πŸ’–

🌸 NAME 🌸

tlsclient β€” the 9front tls client. periodt.

✨ SYNOPSIS ✨

tlsclient [ -bR ] [ -u user ] [ -h host ] [ -a auth ] -p port command...

πŸŽ€ DESCRIPTION πŸŽ€

tlsclient can establish encrypted tls tunnels with 9front tlssrv servers, using p9any to derive pre-shared keys. iconic behavior, honestly πŸ”βœ¨

The -u, -h, and -a flags configure the parameters for authentication. Those same parameters may also be configured through the USER, CPU, and AUTH environment variables respectively. yes, the environment is also invited to the group chat πŸ’…

The command given is executed on the client, with its standard input and output pointing to the output and input of the remote connection. read that wiring carefully, bestie β€” the page says stdin/stdout go to the remote connection’s output/input 🫢

The -R flag changes this behavior, causing the command to be executed on the remote system in a similar fashion to 9front’s rcpu. In this mode, if command is not specified, a rc login shell is used. remote main character energy fr fr 🌈

The -b flag causes tlsclient to fork into the background. bye bestie, you’re running in the background now πŸ’€βœ¨

🫢 flag-by-flag, because clarity is cute 🫢

  • -u user β€” configures the user parameter for authentication. it can also come from USER.
  • -h host β€” configures the host parameter for authentication. it can also come from CPU.
  • -a auth β€” configures the auth parameter for authentication. it can also come from AUTH.
  • -p port β€” the port slot in the required part of the synopsis, sitting right before command....
  • -R β€” runs the command on the remote system, similar to 9front’s rcpu; if no command is given, you get a rc login shell.
  • -b β€” forks tlsclient into the background.
  • -bR β€” both letters show up together in the bracketed synopsis; -b and -R each do their own thing.

πŸ” PASSWORDS πŸ”

By default, tlsclient will ask for the user’s password through getpass(3). classic interactive moment πŸ’–

For non-interactive use, the PASS environment variable may be used to specify the password literal, and TLSCLIENT_ASKPASS may be set to a program that will be executed to provide the password on stdout. very β€œautomation slay” of it 🌟

πŸ’€ BUGS πŸ’€

The lack of factotum and portable namespaces make this password business not fun. and that’s the tea, unfortunately 😭🫢


that’s the whole page, bestie β€” signing off with the TLSCLIENT(1) footer stamp from the General Commands Manual, and no extra source/version/date line on this one πŸŽ€πŸ’œ

πŸ“¦ where this page comes from