User NS usage and attack surface mitigation on debian

I stumbled upon this answer from three years ago (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898446) "User namespaces *are* enabled - but by default, they can only be created by root". I need clarifications on that, cause I didn't quite know how namespace management works. I experimented

Bug#986822: BUG#986822 Broadwell SST CATPT Sound module

Hi Vincent I'll kill the pipewire server, i would uninstall the packages but they are hard deps for gnome now. Is the fw file catpt is trying to load the correct one? Is there new fw files that come with catpt that have been forgotten? Is there a listiing for the error codes -110 and -2, are they

Re: "tweewide: Fix most Shebang lines" in stable updates

Hi Ben, On Tue, Jun 15, 2021 at 12:52:31AM +0200, Ben Hutchings wrote: > Commit c25ce589dca10d64dde139ae093abc258a32869c "tweewide: Fix most > Shebang lines" was backported to stable branches including 4.9 and > 4.19. This changes scripts interpreted by bash, perl, and python to > use /usr/bin/en

Bug#989551: linux-image-5.10.0-7-amd64: linux-image-5.10.0.7-amd64 hang on boot. Shows symbols: '^@^@^@' and nothing else. Debian testing.

Hi, On Tue, Jun 15, 2021 at 10:05:29AM +0300, Михаил Осипов wrote: > Sorry, missed this message. Here are the logs. Several boots with and > without recovery mode. Last one with old kernel. Thanks for provinding those, much appreciated and it helps. So from the boot logs this might be amdgpu rela

Re: release notes mentioning dropped support?

wOn Mon, 2021-06-14 at 06:25 +0100, Justin B Rye wrote: > Paul Gevers wrote: > > + > > + Hardware that's no longer supported > > The contraction "that's" seems out of place in a title - probably we > should just use: > >  No longer supported hardware > That would correctly be s