3 ms·
Copying your bash-profile is good as long as soon as you're _the_ user on that server, or when you have separate users for all users of the server. At my work,
by jwandborg 9y ago
Copying your bash-profile is good as long as soon as you're _the_ user on that server, or when you have separate users for all users of the server.
At my work, we all use the same user for ssh (uid 1000), for all servers, for all projects. It's a good opportunity to exercise mode-switching when switching from (local) fish to (remote) bash and back again, and I'm happy both of fish, bash share the common readline bindings, it also makes it clear what kind of shell you're in if you're jumping back and forth between docs, manpages and shells.
I have one itch, fish and bash do word-boundaries differently when deleting with Ctrl-W (delete word). bash even does word-boundaries different from Ctrl-W when using Meta-D (delete word in front).
- hnlmorg 9y agoI don't know your specific set up so I don't want to come across as preachy but it's not generally good practice to have everyone using the same UID. I know for a fact we would fail our regular PCI and gambling commission audits if we did that but even for businesses that don't need that kind of regulation, sharing a UID means you're sharing passwords / private keys which seems a major security breach just waiting to happen (eg what happens when someone leaves the team?)
- irishsultan 9y agoYou don't need to share private keys or passwords to share a UID, each person can have his or her own public key in .ssh/authorized_keys Of course I agree that this is still bad practice from an auditing perspective (and assuming a password is needed to su/sudo you do need to share that password).
- hnlmorg 9y agoGood point about authorized_keys, I'd forgotten about that.