Yea, worked in ID for a good bit of time, this is great stuff.

ZFS. Since it backs up at block level, moving giant files means you onoy send a few K for the backup, unlike other solutions like rsync, etc.

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

I use a dual NIC mini PC running OpnSense. Ot would support USB sims. I actually have two of the routers connected woth a network cable. If one goes down, the other takes over.

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.

Frame it. Neato.

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.

Old news, but time for Jellyfin. I made the switch a couple months ago. Some minor teething issues, but better, IMO, especially now as my family all have LDAP users and that just works.

None of that is illegal. He states he purchased the media. And it’s certainly not harmful content.

Yes? There are Lemmy clients that are open source, for instance. And the Wireguard client is.

Granted this is not Headscale’s fault, they’re just using Tailscale clients. Either way I’m glad I use a roll-your-own Wireguard.

I and my partner also don’t use those OSs, but it’s more the point of using FOSS when we can.

Yea, but in iOS?