You are not logged in.
A newly added Debian Wiki page:
DebianInstallerCreateUSBMedia
Preparing a USB Memory Stick to boot the Installer
https://wiki.debian.org/DebianInstaller/CreateUSBMedia
Various advanced options.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Dpkg FAQ
Yeah this is pretty Deep Debian, but someone sometime might want to check it out:
https://wiki.debian.org/Teams/Dpkg/FAQ
EDIT: but be very careful about merged-usr:
https://wiki.debian.org/Teams/Dpkg/FAQ# … ed-dirs.3F
The dpkg developer does not agree with current Debian policy!
Last edited by johnraff (2023-11-17 01:29:11)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
The latest example debian installer preseed file for Bookworm:
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
^ Wow, things have changed. When I did the original BunsenLabs live-builds (hydrogen/jessie), the preseed was maybe 60 lines? Now it's almost 500. Looks like they've added a lot of helpful comments in addition to adding many possible options. Rock on, Debian!
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
This one too:
https://preseed.debian.net/debian-prese … n-full.txt
From: https://preseed.debian.net/debian-preseed/
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
^ OK, now you're just messing with me. Good night.
lmfao, I'm in tears.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
@johnraff wrote:
The latest example debian installer preseed file for Bookworm:
https://www.debian.org/releases/bookwor … reseed.txt
Nice! Thanks for posting this!
The full list is also just a massive set of options. Good stuff.
Offline
Good reference also for people writing shell scripts:
GNU Coding Standards
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Vulnerability in live-build
"live-build should authenticate files it downloads"
https://bugs.debian.org/cgi-bin/bugrepo … 718225#115
If you're using live-build, I'd highly recommend setting the various
`--mirror` and `--parent-mirror` settings in your `lb config` commands
explicitly, specifying HTTPS repos for each of those settings. It's not
a perfect solution, but as long as no one has compromised HTTPS, it
should be sufficient to plug this hole.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
The --parent-mirror-* options take their defaults from the matching mirror-* setting.
So I think we would need this in auto/config:
--mirror-binary 'https://deb.debian.org/debian'
--mirror-binary-security 'https://deb.debian.org/debian-security'
--mirror-bootstrap 'https://deb.debian.org/debian'
--mirror-chroot-security 'https://deb.debian.org/debian-security'
All the other values should derive correctly from those settings, I think.
It is a pretty mild local vulnerability though:
A malicious third party positioned in the network between the victim's mirror and the victim themselves can MITM the connection, and then provide a malicious kernel or initramfs. live-build will integrate these malicious files into the built ISO.
https://gist.github.com/ArrayBolt3/99d1 … 43eaf85520
Is this really something to be worried about?
Offline
It's been on the Bug Tracking System for years, so maybe not such a big deal. Someone has just picked it up again. Although "a malicious kernel or initramfs" sounds like something not to put in an iso.
Setting those mirror urls to https* looks like a good start anyway, and very easy to do.
Some day it would be nice if live-build would actually verify the downloaded files against the checksums Debian provide, just as is done when apt downloads packages from a repository.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Is there any interest in adding spice-vdagent to the package list for BunsenLabs?
It makes the OS a better behaved guest for spice-based virtual machines, such as gnome-boxes & virt-manager, with no added overhead for bare metal installs.
Offline
^I always add it to my VMs because it makes several things work better, but there are possible security issues. I'm not sure if it should be there by default. I notice the Debian installer auto-detects if you're installing to a VM and adds qemu-guest-agent but not spice-vdagent.
Another thing is that RedHat seem to be about to pull the plug on Spice anyway, so spice-vdagent's days might be numbered, even on Debian. Not good, because there seems to be no replacement atm.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
SPICE is supported for RHEL 8 so that means it has maintenance support until 2029-05-31. EDIT: and Debian will support it unitl trixie EOL if it makes the release.
The spice-vdagent daemon only runs if /dev/virtio-ports is present so it will have no effect on a bare metal system beyond the ~200KiB of disk space.
Last edited by Head_on_a_Stick (2025-01-30 07:45:56)
Offline
SPICE is supported for RHEL 8 so that means it has maintenance support until 2029-05-31. EDIT: and Debian will support it unitl trixie EOL if it makes the release.
Well, yes if it gets into Trixie then of course it would be extremely unusual to be dropped before EOL.
The spice-vdagent daemon only runs if /dev/virtio-ports is present so it will have no effect on a bare metal system beyond the ~200KiB of disk space.
But the main reason I'd be reluctant to put it in by default is the security issues for VMs. I don't think users should have that dropped on them without warning.
eg (first thing that came up):
https://www.openwall.com/lists/oss-secu … 20/11/04/1
`spice-vdagentd` is running as *root* as a socket activated systemd service.
Anyway, it's helping to break down the VM's isolation from the outside world, which not everybody might want.
My VM's are just for testing so it's less important.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
I was briefly wondering if we could tweak the Debian-Installer to offer an install of spice-vdagent along with qemu-guest-agent if it detected being run in a VM... then remembered bl-welcome.
It should be quite easy to add that offer to the welcome script if a VM is detected (along with a mention of possible security issues). I think that would be a good solution, no?
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
The bl-welcome addition sounds like a good idea :-)
Offline
This means that Debian-Installer is now automatically installing spice-vdagent if it detects a virtual machine and a desktop system, so probably no need for us to do anything.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline