The way you currently say it, they tried to stop the exemption. They fought for the law, so OS gets an exemption.

Or do I understand you wrong?

We’ve got my 95 old grandma https://enna.care/ and she can use it. Instead of having to use the touch interface it works by placing cards on to an NFC reader.

What did you do about authentik always loading several seconds before login someone into a service?

One thing Torvalds enforces is not breaking userland. So it shouldn’t be kernel problems. More likely its some other lib that breaks compatibility.

Well, it startend with conduit. That was a respectable name. The development slowed down and someone wasnt happy abput not getting pr merged. Then it got forked to conduwuit.

Speed picked back up. There was later a massive meltdown for some reason. To successors emerged continuwuity and tuwunel.

Its also not the first pig cycle in the memory industry. There used to be over 20 manufacturers producing ram. These three survived because they didn’t massively ramp up production when demand increased. So they’ve collectively said, we are not really investing into production.

Oh I missed that. Oh no. Rolling your own crypto, surely nothing can go wrong.

For a discord or Telegramm alternative it doesnt need to be e2e.

It’s also a lot harder to make money with open source. You would need to find something to offer on top for money. That can be hosting (nextcloud), support (redhat), consultation (hyper) or additional features(zeds AI offering).

In a side node: when building for geentoo it should be possible to build all rust libs as dylib. The compiler only offers a stable abi for the same version and all flags being equal. When building everything yourself that should work at the coat of updating the compiler requiring a complete rebuild of all libs.

I should have been more clear.

I meant for self hosting.

Though realistically, even if the service is provided for the public, you could just use an instance of keycloak or something similar with open registration. That’s what an association I’m close to is doing already.

By default, the Credentials provider does not persist data in the database. However, you can still create and save any data in your database, you just have to provide the necessary logic, eg. to encrypt passwords, add rate-limiting, add password reset functionality, etc.

That is exactly the complexity I wouldn’t want. With just SSO it is enough to send a redirect URL to the browser and on the callback set a cookie. No js needed. If your service gets compromised and someone leeks the credentials, just log everyone out.

If i created a service I would go in the opposit direction. Only offer SSO and no other option.

You loose quite a bit of complexity that way.

You say you are on a budget. Yet you talk about 128 Gigs of ram.

Maybe you should clarify what your budget is.

Its timing based. When piped a script, bash executes each line completly before taking the next line from the input. Curl has a limited output buffer.

1. Operation that takes a long time. Like a sleep, or if you want it less obvious. A download, an unzip operation, apt update, etc.
2. Fill the buffer with more bash commands.
3. Measure on the server if at some point curl stops downloading the script.
4. Serve a malicious payload.

They can even serve a different file for curl vs curl|bash

I think the Problem is the kernel dumping RAM to disk in crash. Potentially containing secrets.

I manage all my services with systems. Simple services like kanidm, that are just a single native executable run baremetal with a different user. More complex Setups like immich or anything that requires a pzthon venv runs from a docker compose file that gets managed by systemd. Each service has its own user and it’s own directory.

If a service doesnt offer Oidc, just dont self host it. The SSO service can then be properly secured and even if its only a password, at least its not reused.

Careful. Not every fascist is a nazi. From what I can tell he is only the former and not the latter.