deleted by creator
deleted by creator
You can make it work mostly that way. Create a UKI (unified kernel image including EFI stub loader, kernel, initial filesystem and kernel parameters), then tell uefi to directly boot it. The four steps still run, but using only a single file.
I think the --all option is this mode.
At least on xorg the gifs I had worked.
I don’t know how it compares to nsxiv, but imv supports Wayland.
Nod32 offers a commercial antivirus for that scenario as well. The consumer variant has been discontinued.
That depends on the depth of the review, e.g. verifying the submitter is a member of the project, the software name does not conflict with a well known name,…
At least this prevents impersonation of well-known publishers or their software. Maybe all changes to metadata like the description should require a manual review even for established packages.
Those getting the most recent software versions, so nothing that should be running in a server.
I think that was a precaution. The malicious build script ran during the build, but the backdoor itself was most likely not included in the resuling package as it checked for specific packaging systems.
There is an actively maintained project for github: https://github.com/josegonzalez/python-github-backup
In that case you should ignore the interface in networkmanager (set it as unmanaged) and add one of the wireguard gnome shell extensions i think. https://extensions.gnome.org/extension/3612/wireguard-indicator/
That is regrettably not too unusual. Many platforms deactivate / ban empty accounts that were inactive for a long time. I guess “aging” accounts before use is something not too uncommon for bots.
Newer versions should have a replacable waste tank, but the tank does have a chip with serial number.
Maybe you can register a custom protocol and have your own script outside of flatpak that runs firefox. Then use an xdg-open command that prefixes the custom protocol.
There seems to be a receiver available using some tricks https://github.com/rgerganov/shanocast
Currently there is support for a network connection over thunderbolt you can use as a basis. If you want to send other data without network encapsulation, you’ll need to write a kernel module for that.
https://www.kernel.org/doc/html/latest/admin-guide/thunderbolt.html#networking-over-thunderbolt-cable
https://christian.kellner.me/2018/05/24/thunderbolt-networking-on-linux/
I’m not sure how well maintained it is, but porteus-kiosk might ve a very good fit for this use case…
Hmm, i think I mixed it up with the config. There is an all option in swayimgrc.