Bug#1010248: ITP: wlgreet --

2022-04-26 Thread duck
Package: wnpp Severity: wishlist Owner: Marc Dequènes (Duck) X-Debbugs-Cc: debian-devel@lists.debian.org Control: block -1 with 1010247 * Package name: wlgreet Version : 0.3 Upstream Author : Kenny Levinsen * URL : https://git.sr.ht/~kennylevinsen/wlgreet * License

Bug#1010247: ITP: greetd -- minimal and flexible login manager daemon

2022-04-26 Thread duck
Package: wnpp Severity: wishlist Owner: Marc Dequènes (Duck) X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: greetd Version : 0.8.0 Upstream Author : Kenny Levinsen * URL : https://git.sr.ht/~kennylevinsen/greetd * License : GPL-3 Programming La

Re: shim-signed

2022-04-26 Thread The Wanderer
On 2022-04-26 at 18:05, Paul Wise wrote: > On Tue, 2022-04-26 at 20:41 +0200, Bastian Blank wrote: > >> secure boot signing process at Microsoft is a review-sign process > > What kind of review are Microsoft doing of the Debian shim? > > Are they reviewing the source and checking for a reproduc

Re: shim-signed

2022-04-26 Thread The Wanderer
On 2022-04-26 at 10:14, Marc Haber wrote: > On Sat, 23 Apr 2022 18:21:47 +0100, Steve McIntyre > wrote: >> Alternatively, people can build replacement shim-signed packages >> using their own root of trust if desired. If we had a large enough >> number of users wanting a different root of trust,

Re: shim-signed (was: Firmware - what are we going to do about it?)

2022-04-26 Thread Paul Wise
On Tue, 2022-04-26 at 20:41 +0200, Bastian Blank wrote: > secure boot signing process at Microsoft is a review-sign process What kind of review are Microsoft doing of the Debian shim? Are they reviewing the source and checking for a reproducible build? -- bye, pabs https://wiki.debian.org/Pau

Re: shim-signed (was: Firmware - what are we going to do about it?)

2022-04-26 Thread Bastian Blank
Moin On Tue, Apr 26, 2022 at 04:14:02PM +0200, Marc Haber wrote: > On Sat, 23 Apr 2022 18:21:47 +0100, Steve McIntyre > wrote: > >We don't have good docs around this in general (hey, it's security > >software - it's against the law to write good and complete docs!), but > >I've certainly discusse

Re: shim-signed (was: Firmware - what are we going to do about it?)

2022-04-26 Thread Steve McIntyre
Marc Haber wrote: >On Sat, 23 Apr 2022 18:21:47 +0100, Steve McIntyre > >>Better than that, our shim-signed source package always double-checks >>things here. At build time it removes the Microsoft signature and >>compares that shim binary to the binary that we submitted for >>signing. We would sp

Re: shim-signed (was: Firmware - what are we going to do about it?)

2022-04-26 Thread Ansgar
On Tue, 2022-04-26 at 16:04 +0200, Marc Haber wrote: > On Sat, 23 Apr 2022 13:54:59 +0200, Ansgar wrote: > > Why? > > If only I knew. I myself don't feel to comfortable to rely on > Microsoft being able to pull the plug on us any time. I don't know > whether they can, but I imagine some kind of r

Bug#1010210: ITP: orthanc-neuro -- Neuroimaging plugin for Orthanc

2022-04-26 Thread Sebastien Jodogne
Package: wnpp Severity: wishlist Owner: Sebastien Jodogne X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: orthanc-neuro Version : 1.0 Upstream Author : Sebastien Jodogne * URL : https://book.orthanc-server.com/plugins/neuro.html * License : GPL P

Re: shim-signed (was: Firmware - what are we going to do about it?)

2022-04-26 Thread Marc Haber
On Sat, 23 Apr 2022 18:21:47 +0100, Steve McIntyre wrote: >We don't have good docs around this in general (hey, it's security >software - it's against the law to write good and complete docs!), but >I've certainly discussed this with a few folks over the years. It would be great to have that writ

Re: shim-signed (was: Firmware - what are we going to do about it?)

2022-04-26 Thread Marc Haber
On Sat, 23 Apr 2022 13:54:59 +0200, Ansgar wrote: >On Sat, 2022-04-23 at 12:21 +0200, Marc Haber wrote: >> >Is the presence of shim-signed on the install media enough to make >> >people feel somehow contaminated? >> >> I think so, yes. Personally, I don't care too much but i can >> understand why

Re: Firmware - what are we going to do about it?

2022-04-26 Thread Hans
Dear developers, if like to here an opinion from the useer side, please listen. I made many installations of debian in the last years, mostly notebooks preinstalled with windows. What often lacks is, that on many newer notebooks the network card is not accessible. Either due of missing firmware

Re: Firmware - what are we going to do about it?

2022-04-26 Thread Hakan Bayındır
On 4/26/22 12:08, Andrey Rahmatullin wrote: On Tue, Apr 26, 2022 at 11:59:20AM +0300, Hakan Bayındır wrote: No, they do not. Most popular devices won't work at all without non- free firmware, including boring things such as mass storage (SD cards, SSD, HDD, ..., and controllers), input device

Re: Firmware - what are we going to do about it?

2022-04-26 Thread Andrey Rahmatullin
On Tue, Apr 26, 2022 at 11:59:20AM +0300, Hakan Bayındır wrote: > > No, they do not. Most popular devices won't work at all without non- > > free firmware, including boring things such as mass storage (SD cards, > > SSD, HDD, ..., and controllers), input devices (keyboards, mice, ...). > > Yeah, y

Re: Firmware - what are we going to do about it?

2022-04-26 Thread Hakan Bayındır
> On 26 Apr 2022, at 11:30, Ansgar wrote: > > On Tue, 2022-04-26 at 10:47 +0300, Hakan Bayındır wrote: >> While I understand where you're coming from, I don't think such thing >> is necessary, because a) Most popular devices with non-free firmware >> blobs already work without such firmware >

Re: Firmware - what are we going to do about it?

2022-04-26 Thread Ansgar
On Tue, 2022-04-26 at 10:47 +0300, Hakan Bayındır wrote: > While I understand where you're coming from, I don't think such thing > is necessary, because a) Most popular devices with non-free firmware > blobs already work without such firmware No, they do not. Most popular devices won't work at al

Re: Firmware - what are we going to do about it?

2022-04-26 Thread Hakan Bayındır
On 4/26/22 09:12, Ansgar wrote: On Mon, 2022-04-25 at 23:48 +0300, Hakan Bayındır wrote: While what you’re saying is technically true, the default selection means much more than a default. It’s defines the stance of Debian, as a whole. [...] So, if Option 5 is adopted, the default state is