▲ 88 ▼ Just created my own zero trust network! (lemmy.world) submitted 1 year ago by HurlingDurling@lemmy.world to c/selfhosted@lemmy.world 52 comments fedilink hide all child comments No awards are needed, just wanted to share my excitement that while my Jellyfin server still keeps loosing my entire library every 24 hours at least now it has a domain and ssl cert! That is all. Happy Friday everyone
[–] dataprolet@lemmy.dbzer0.com -2 points 1 year ago (3 children) Define "insecure". permalink fedilink source parent hideshow 3 child comments replies: [–] sugar_in_your_tea@sh.itjust.works 5 points 1 year ago (2 children) Default passwords, old insecure versions of apps and system packages, etc. "Just getting it working" usually leaves things insecure, and you usually need to take things a step further to secure your publicly accessible services. permalink fedilink source parent hideshow 2 child comments replies: [–] SheeEttin@lemmy.zip 4 points 1 year ago (1 child) Not just old insecure, but current insecure too. Plenty of stuff runs fully current but still vulnerable code. Put it behind a firewall. permalink fedilink source parent hideshow 1 child comment replies: [–] sugar_in_your_tea@sh.itjust.works 4 points 1 year ago Sure. My point is that self-hosters tend to let services sit without updates for months if not years at a time. That's fine if you don't expose anything to the internet, so keep that surface area as limited as possible. permalink fedilink source parent
[–] sugar_in_your_tea@sh.itjust.works 5 points 1 year ago (2 children) Default passwords, old insecure versions of apps and system packages, etc. "Just getting it working" usually leaves things insecure, and you usually need to take things a step further to secure your publicly accessible services. permalink fedilink source parent hideshow 2 child comments replies: [–] SheeEttin@lemmy.zip 4 points 1 year ago (1 child) Not just old insecure, but current insecure too. Plenty of stuff runs fully current but still vulnerable code. Put it behind a firewall. permalink fedilink source parent hideshow 1 child comment replies: [–] sugar_in_your_tea@sh.itjust.works 4 points 1 year ago Sure. My point is that self-hosters tend to let services sit without updates for months if not years at a time. That's fine if you don't expose anything to the internet, so keep that surface area as limited as possible. permalink fedilink source parent
[–] SheeEttin@lemmy.zip 4 points 1 year ago (1 child) Not just old insecure, but current insecure too. Plenty of stuff runs fully current but still vulnerable code. Put it behind a firewall. permalink fedilink source parent hideshow 1 child comment replies: [–] sugar_in_your_tea@sh.itjust.works 4 points 1 year ago Sure. My point is that self-hosters tend to let services sit without updates for months if not years at a time. That's fine if you don't expose anything to the internet, so keep that surface area as limited as possible. permalink fedilink source parent
[–] sugar_in_your_tea@sh.itjust.works 4 points 1 year ago Sure. My point is that self-hosters tend to let services sit without updates for months if not years at a time. That's fine if you don't expose anything to the internet, so keep that surface area as limited as possible. permalink fedilink source parent