I hate any company that uses or builds AI to screen out hires so, so much. Tagging metadata is OK, but filtering is just evil (am/have been a hiring manager).

The company also added that it’s instituting a bug bounty program to better catch security vulnerabilities in the future. “We do not take this matter lightly, even though it was resolved swiftly and effectively,”

I also hate it more that I can’t hate them for doing the right thing.

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.

Everyone is waiting for this. There needs to be a party.

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.

Agreed, and unfortunately articles like this are food for CEOs to do more under the guise of AI. “See, it works!”

I’m still running Qwen32b-coder on a Mac mini. Works great, a little slow, but fine.

Yea I just hit 2k hours. I don’t play a ton but have been playing forever and am now hearing Rematch may be a good secondary.

Were you a Rocket League player by chance?

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?

It will have had to. Many of the most common from pre 2012 are not allowed at banks. And no 4 consecutive digits are.

Except no dates. This chart is soooooo old.

Using the same digit 4 times is no longer allowed most places, but this chart shows them being pretty popular.

This chart has no sourcing or date associated. Is it old?

Edit: Yes, it is. Here is the excellent source article: http://www.datagenetics.com/blog/september32012/

So it’s from 2012, and used historic breach data from years before then.

In other words, this chart is wholly inacurate now.

Tagging those discussing similar: @Rivalarrival@lemmy.today @codfishjoe@lemmy.world

Make a dummy Google Account, and log into it when on the VPN. Having an ad history avoids the blocks usually. (Note: only do this if your browsing is not activist related/etc)

Also, if it’s image captchas that never end, switch to the accessibility option for the captcha.

What exactly is multi-community? It’s not defined above and the PR has no description.

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