Did you post this right as I edited the title? Lol.
moonpiedumplings
Not really? From this page, all it looks like you need is a salsa.debian.org account. They call this being a "Debian developer", but registration on Debian Salsa is open to anybody, and you can just sign up.
Once you have an account, you can use Debian's Debusine normally. I don't really see how this is any different from being required to create an Ubuntu/Launchpad account for a PPA. This is really just pedantic terminology, Debian considers anybody who contributes to their distro in any way to be a "Debian Developer", whereas Ubuntu doesn't.
If you don't want to create an account, you can self host debusine — except it looks like you can't self host the server that powers PPA's. I consider this to be a win for Debusine.
Make sure you stream with the "linux" tag so thag people who follow that tag around like me can find you!
Probably the binary blobs.
Ventoy uses binary blobs which can't be trusted to be free of malware or compliant to their licenses. https://github.com/NixOS/nixpkgs/issues/404663 See the following Issues for context: https://github.com/ventoy/Ventoy/issues/2795 https://github.com/ventoy/Ventoy/issues/3224
Source: https://github.com/NixOS/nixpkgs/blob/c6f52ebd45e5925c188d1a20119978aa4ffd5ef6/pkgs/by-name/ve/ventoy/package.nix#L213 (nixpkgs git repo)
I will admit that I still use ventoy though.
To copy what I said when this was posted in another community:
The png didn't do shit. Users where compromised by a malicious extension.
Steganagrophy (hiding data in a png) is a non issue and cannot do anything independently. It is also impossible to really stop.
Which is probably why the cybersecurity news cycle likes to pretend that steganagrophy is a risk on it's own, so that they can sell you products to stop this "theat".
I hate the clickbait title is what I'm trying to say. But the writeup is pretty interesting.
Although the real solution to this problem is probably only letting users install known safe extensions from an allowlist, instead of "pay us for consulting!".
The png didn't do shit. Users where compromised by a malicious extension.
Steganagrophy (hiding data in a png) is a non issue and cannot do anything independently. It is also impossible to really stop.
Which is probably why the cybersecurity news cycle likes to pretend that steganagrophy is a risk on it's own, so that they can sell you products to stop this "theat".
I hate the clickbait title is what I'm trying to say. But the writeup is pretty interesting.
Although the real solution to this problem is probably only letting users install known safe extensions from an allowlist, instead of "pay us for consulting!".
I have a similar setup, and even though I am hosting git (forgejo), I use ssh as a git server for the source of truth that k8s reads.
This prevents an ouroboros dependency where flux is using the git repo from forgejo which is deployed by flux...
Lmao. They gave a windows vm 4 gigs of ram for this. Wtf.
There is no way this is better than fileless persistence, although this seems easier to execute.
But why not a Linux vm?
Why not an obfuscated binary?
I admire the laziness though.
Proxmox is based on debian and uses debian under the hood...
This post is a pretty good overview of why oauth2/openid are more popular.
Not to say that oauth/openid have never ever had vulnerabilities of their own, but there is a big difference between "accept these configurations" and what saml is, which is "parse this xml".
This is exactly why syncthing is problematic as a backup solution.
If I delete a file on one host and syncthing is doing the default two way sync, the deletion is also replicated to the other machine.
They acknowledge this in their faq: https://docs.syncthing.net/users/faq.html#is-syncthing-my-ideal-backup-application
You can mitigate some of these issues with file versioning, or one way syncs, but ultimately it's just not really the tool for the job.