Technology

38472 readers

304 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 3 years ago

MODERATORS

alyaza@beehaw.org

TheRtRevKaiser@beehaw.org

gyrfalcon@beehaw.org

rs5th@beehaw.org

SemioticStandard@beehaw.org

TheRtRevKaiser@kbin.social

coldredlight@beehaw.org

remington@beehaw.org

230

I don't know who needs to hear this, but DO NOT EVER expose Jellyfin to the internet (github.com)

submitted 5 days ago by Scary_le_Poo@beehaw.org to c/technology@beehaw.org

172 comments fedilink hide all child comments

Collection of potential security issues in Jellyfin This is a non exhaustive list of potential security issues found in Jellyfin. Some of these might cause controversy. Some of these are design fla...

(page 2) 50 comments

sorted by: hot top controversial new old

[–] KingThrillgore@lemmy.ml 4 points 4 days ago

Use a VPN

[–] walden@sub.wetshaving.social 8 points 5 days ago (17 children)

I'm not smart, can you tell me if having it behind a reverse proxy with certs and everything fixes any of these flaws?

[–] Mora@pawb.social 11 points 5 days ago

Not really, no. These are application flaws. Caddy will happily do its job and just let bad actors abuse them. (Unless you mean mTLS certs, then Caddy would only respond to those having a client certificate, which hopefully reduces the number of bad actors to your users😉)

load more comments (16 replies)

load more comments