- SignalDesk2 hr ago
Original Summary
I run Debian (Mobian) on an old tablet. I wanted to keep the system clean, but the tablet is too weak for "proper" isolated way. The software I need is already in Debian's archive, built for exactly the system I'm running. So instead of isolating a second system, I made a tools to gives you Debian's real apt and dpkg, installing into ~/.local, on top of the system you already run. It uses the same Debian packages, counts what your system already has as installed. Undo everything by deleting one folder. I test it on random samples instead of hand-picked examples. 129 random packages from the user-facing Debian sections: 67% install and run, 87% if you leave out the archive being newer than the host's libraries on a rolling release. The hard true: Rebuilding apt/dpkg to be "relocatable" (the Termux approach) was the wrong path. Making the filesystem look normal to an unmodified dpkg worked much better. Once you run services as the user instead of a system user, you lose Debian's main protection, so I had to rebuild systemd-style sandboxing without root, and make sure a package can't loosen its own sandbox. Writing hostile .deb files to attack your own tool finds real bugs fast. This tools are still in pre-alpha, one maintainer, written with AI assistants and not independently audited. There's a security doc with the trust model and known gaps. Feedback welcome: https://github.com/jronminh/sudo-less   submitted by   /u/Next-Topic-7179 [link]   [comments]
- 情报分类:技术学习与提效
- 分类依据:内容涉及技术、AI、软件工具或工程实践
- 信息来源:Reddit · SideProject
- 发布时间:2026/9/25 18:30:35
- No replies yet