hardbyte

ty. I'm pushing opentelemetry metrics which we use for alerting. I had thought about emitting PolicyReports from the operator too

pgroles is a declarative PostgreSQL role manager (YAML in, plan/apply out, CLI or Kubernetes operator). This interactive tutorial walks through a few common Postgres permission errors that you might run into.

You run queries against real PostgreSQL 18 compiled to WASM (PGlite). Building up from early broad grants directly on users in the first section through to abstractions around owners, login roles and roles that scope access.

Hopefully clear I'm not trying to take credit for the upstream work!

Yeah a big motivation for us was avoiding the need to keep another system up to date. Gatehouse basically sits at the execute policy layer, and we let the application code decide how to unify the data (or not).

Oso local authorization looks like a fantastic solution.

You're spot on - we wanted to support some async graph traversal calls similar to the ReBAC example and therefore made the evaluate_access call async. I also wanted to support short circuiting such that somewhat expensive IO calls might be skipped by returning early from a policy that didn't need to make that call.

Nah, I think your intuition is correct it should be broken up.

BYO persistence

Thanks! I'm a big fan of Cedar and DSLs such as CEL and gorules. Hopefully there is a place for a Rust solution as well.

I did put licence = "Apache-2.0" in the Cargo.toml but Partly is okay with it being MIT. Update the repo to explicitly add the license text now. Thanks for the call out

async-friendly Rust native library with decision traceability.

It's particularly useful for detecting issues such as inadvertent IAC changes that can have significant consequences on your cluster's network connectivity and security.

Netchecks has:

* An easy-to-use CLI netcheck for running network checks locally.

* A helm installable operator for Kubernetes: create "NetworkAssertions" to have netchecks periodically ensure your cluster's network conditions are working as specified.

* Monitoring and alerting: integrate with Prometheus and Alertmanager to monitor your network checks' results and receive alerts for any discrepancies.

* Custom validation rules using CEL expressions, allowing you to specify precise conditions for checks to pass or fail.

Check out the project docs at docs.netchecks.io and the code on GitHub: https://github.com/hardbyte/netchecks

I'd love to hear your feedback and suggestions for improvement, so feel free to open issues, contribute.

Stay vigilant!

Even with partially homomorphic encryption and additional "privacy preserving protocols" you can carry out pretty general computation tasks such as machine learning. Have a look at this blog post using the Paillier cryptosystem for a federated linear regression - https://blog.n1analytics.com/distributed-machine-learning-an...

I'm really just writing up what I did so the internet can tell me what I did wrong...

There is another Tensorflow bayesian programming library called Aboleth - https://github.com/data61/aboleth

Confidential Computing Project | Data61, CSIRO | Australia (Visa reqd)

We are developing a platform and product for privacy preserving data analytics – machine learning on data, without seeing the data.

Positions: We are hiring senior software engineers and researchers. Developers with Crypto or Machine Learning experience wanted!

https://www.linkedin.com/jobs2/view/97655757

visual basic