Show HN: Shittp – Volatile Dotfiles over SSH

https://github.com/FOBshippingpoint/shittp

by sdovan1 • 7 months ago

136 85 7 months ago

sdovan14• 7 months ago

I often need to login to colleagues' machines at work, but I find that their settings are not what I am familiar with. So I wrote an SSH wrapper in POSIX shell which tars dotfiles into a base64 string, passes it to SSH, and decodes / setups on the remote temp directory. Automatically remove when session ends.

Supported: .profile, .vimrc, .bashrc, .tmux.conf, etc.

This idea comes from kyrat[1]; passing files via a base64 string is a really cool approach.

[1] https://github.com/fsquillace/kyrat/

amelius• 7 months ago

Ok, but what if your colleague does not have Vim installed?

Wouldn't it make more sense to have a tool that brings files over to the local computer, starts Vim on them, and then copies them back?

Joker_vD5• 7 months ago

That starts to sound like using VS Code in remote mode.

QuinnyPig• 7 months ago

I can’t recall encountering a system in the last 15 years that didn’t have vim (or at least vi for esoteric things) on it.

sdovan14• 7 months ago

We usually work on the VM with daily-built ISO. For example, I would compile and upload Java program to the frontend team member's VM, and type "srt" for "systemctl restart tomcat."

Joker_vD5• 7 months ago

   scp my-precious-dotfiles remote:~
   trap 'ssh remote rm my-precious-dotfiles' EXIT
   ssh remote

Or you can even bake the trap into the remote bash's invocation, although that'd be a bit harder.

stephenlf• 7 months ago

That overwrites the remote dotfiles. Any workarounds?

alsetmusic• 7 months ago

I came across something similar a few months ago. I pieced together a working hybrid by patching in parts from an older release with the latest version. I didn't ever work out if the latest version failed because of something in my environment or not, but I'm on a Mac fwiw.

https://github.com/cdown/sshrc

xuhu• 7 months ago

How much time does it add when running e.g. "shittp user@lan-host uname" ?

fragmede• 7 months ago

I often need to login to colleagues' machines at work, but I find that their settings are not what I am familiar with

I'd hate to jump to conclusions, but what username are you looking into what machines with for that to be an issue?

tensegrist2• 7 months ago

time to call the it team at work (on the phone) to ask them to add a new item to the software allowlist

grepfru_it6• 7 months ago

Be careful, this will force your defaults over system defaults possibly overriding compliance or security settings. There are a few places I noticed where well-placed malware could hop in etc.

It’s not bad software, it’s also not mature. I’m currently on a phone and on vacation so this is the extent of my review. Maybe I’ll circle back around with some PRs next week

tensegrist2• 7 months ago

i was merely joking about the name apparently being intended to be pronounced in a rather juvenile manner

Y_Y3• 7 months ago

  tmp="$(mktemp -d)" && rsync -a --exclude='.ssh' user@host:~/.[!.]* "$tmp"/ && HOME="$tmp" exec "$SHELL"

imiric• 7 months ago

I use something similar.

It's surprising to me how many projects can be replaced with just a line or two of shell script. This project is a slightly more sophisticated shell script that exposes a friendlier UI, but I don't see why it's needed when the alternative is much simpler, considering the target audience.

grepfru_it6• 7 months ago

I think this will copy your 9gb Mozilla cache directory as well? Still one liners like this is all you need lol

sigwinch5• 7 months ago

Any sufficiently-advanced automated rsync would have a filter for caches.

Bender3• 7 months ago

My mozilla cache would be under ~/.mozilla/firefox. Is the nightly version moving to ~/.config?

Reason I say would be is that I disable disk cache among other things performed by Arkenfox [1]

[1] https://github.com/arkenfox/user.js

sdovan14• 7 months ago

Overriding HOME variable is neat! Make things much easier.

flakes• 7 months ago

I do the same, but I skip rsync for git.

    git clone $uri dotfiles; export HOME=$(pwd)/dotfiles

These days, my laptop acts as a dumb SSH gateway for Linux VMs. No configuration or setup, aside from VS code connecting to VMs. Any server that I would want to load my dotfiles onto will almost always have git installed.

Rant (not directed at any comment here): If it's a production server without git, then please do not run scripts like this. Do not create junk directories on (or ideally any modifications to) secure machines. It inevitably causes new and uninteresting puzzles for your colleagues. Create documented workflows for incident responses or inspection.

twp• 7 months ago

chezmoi has similar functionality, but it does install a binary on the target machine:

https://www.chezmoi.io/reference/commands/ssh/

thunderbong• 7 months ago

Is this similar to sshrc?

https://github.com/cdown/sshrc

K0IN• 7 months ago

Maybe also kind of related xxh

https://github.com/xxh/xxh

goku125• 7 months ago

How about mounting your dotfiles directory (~/.config) or even your entire home directory on the remote system using SSHFS or NFS? I'm sure somebody would have tried it or some project may already exist. Any idea why that isn't as prevalent as copying your dotfiles over?

vbernat2• 7 months ago

This would enable a lot of attacks.

goku125• 7 months ago

Could you elaborate?

sigwinch5• 7 months ago

I’m trying to imagine why sshfs mounting the less-capable remote onto the workstation would be blocked.

cl3misch• 7 months ago

That requires the remote machine to be configured to SSH into your local machine. In the scenario where OP's project is useful (SSH to foreign machines) I might not want that.

On the other hand, if the remote machine is mine, it will have my config anyway.

goku125• 7 months ago

There should be some way to mount a local directory onto a remote system without requiring the remote system to log in to the local system. SSH provides a secure bidirectional communication channel between the two systems. While we normally use sshfs to mount a remote directory to the local system, why should the reverse be impossible? Besides, you could also use NFS over SSH or TLS.

qudat• 7 months ago

I have a dotfiles git repo that symlinks my dotfiles. Then I can either pull the repo down on remote machine or rsync. I’m not sure why I would pick this over a git repo with a dotfiles.sh script

https://erock-git-dotfiles.pgs.sh/tree/main/item/dotfiles.sh...

montroser2• 7 months ago

This is for when you have to ssh into some machine that's not yours, in order to do debugging or troubleshooting -- and you need your precious dotfiles while you're in there, but it would be not nice to scatter your config and leave it as a surprise for the next person.

This installs into temp dirs and cleans it all up when you disconnect.

Personally, my old-man solution to this problem is different: always roll with defaults even if you don't like them, and don't use aliases. Not for everyone, but I can ssh into any random box and not be flailing about.

Even with OP's neat solution, it's not really going to work when you have to go through a jump box, or have to connect with a serial connection or some enterprise audit loggable ssh wrapper, etc

Y_Y3• 7 months ago

There's definitely something be said for speaking the common tongue, and being able to use the defaults when it's necessary. I have some nice customisations, but make a point of not becoming depwndent on them because I'm so often not in my own environment.

On the other hand, your comment has me wondering if ssh-agent could be abused to drag your config along between jump hosts and enterprise nonsense, like ti does forwarding of keys.

cyanf• 7 months ago

Why would you want to ssh into a machine that's not yours? That's a violation of the Computer Frauds and Abuse Act, up to 10 years in prison!

throw2772• 7 months ago

This reminds me - in a previous company I worked at, we had a bunch of old firewalls and switches that ran SSH servers without support for modern key exchange algorithms etc

One of the engineers wrote a shell alias called “shitssh”, which would call ssh with the right options to allow the old crufty crypto algorithms to be used. This alias got passed down to new members of the team like a family heirloom.

psd1• 7 months ago

Nice, although wouldn't work today. Modern distros (ime, fedora 42) need you to update policy and reboot. You can't connect with just --key-exchange YOLO1 any more

I hate network vendors. Wish I could put BSD on my old Catalysts.

est2• 7 months ago

I wonder why are dofiles have to be on remote machines?

e.g. I type an alias, the ssh client expands it on my local machine and send complex commands to remote. Could this be possible?

I suppose a special shell could make it work.

minitech• 7 months ago

I suppose a special shell could make it work.

Working on it! :)

Remote machines usually don’t need to know your keystrokes or handle your line editing, either. There’s a lot of latency to cut out, local customization to preserve, and protocol simplification to be had.

Joker_vD5• 7 months ago

I wonder why are dofiles have to be on remote machines?

Because the processes that use them run on the remote machines.

I type an alias, the ssh client expands it on my local machine and send complex commands to remote.

This is not how SSH works. It merely takes your keystrokes and sends them to the remote machine, where bash/whatever reads and processes them.

Of course, you can have it work the way you imagine, it's just that it'd require a very special shell on your local machine, and a whole RAT client on the remote machine, which your special shell should be intimately aware about. E.g. TAB-completion of files would involve asking the remote machine to send the dir contents to your shell, and if your alias includes a process substitution... where should that process run?

est2• 7 months ago

the processes that use them run on the remote

Yes but but does the process have to read from a file system dotfile, instead of some data fetched over a ssh connection?

your alias includes a process substitution

Very valid point. How about a special shell only provides sys calls and process substitution on remote, the rest runs on local client, and communicate via ssh?

I understand this will make client "fat" but it's way more portable.

drewr• 7 months ago

I didn't look closely at the project, but why take the extra step of base64? I do this all the time with tar by itself and it's wire-proof enough to work fine.

owl_vision• 7 months ago

something like this, i recon:

  $ tar cf - ~/.shrc | ssh target '(cd ~ && tar xf -)'

sigwinch5• 7 months ago

In some cases, shar would be a useful wrapper for that.

neocron• 7 months ago

I don't know, I just use the standard on my machine or on remote. Why bother to customize it all the time when you can't work without the customizations

darrenf• 7 months ago

For kitty users, see also https://sw.kovidgoyal.net/kitty/kittens/ssh/

foltik2• 7 months ago

I have a python script [0] which builds and statically links my toolbox (fish, neovim, tmux, rg/fd/sd, etc.) into a self contained —-prefix which can be rsynced to any machine.

It has an activate script which sets PATH, XDG_CONFIG_HOME, XDG_DATA_HOME, and friends. This way everything runs out of that single dir and doesn’t pollute the remote.

My ssh RemoteCommand then just checks for and calls the activate script if it exists. I get dropped into a nice shell with all my config and tools wherever I go, without disturbing others’ configs or system packages.

[0] https://github.com/foltik/dots

stijnveken2• 7 months ago

Is this available somewhere? I'm curious to see how this works.

foltik2• 7 months ago

Published a minimal version and added a link! This implements everything I mentioned except for static linking, so YMMV depending on your C/CXX toolchain and installed packages.

throw20251220• 7 months ago

More like shit toilet paper. Name like findtherapist.com

deadbabe• 7 months ago

Why call this Shittp? Is it to imply it’s actually shitty and just a proof of concept or fun project?

yoan9224• 7 months ago

I love the concept but I'd be worried about security in enterprise environments. Some of the dotfiles (especially .bashrc) could override security policies or compliance settings that IT has configured.

That said, for personal servers this is brilliant. I've been using a git repo for dotfiles but having them automatically cleanup on disconnect is clever.

One improvement: consider using SSH's ProxyCommand or LocalCommand instead of wrapping SSH entirely. That way it works transparently with tools that call SSH directly (git, rsync, etc).

Also curious - does this handle tmux sessions properly? I often SSH in, start tmux, disconnect, then reconnect later. Would the dotfiles still be there?

ghostly_s• 7 months ago

People who choose such a noxious name for their project that it actually dissuades people who might otherwise be users think that says something about those prudish users, but it really says something about them.

allarm• 7 months ago

Oh! The horror.

gbraad• 7 months ago

I have been doing something similar for years, especially for login to VMs: sets up an environment of my dotfiles based on a checkout and runs a resumable 'screen' session with tmux. This looks elegant (ephemeral), but I seldom log in to a machine I can't leave my files on as installed.

${HOME} is where your dotfiles are.

5-0• 7 months ago

It's nice to read the different takes on this.

On that note, I didn't see any mention of https://github.com/romkatv/zsh4humans/blob/master/tips.md#ex... , so there.

Show HN: Shittp – Volatile Dotfiles over SSH

Related Stories