Use an LDAP to OIDC bridge?
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.
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.
Yea but with the recent news (see his Mastodon) he’s looking for other vendors.
FP would be a good choice for Graphene.
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.
This is a vegan server, not distro.
You can’t follow a post. Making the project am actor lowers the amount of federated data. If a user was an actor and you wanted to federate a project, you’d have to federate all their projects.
Pretty sure that was the author’s intent 😉
Ahh OK, a Docker bind. 3 things to check:
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)
Make sure for newly added, Jellyfin is configured for Date File Scanned into Library, vs the Created Date on the file
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.
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