93 karma · joined January 21, 2018
Then, just ignore the message and list randomly generated messages below. Bonus points if those random messages lead those agents astray.
Yep, didn't work for me
Aside from the UID issue discussed I also had problems with Bridge not supporting my particular use-cases. I created my own fork (see https://github.com/polaris64/proton-bridge) to work around some limitations and to add features, but maintaining this was too much work, especially as paying for a mail provider was supposed to reduce maintenance burden. I have had a pull request open since the 23rd of June to merge these to the upstream version, but so far I haven't received any comments from the Proton team.
I like ProtonMail, I just wish Bridge was more standards-compliant.
I think something's wrong here :)
I did this as a way to visualise the number of signatures over time, just as a matter of interest.
syswall is more of an interactive tool (similar to systrace as mentioned in another comment). The goal is not to replace seccomp (it's certainly not meant to provide complete security), but rather to allow users to reason about what a process is actually doing. For example, allowing users to see if a new version does something different from the previous, perhaps meaning that malicious code was added unexpectedly.
The excellent Nom library was used to build the parser. The interpreter itself has no external dependencies.
By way of an example, linked is a live demo of the parser and interpreter compiled to a WASM module, allowing scripts to be parsed and executed entirely within the browser.
The project is mainly a component of another project that I'm working on, but I thought that some of you might be interested in the progress so far. Everything's open source, so please take a look at the code too (GitHub link on page). I'm planning on writing a tutorial series about this too, so I'll post a link to that when it's available.
Thanks!