oso
pycryptodome
Our great sponsors
oso | pycryptodome | |
---|---|---|
16 | 8 | |
3,403 | 2,664 | |
1.4% | - | |
6.7 | 8.4 | |
about 1 month ago | 6 days ago | |
Rust | C | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
oso
-
Who's hiring developer advocates? (October 2023)
Link to GitHub -->
-
Show HN: ILLA is an Open-source alternative to Retool
Not OP but Authentication is easy, authorization is a cross-cutting concern that often requires custom code. E.g., there are people and teams, both of which can have different kinds of access to something (read/write). Sometimes teams have sub-teams. Do the sub-teams have access to the parent teams' resources and/or vice versa? Also what kind of sharing are you going to support? Do people have to have an account to view stuff shared to them or can you just send a link? There are some efforts to make custom DSLs for describing authorization policies, to avoid cross-cutting code[1].
Computed fields require different treatment at every level of the stack. This isn't inherently hard, but it is an extra feature these low-code/no-code platforms need. Where things get difficult is inn migrations. It's common for a field that is computed at the beginning to become customizable, or for the computation to change. When that happens, what should the value be for old columns? Computed fields also often pull data from multiple other tables, which may require some combination of custom queries and database optimization.
[1] https://github.com/osohq/oso
-
Resource-based authentication
Oso and OpenFGA are two alternatives that implement Zanzibar-style authorisation.
- Oso - batteries-included framework for building authorization in your application.
-
Decoupling Authorization Logic from Code in NodeJS
There's Oso as well
-
Is Datalog a good language for authorization?
Well this was fun to see! I'm the CTO of Oso, where we're building Polar (the second of the links mentioned https://docs.osohq.com/).
I have a few really minor nitpicks, so will try and make up for it by adding to the discussion :)
First of all, it doesn't really make sense to talk about Datalog as a good language for authorization, because much like with Prolog there doesn't really exist a single implementation of it. OPA's language Rego is a datalog variant, and Polar started out as a Prolog variant (although it's not really recognisable as one any more).
And that's an important point because otherwise it would be pretty reasonable to decide that: logic programming is good for authorization => you should go find the most battle-tested language out there and use that. For example, there's SWI Prolog [1] and Scryer Prolog [2] as two of my favourites.
To me, the thing that is mind-blowing about logic programming, is (a) how powerful the paradigm is, and (b) how concisely you can implement a logic programming language. Take miniKanren [3] which is a full-blown logic language in a few hundred lines of code.
In my mind, the original article makes a decent case that logic programming is a good fit for authorization. And just generally I love anyone bringing attention to that :)
But to me, the reason logic programming is such a solid foundation for authorization logic is the pieces you can build on top of it. For Polar, we've added:
- Types! So you can write authorization logic over your data types and help structure your logic. We've implemented this by simply adding an additional operator into the language that can check types
-
Hey Rustaceans! Got an easy question? Ask here (52/2021)!
First time hearing about rhai, but there's a project in that space called Oso that's authored in Rust and uses a different DSL than Rego. You may or may not find it appealing.
-
Hey Rustaceans! Got an easy question? Ask here (44/2021)!
Authentication is probably the aspect of it that's the weakest. Authorization has a few nice libs, with Oso probably being the nicest, but authentication is mostly roll your own from what I've seen.
-
We Built a Cross-Platform Library with Rust
> Hopefully Oso open source their library.
https://github.com/osohq/oso seems to have the core, C FFI, and language bindings.
Thanks! PHP is a highly requested language for us and we've been rolling them out based on demand. You can vote for it if you want here https://github.com/osohq/oso/issues/791
pycryptodome
-
If you have created an app with encrypted data and/or HIPAA compliance considerations, what packages and resources did you use?
PyCryptodome
-
Daily General Discussion - December 28, 2022
Install pycryptodome instead, it's forked from pycrypto (which is dead) and is actively maintained by the same team.
- pycryptodome vs pycryptodomex is there a difference?
- Weird error when running revdep-rebuild (failed to split pycryptodome package)
-
Please Help. I have installed everything yet tnote dos note work, there is nothing on the net now.
The specific bug you are having is in this issue of PyCrypto. That said, tnote should move on as PyCrypto is no longer maintained.. Ideally, tnote could migrate to PyCryptodome which is a near drop in replacement for PyCrypto, so "potentially" a single line of code change.
-
Hello there, I have something to ask for those who use tidal-dl on termux to download hi-res music. I was new to this and i followed every command on downloading tidal-dl, but whenever I've got in "pip3 install --upgrade tidal-dl" it always ended up like this, I'm so tired try and tried it again.
Possibly not a termux only issue (see this).
-
Picocrypt - A FOSS 3MB Encryption Tool!
I know what you mean and I understand your concern. As it currently stands, I can say with a high level of confidence (although not complete) that Picocrypt is very secure. That's because Picocrypt uses ChaCha20, which is a simple cipher to implement correctly and without errors. It's extensively documented. I have a solid understanding of cryptography and I carefully choose a Python cryptography library with over 1k stars do implement ChaCha20. I know that there's a lot of responsibility when making security software, which is why I'm accepting donations to get Picocrypt audited as soon as possible (ideally within a year). Thanks for your feedback, I appreciate it.
What are some alternatives?
CASL - CASL is an isomorphic authorization JavaScript library which restricts what resources a given user is allowed to access
cryptography - cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
node-casbin - An authorization library that supports access control models like ACL, RBAC, ABAC in Node.js and Browser
keyring
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
PyCrypto - The Python Cryptography Toolkit
django-guardian - Per object permissions for Django
HomeBrew - 🍺 The missing package manager for macOS (or Linux)
django-rules - Awesome Django authorization, without the database
Secure - Secure 🔒 headers for Python web frameworks
Ory Keto - Open Source (Go) implementation of "Zanzibar: Google's Consistent, Global Authorization System". Ships gRPC, REST APIs, newSQL, and an easy and granular permission language. Supports ACL, RBAC, and other access models.
Spoodle - A mass subdomain (Subbrute) + poodle vulnerability scanner