Pierre Alain

@arkenoi, @froeb I recently saw that you've been trying to adapt liteqube to Qubes 4.2. I'm throwing a bottle into the sea in case you might have an idea of...

Hi @100111001 thanks for your report! Indeed shell commands are not correctly taken into account (see https://github.com/mirage/qubes-mirage-firewall/blob/main/command.ml) and the provided port forwarding script will require a shell compatible with iptables...

Yes unfortunately the script will not work with mirage because it runs the netvms chain from the target machine to sys-net and we will not be able to run shell...

Thanks for the reports! With `qvm-prefs mirage netvm x` I can see in the logs a line with `INF [qubes.db] got update: "/qubes-gateway" = "10.137.0.x"` (this is good but nothing...

In the working process for adding OpenBSD as a possible netvm, I've been working on dynamic netvm management. @xaki23, @rootnoob would you mind to try out the current head of...

Update: I still have some issues, and I'm not sure how to solve them :( If the uplink AppVM is stopped we have no qubesDB updates (probably this could be...

Sorry for the daly, this issue should be fixed by #178 which has been merged. @rootnoob @xaki23 this has been released yet, but in the meantime you should be able...

To give mirage-next a try, I updated qubes-mirage-firewall to the current head of this repository and the changes were pretty straightforward (https://github.com/palainp/qubes-mirage-firewall/tree/mirage-next). I just ended up with a key defined...

The current state of mirage allows to target one of the root/private/volatile block devices with `let block = block_of_xenstore_id "51712"` and the id value is done via $202*2^8+minor$ as explained...

The linked article in the PR (http://locklessinc.com/articles/tcp_checksum/) is very interesting and, after a quick test, I can confirm that it computes the csum very fast :) (but so far the...