How do you hope to convince sys-admins to install this? I work with clusters where I do not have superuser access, so this is a no go for me.

▲

greaber a day ago | parent [-]

It just installs in $HOME/.local/bin by default (and some other parts go in other locations inside your home directory). You don't need superuser access for anything. The first time you connect to a server, it installs its matching counterpart in your home directory on the server.

▲

ProphetOfParado 21 hours ago | parent | next [-]

Ah, that's nice!

▲

unsnap_biceps a day ago | parent | prev [-]

Honestly, that's even scarier for an untrusted/low trusted tool...

▲

cstrahan a day ago | parent [-]

What is it about a tool, running as your own non-root user, installed in your home directory, that makes it scary?

	▲	unsnap_biceps 6 hours ago \| parent [-]
		Let's say this is widely used and let's presume that a specific version has a security issue. With everyone having their own copy of the binary on every host versioned at the time they first ran a command on that host, or any decently sized fleet, it'll take a big effort to track down and ensure all versions have been updated or removed (to be re-generated later). Frankly, we would re-kick our fleet ahead of schedule rather then try to remediate it more manually. But we re-kick our fleet on a rotating yearly schedule, so it's not too much an effort to re-kick it earlier. It's a completely automated system in place now.