170
submitted 3 weeks ago by Mubelotix@jlai.lu to c/selfhosted@lemmy.world
you are viewing a single comment's thread
view the rest of the comments
[-] yannic@lemmy.ca 0 points 2 weeks ago

You've piqued my interest. Where can I read about it?

I did a quick search on their github and came up empty. Maybe no one mentioned "htaccess" in the issue.

[-] quick_snail@feddit.nl 0 points 2 weeks ago* (last edited 2 weeks ago)

Search for "basic auth"

Its the only software project I know of that you can't put behind http basic auth. They mark this bug as "wontfix" every time someone points it out to them

[-] yannic@lemmy.ca 1 points 2 weeks ago

Basic auth? The insecure authentication method?

Ok, I'll look it up anyway. Under the jellyfin repository, there were eight results, none of which seemed to describe what you meant, and under the jellyfin-web repository, there were none. Using a web crawler search, I was able to find Issue #123 for jellyfin-android

Is that it?

[-] quick_snail@feddit.nl 0 points 2 weeks ago* (last edited 2 weeks ago)

Basic auth is very secure.

Unlike custom implemented logins. So it's common to use basic auth in front of custom auth implementations. So even when the app has a login vuln, you're safe.

Yes that ticket is one of many.

Try searching the repo. Make sure to backspace out the prefix that ignores closed tickets.

[-] yannic@lemmy.ca 1 points 1 week ago* (last edited 1 week ago)

That's exactly how I searched. If you want security, it's probably best to follow the Unix philosophy of do one thing and do it well. In other words, don't trust someone building a media server to handle auth and instead use the OIDC or LDAP plugins.

this post was submitted on 01 Apr 2026
170 points (100.0% liked)

Selfhosted

58589 readers
65 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS