The time saving of a well filled ~/.ssh/config is impressive, especially once you start juggling ProxyJump hops.
nozzlegear 44 minutes ago [-]
Gotta be jujutsu. I've completely stopped using git and use jj everywhere instead. It works so much better for my workflow.
ddxv 55 minutes ago [-]
ssh and scp just never fails to impress
-J for jumping
-L for port forwarding
-X for pulling remote applications to view on my laptop (waypipe for Wayland)
Adding all those, and ips and whatnot to .ssh/config so I just type:
ssh foo
fragmede 28 minutes ago [-]
setup LocalCommand, in ~/.ssh/config, so your config files get copied to every server you connect to, so you have all your aliases and scripts.
rft 5 minutes ago [-]
I intentionally avoid this, especially if I am not the only one connecting to a server. I see potentially breaking others' expectations for my convenience as a clear downside. Plus there is a level of paranoia there, I might have unintentionally included a credential in some config that gets copied over. That potentially increases the blast radius of a server compromise beyond what is strictly required for that specific server. I might copy over some scripts into a directory not in $PATH, easy enough to add it to my shell session if needed, CTRL+R helps as well.
justsomehnguy 42 minutes ago [-]
user: pranav_tech26
created: 16 hours ago
karma: 7
fragmede 35 minutes ago [-]
...yes?
justsomehnguy 28 minutes ago [-]
No.
EDIT: also check their comment history.
fragmede 6 minutes ago [-]
Would you mind just saying what you mean?
rhysha 4 hours ago [-]
bearer-cli for static application security testing
The time saving of a well filled ~/.ssh/config is impressive, especially once you start juggling ProxyJump hops.
-J for jumping -L for port forwarding -X for pulling remote applications to view on my laptop (waypipe for Wayland)
Adding all those, and ips and whatnot to .ssh/config so I just type:
ssh foo
EDIT: also check their comment history.