Sandal6823@sh.itjust.works to Linux@lemmy.ml · edit-24 days agoWhy disable ssh login with root on a server if I only log in with keys, not password?message-squaremessage-square81fedilinkarrow-up1104arrow-down15file-text
arrow-up199arrow-down1message-squareWhy disable ssh login with root on a server if I only log in with keys, not password?Sandal6823@sh.itjust.works to Linux@lemmy.ml · edit-24 days agomessage-square81fedilinkfile-text
On a server I have a public key auth only for root account. Is there any point of logging in with a different account?
minus-squareWheelchairArtist@lemmy.worldlinkfedilinkarrow-up3·4 days agothat’s why root owns my .bash* stuff
minus-squareSavvyWolf@pawb.sociallinkfedilinkEnglisharrow-up1arrow-down1·4 days agoI don’t think that actually works; the attacker could just remove .bashrc and create a new file with the same name.
minus-square2ndSkin@sh.itjust.workslinkfedilinkarrow-up6arrow-down2·4 days agoIf the .bashrc is immutable, the attacker can’t remove it. That’s how it works.
minus-squareSavvyWolf@pawb.sociallinkfedilinkEnglisharrow-up2arrow-down2·3 days agoThe home directory would need to be immutable, not bashrc.
minus-square2ndSkin@sh.itjust.workslinkfedilinkarrow-up4·edit-23 days ago? It’s .bashrc, not bashrc, and .bashrc is in the home directory. If .bashrc is immutable, it can’t be removed from home.
minus-squareSavvyWolf@pawb.sociallinkfedilinkEnglisharrow-up1·3 days agoIt’s the directory that needs to be writable to delete files, not the file itself. Although the immutable bit (if that’s what you’re talking about - I thought you meant unsetting the write bit) might change that, I’m not sure.
minus-squareWheelchairArtist@lemmy.worldlinkfedilinkarrow-up2arrow-down1·4 days agoyou’re right. that’s something i wanted to look into. guess setfacl would do the trick?
minus-squareMagiilaro@feddit.orglinkfedilinkarrow-up2·3 days ago“chattr +i” is what I use to make things immutable
that’s why root owns my .bash* stuff
I don’t think that actually works; the attacker could just remove .bashrc and create a new file with the same name.
If the .bashrc is immutable, the attacker can’t remove it.
That’s how it works.
The home directory would need to be immutable, not bashrc.
?
It’s .bashrc, not bashrc, and .bashrc is in the home directory.
If .bashrc is immutable, it can’t be removed from home.
It’s the directory that needs to be writable to delete files, not the file itself.
Although the immutable bit (if that’s what you’re talking about - I thought you meant unsetting the write bit) might change that, I’m not sure.
you’re right. that’s something i wanted to look into. guess setfacl would do the trick?
“chattr +i” is what I use to make things immutable
thanks
deleted by creator