HN user

seymon

76 karma

meet.hn/city/de-Karlsruhe

Socials: - seymon.at.hn

---

Posts4
Comments34
View on HN

Using something like this for centralized authorization across services works well for binary access control decisions.

But the problem that remains is "authorized search" in an efficient way. Asking permify what resources a user can access and then query the app postgres db with "WHERE resource_id IN ( {list}, {with}, {many}, {IDs}, ... )" does not scale well. How to solve this?

What's considered nowadays the best practice (in terms of security) for running selfhosted workloads with containers? Daemon less, unprivileged podman containers?

And maybe updating container images with a mechanism similar to renovate with "minimumReleaseTime=7days" or something similar!?

Nostr 10 months ago

Is there any concept of private key rotation or something else? In case a client with a nostr key on it got compromised or something similar? With a traditional password passed logins I would just set a new password from another machine. Regeneration of a new nostr key would mean it's a new account isn't it?

Bun v1.0.0 3 years ago

Has anyone managed to run a non trivial Nest.js application with bun already?

With non trivial I mean an application using a lot of Nest.js features and libraries like TypeORM, Swagger-UI.

One thing I find difficult using access control systems as a distributed service like Zanzibar is a convenient and performant way to search and filter resource data using permissions. For example defining database queries that should only return resources a subject has access to based on Zanzibar permissions.

Materialistic Android App. Unfortunately it is not anymore in the Google Play Store. It's the best hackernews android app in my opinion. What android app do you use?

I which all the keycloak login and email themes would be more flexible and could use custom client attributes, realm settings etc.

Another missing thing is multi tenancy within a realm. Because managing a huge number of realms is a configuration nightmare.