durable-php
firejail
durable-php | firejail | |
---|---|---|
5 | 139 | |
4 | 5,464 | |
- | - | |
9.5 | 9.7 | |
2 days ago | 7 days ago | |
PHP | C | |
MIT License | GNU General Public License v3.0 only |
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.
durable-php
-
Authorization is still a nightmare for engineers
That's a really clean implementation. And the shares are used to resolve authorization here [1], right?
Two things that we're solving for at Oso is: making it easier for multiple teams to collaborate on permissions (which we solve by having a declarative language), and solving the list filtering problem (as talked about in the post).
If you don't need either of those two things and are happy with a DIY approach, what you've shared would work great IMO. If you packaged that up as a standalone solution, I could see a lot of people getting value from it!
[1] https://github.com/bottledcode/durable-php/blob/3ad509fcdbb3...
-
Ask HN: What are some unpopular technologies you wish people knew more about?
Heh. https://github.com/bottledcode/durable-php is a semi-faithful php port of Orleans, borrowing some ideas from similar things too. I’ve actually been working on some really neat FFI things for this the past few weeks.
It’s fun.
-
Your coolest Packagist project that no one uses?
Durable php: https://github.com/bottledcode/durable-php based off of C# durable functions.
-
Thoughts on event sourcing: Replaying events
The way I've successfully used event sourcing was to think of it like a WAL where you are basically building up a HashMap. (This is how DurablePHP works -- https://github.com/bottledcode/durable-php -- if you are interested) Replaying should result in the exact same HashMap every single time, any side-effects only happen once.
firejail
-
Sandboxing All the Things with Flatpak and BubbleBox
bubblewrap is designed as a low-level too. There is nothing quick and dirty about it. It disallows everything by default and you have to be explicit about what you want to share with the host. If your application needs complex permissions/resources, then you will need to have a complex bubblewrap command line.
Once you have figured out which permissions/resources you need for a given program, you can wrap the command line invocation in a shell script.
If you want other people to do the work of defining permissions/resources, then have a look at firejail: https://github.com/netblue30/firejail
-
Ask HN: What are some unpopular technologies you wish people knew more about?
Firejail is cool: https://github.com/netblue30/firejail
Linux namespaces/cgroups but nowhere near as heavy as Docker.
I use it when I want to limit the memory of a Python script:
```
-
Toolship: A (More) Secure Workstation
Firejail can also be a useful option, though no good if you're on Mac https://firejail.wordpress.com/
Uses the same Linux primitives as docker etc, but can be a bit more ergonomic for this use case
-
Firejail: Light, featureful and zero-dependency security sandbox for Linux
Firejail, Flatpak (which uses Bubblewrap under the hood), and Snap (which uses AppArmor) all use the same underlying technology: Linux namespaces.
This question comes up a lot, and has been answered here: https://github.com/netblue30/firejail/wiki/Frequently-Asked-...
TL;DR: Firejail has much more comprehensive features than Flatpak (Bubblewrap). Firejail also has more comprehensive network support, support for AppArmor and SELinux, and easier seccomp filtering.
Compared to Snap (which uses AppArmor), Firejail is compatible with AppArmor and again goes above and beyond with a lot of additional features.
-
Bubblewrap – Low-level unprivileged sandboxing tool used by Flatpak
Wonderful little tool, too bad you must chain various exec calling tools to get cgroups (a bit akin to `ionice ... nice ... cmd`) and Linux users namespaces can't allow UNIX sockets while preventing network access (I think?).
Migrated from Firejail when its complexity annoyed me too much and I hit https://github.com/netblue30/firejail/issues/3001 (Firejail doesn't like parens or brackets in --put/--get parameters) to a badly NIH version using bwrap and bash to have "profiles":
- Firejail: Light featureful and zero-dependency security sandbox for Linux
-
Do, or do not. There is no try
Firejail does this. The profile database is the two "profile" directories in https://github.com/netblue30/firejail/tree/master/etc
-
Strange times make for strange friends...
What do you mean by a Firefox container? Do you mean FireJail?
What are some alternatives?
Resolve - A simple PSR-11 compliant dependency injector.
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
Encrypted - Encryption cast for Eloquent
flatpak - Linux application sandboxing and distribution framework
ConcurrencyHelper - ConcurrencyHelper is a library for easily and efficiently running any callable via multiple parallel PHP instances.
bubblejail - Bubblewrap based sandboxing for desktop applications
ConsolePainter - BEAUTIFUL Console Colors via a Fluent Interface.
Flatseal - Manage Flatpak permissions
class-finder - Utility classes to help discover other classes/namespaces
yabai - A tiling window manager for macOS based on binary space partitioning
MultiPhreading - PHP Multi Process Threading, Shared Memory Berkley Keystore, Message Queue system.
podman - Podman: A tool for managing OCI containers and pods.