Fair enough, I see what you mean now. This is more of a progress report than a project release. Sorry for the misunderstanding. FWIW I think your project is cool regardless of whether you used AI or not, so great work!
P.S. Out of curiosity I did read a bit of your comment history and I do agree with your comments w.r.t privacy and AI disclosure. It is a tricky problem indeed.
If it’s not made with AI you can use the CBH tag
Have you heard of Tube Archivist?
Edit: ok i see you mentioned it in your Local Smarttube announcement post. Why doesn’t Tube Archivist fit your needs?
I believe you need AI disclosure to post in this sub. Check the sidebar rules.
Just look up firmware rootkits and UEFI rootkits. For example: https://arstechnica.com/information-technology/2022/07/researchers-unpack-unkillable-uefi-rootkit-that-survives-os-reinstalls/
Security is a big reason to use VMs. Containers share the kernel with the host. That means that any of the kernel vulnerabilities from this year (like DirtyFrag and CopyFail) could have been used to compromise your host. Once the host is compromised, the only way to be safe is to literally buy a new machine. Seriously. Viruses can bury deep and even infect the motherboard firmware to persist indefinitely.
Kernel vulnerabilities are frequent enough that I find VMs worth it. I still use containers in my VMs though.
Why not put your wiki notes on your admin machine (whatever machine you use to manage the proxmox server)?
If you wrote an article I’d read it! But this is a great starting point nonetheless, thanks
Mind sharing which local AI you used, the harness, etc?
For those that like the cli, you can use flatpak remote-info --log flathub com.stremio.Stremio to scroll through the list of past versions, and look for the “Commit” id of the version you want, then do:
flatpak update --commit=<commit id> com.stremio.Stremio
Then use flatpak mask to prevent further updates.
Been following this project for a while but did it ever get a formal security audit?
This is the one used by hacker news right?
A lot of times its tech opinion articles. Stuff like “why AI is bad”. And I read the arguments and judge them for myself.
I already considered that, and for an untrusted website I already don’t trust the content or the scripts. So it doesn’t matter if it was modified or not, it’s still untrusted.
Facts can be verified with sources you do trust (which should be using HTTPS). Logic can be used to verify others.
IMO when reading random articles on the internet you already have to worry about untrusted scripts. I just use NoScript, and if the website requires Javascript I move on
If you’re just pushing for WebPKI without “thinking too hard” about perpretrating a security system with a large number of failure points, then you’re following that windows method.
SSL/TLS have very specific benefits. None of which matter that much for reading random articles on the web. So I don’t see the problem with this website doing their own thing to bring attention to the potential issues of the current system.
It works fine, just ignore the warning and don’t enter any sensitive info
I bet another reason is security. You might not trust the NUT software. It might be proprietary, and even if its open source, it might not be scrutinized enough to be safe.
Using separate hardware, lets you take in the power loss signal from the NUT and then convert it to a channel you might trust more, like an http request over wireguard. Alternatively you could use a VM with usb passthrough on the main PC…though usb passthrough still has risks.
This is a cool idea, and I love the hacker energy behind it, but I agree with some of the other comments that the receiver would have to trust you quite a bit to allow hardware into their house. Even with the SSH view-only accounr, you could be putting the SSH server in a VM so that the client thinks they’re seeing the whole OS but they aren’t.
Alternative idea would be to provide an open source ansible script or docker compose file to spin up everything you need, and let them verify and deploy it themselves. Then they give you the wireguard configs to remote in.
Declarative configuration (like docker compose) is basically “code local, push remote”, and it has a lot of benefits, including improving efficiency because you have a clearer idea of exactly what is set up on the server, to make it easier to debug or make changes.
Contrast this with just sshing in and running a bunch of commands to install something. Then coming back months later and wondering “what files did I touch? what packagea did I install? Hmm dpkg log says I added X but then later I removed it, so was it important?” Etc.