I’m not sure I follow the question. All of the TLD *.arpa is not reserved for private use, only *.home.arpa. So all your internal services are required to be a sub domain.

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.

I just use openssl"s built in management. I have scripts that set it up and generate a .lan domain, and instructions for adding it to clients. I could make a repo and writeup if you would like?

As the other commenter pointed out, .lan is not officially sanctioned for local use, but it is not used publicly and is a common choice. However you could use whatever you want.

I use a domain, but for homelab I eventually switched to my own internal CA.

Instead of having to do service.domain.tld it’s nice to do service.lan.

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

Use an LDAP to OIDC bridge?

Either comment OP hasn’t followed the news, or they forgot this was the Fediverse.

I used to do all the things mentioned here. Now, I just use Wireguard. If a family member wants to use a service, they need Wireguard. If they don’t want to install it, they dont get the service.

No I’m not, you’re just hot-swapping between ATProto and BlueSky, cherry picking the best parts of whichever to suit the debate. See: https://lemmy.dbzer0.com/post/47335289/19626444

Sure seems like that’s what you’re doing. Notice how no one is against ATProto. Your post title is about BlueSky, not about ATProto.

We don’t care about the protocol, despite what you think. Your average Lemmy user isn’t on a standards body. We care about the network it facilitates.

Volunteers run the Fediverse, keeping it open. The former Twitter CEO runs BlyeSky. Want to start an actual open network running ATProto? Go for it.

Mastodon is more open than you think.

You made a post to attempt to dispell what you consider a misunderstanding about BlueSky, yet your comment suggests you dont understand the Fediverse.

Well, that problem also exists with mastodon.social

No, it doesn’t. There are thousands of instances, some with hundreds of thousands of users. If you sort the instance list by active users, the population spreads out even more, because smaller instances have more active users.

and a lot of the actual fediverse.

Wrong again. Lemmy.world is about 30% of Lemmy, and less when you include Mbin, PieFed, etc.

Its less distributed, but its still decentralised.

I run a Fedi instance connected to hundreds of others. If one, even a large one, defederates me, it does not cut me off. If I ran a PDS, I’d be connected to BlueSky, and they can do what they want.

You are rationalizing this to yourself because you like BlueSky.

Still is. Always will be.

Actually #2 may be a brain fart for me. I’m probably thinking of the setting in the Arrs that changes file date to release date.

Ahh OK, a Docker bind. 3 things to check:

1. That you added the folders in that weird way Unraod requires, see: https://forum.jellyfin.org/t-solved-jellyfin-not-detecting-media-in-unraid (this probably isn’t it, but worth checking)

2. Make sure for newly added, Jellyfin is configured for Date File Scanned into Library, vs the Created Date on the file

3. Ensure the Arrs aren’t set to change the date on file import. By default they modify created/modified dates to be the release date, which can put things in an unexpected order.

Hmm, shared how? NFS?

https://github.com/SynoCommunity/spksrc/issues/5941 ?

I really wanted Jellyfin working in my DS214Play with DSM6, and I noticed that a package for these evansport CPUs doesn’t exist and it’s officially not supported, so I tried myself and I succeeded.

Frame it. Neato.

Gives them legal standing against scraping for if ot is needed in the future.

How is your underlying file system set up?

Can your router open ports from a hostname vs an IP? If so, clients could run dynamic DNS.

WG client side isn’t really that hard, though. All the fam run WG 24/7 on devices, and only traffic for the internal network goes through it.