sshing

If you are SSHing into a container, interrogating the version, and upgrading it manually, you're doing it wrong.

Daily work involved SSHing into the production box and editing the PHP code in vim.

SSHing into the production box and running a repl in the SSH terminal.

How should we think about the security story when sshing from a more trusted to a less trusted host?

SSHing into a Windows box with file shares open to other hosts is...

But right now I can do all my regular dev tasks on the iPhone by SSHing in my webserver.

This is especially true when I am SSHing into a server much more powerful than than my MacBook or Linux laptops.

BTW Running my own name server has solved a lot of weird slowdowns I used to experience when browsing the web or sshing.

I have also been sshing into my Linode so maybe that's cheating.

Almost everything is done remotely, sshing into the dev VM and running emacs there, the only exception being java stuff.

So if you don't create your function, SSHing to the friend's Mac and typing 'say whatever you want' will have an interesting but probably not desired effect:) I'll admit to having used this on a friend's machine once or twice for amusement.

I've not figured out how to run a cluster without giving myself through one of my workstations or a jump box or something ssh access to all of them, so I'm generally okay with a program that automates some of that SSHing I do, like ansible; far more comfortable than I am with a box that is running some monitoring web frontend having any kind of access to my backend servers.