• 3 Posts
  • 88 Comments
Joined 2 years ago
cake
Cake day: June 24th, 2023

help-circle

  • No thanks. I get some people agreed to this, but I’m going to continue to use .lan, like so many others. If they ever register .lan for public use, there will be a lot of people pissed off.

    IMO, the only reason not to assign a top-level domain in the RFC is so that some company can make money on it. The authors were from Cisco and Nominum, a DNS company purchased by Akamai, but that doesnt appear to be the reason why. .home and .homenet were proposed, but this is from the mailing list:

    1. we cannot be sure that using .home is consistent with the existing (ab)use
    2. ICANN is in receipt of about a dozen applications for “.home”, and some of those applicants no doubt have deeper pockets than the IETF does should they decide to litigate

    https://mailarchive.ietf.org/arch/msg/homenet/PWl6CANKKAeeMs1kgBP5YPtiCWg/

    So, corporate fear.






  • fmstrat@lemmy.nowsci.comtoSelfhosted@lemmy.worldgoodbye plex
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    5 days ago

    I just validated that the latest version of the LDAP privilege escalation issue is not an issue anymore. The curl script is in the ticket.

    This was the one where a standard user could get plugin credentials, such as the LDAP bind user, and change the LDAP endpoint. I.E., bad.

    I chose this one because after going through all of them, it was the only one that allowed access to something that wasn’t just data in Jellyfin.

    So for me, security is less of an issue knowing that, as only family use the service, and the remaining issues all require a logged in user (hit admin endpoint with user token).

    Plus, I tried a few of those and they were also fixed, just not documented yet. I didn’t add to those tickets because I was not as formal with my testing.

    @EncryptKeeper@lemmy.world