Possibly linux to Sysadmin@lemmy.worldEnglish · 1 year agoYou have a organizational identity right?imagemessage-square39fedilinkarrow-up1338arrow-down122
arrow-up1316arrow-down1imageYou have a organizational identity right?Possibly linux to Sysadmin@lemmy.worldEnglish · 1 year agomessage-square39fedilink
minus-squarenickwitha_k (he/him)@lemmy.sdf.orglinkfedilinkarrow-up10arrow-down15·1 year agoSo is using “pass” as the password to all of your sensitive systems. Still not best, or even good practice.
minus-squareJWBananas@startrek.websitelinkfedilinkEnglisharrow-up19arrow-down1·1 year agoAre you conflating self-signed and untrusted? Self-signed is fine if you have a trusted root deployed across your environment.
minus-squarenickwitha_k (he/him)@lemmy.sdf.orglinkfedilinkarrow-up6arrow-down2·1 year agoCorrect. If using actual pki with a trusted root and private CA, you’re just fine. I took the statement to mean ad-hoc self-signed certs, signed by the server that they are deployed on. That works for EiT but defeats any MitM protection, etc.
So is using “pass” as the password to all of your sensitive systems. Still not best, or even good practice.
Are you conflating self-signed and untrusted?
Self-signed is fine if you have a trusted root deployed across your environment.
Correct. If using actual pki with a trusted root and private CA, you’re just fine.
I took the statement to mean ad-hoc self-signed certs, signed by the server that they are deployed on. That works for EiT but defeats any MitM protection, etc.