Processed: src:busybox: busybox-udeb: /etc/udhcpc/default.script assumes a default route from DHCP

[Debian Bug Tracking System]

Processing control commands:

> affects -1 debian-installer
Bug #927413 [src:busybox] src:busybox: busybox-udeb: /etc/udhcpc/default.script 
assumes a default route from DHCP
Added indication that 927413 affects debian-installer

-- 
927413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Debian Installer Buster RC 1 release

[Miroslav Kure]

On Mon, Apr 15, 2019 at 10:47:40PM +0200, Cyril Brulebois wrote:
> 
> This release includes Secure Boot support on amd64, which should work
> out of the box on most Secure Boot enabled machines. This means there
> should be no need to disable Secure Boot support in the firmware
> configuration anymore.

I have this little HP EliteDesk 705 G2 Desktop Mini and trying to boot
the RC1 installer[1] from usb stick with Secure Boot enabled:

 1) d-i boot menu appears (in the past - alpha3 - even this step failed
on this machine something along "no bootloader found")

 2) no matter which option I choose (Graphical install, Advanced, ...)
the following error appears:

error: /install.amd/vmlinuz has invalid signature.
error: you need to load the kernel first.
  
Press any key to continue

The usb stick seems to be created correctly as installation on my
other machine (although no Secure Boot there) works as expected.

-- 
Miroslav Kure

[1] 
https://cdimage.debian.org/cdimage/buster_di_rc1/amd64/iso-cd/debian-buster-DI-rc1-amd64-netinst.iso

Re: Debian Installer Buster RC 1 release

[Steve McIntyre]

On Fri, Apr 19, 2019 at 01:12:43PM +0200, Miroslav Kure wrote:
>On Mon, Apr 15, 2019 at 10:47:40PM +0200, Cyril Brulebois wrote:
>> 
>> This release includes Secure Boot support on amd64, which should work
>> out of the box on most Secure Boot enabled machines. This means there
>> should be no need to disable Secure Boot support in the firmware
>> configuration anymore.
>
>I have this little HP EliteDesk 705 G2 Desktop Mini and trying to boot
>the RC1 installer[1] from usb stick with Secure Boot enabled:
>
> 1) d-i boot menu appears (in the past - alpha3 - even this step failed
>on this machine something along "no bootloader found")
>
> 2) no matter which option I choose (Graphical install, Advanced, ...)
>the following error appears:
>
>error: /install.amd/vmlinuz has invalid signature.
>error: you need to load the kernel first.
>  
>Press any key to continue

Hmmm, odd. Have you done anything special with the SB key setup on
this machine, like reset the keys database or similar?

>The usb stick seems to be created correctly as installation on my
>other machine (although no Secure Boot there) works as expected.

Right.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Further comment on how I feel about IBM will appear once I've worked out
 whether they're being malicious or incompetent. Capital letters are forecast."
 Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html

Re: Debian Installer Buster RC 1 release

[Miroslav Kure]

On Fri, Apr 19, 2019 at 12:37:56PM +0100, Steve McIntyre wrote:
> 
> Hmmm, odd. Have you done anything special with the SB key setup on
> this machine, like reset the keys database or similar?

Not intentionally, but maybe Ubuntu did during installation.

History:
 - The machine came with Windows 10 preinstalled and SB enabled
 - Being unable to turn off SB and hence install Debian (2 years ago),
   I tried Ubuntu and Fedora, whose live CDs worked like a charm
 - As an interim solution until Debian gets SB support I decided to
   install Ubuntu
 - I vaguely remeber some questions regarding SB (create passphrase
   and then after reboot type few characters from that passphrase??)
 - Due to a bug in network card driver I decided to try Fedora with
   newer kernel - no SB questions there, it just worked, but I could
   not accomodate to their tools
 - Last fall I installed Windows 10 again since I needed one windows
   program to test - no SB related questions there
 - Seeing d-i RC1 announcement I decided to finally install Debian and
   here we are
   
I am open to suggestions to try on this machine.

-- 
Miroslav Kure

Re: Problem: UUIDs not being used everywhere for disks in stretch

[Steve McIntyre]

Hey folks,

On Sun, Apr 07, 2019 at 01:01:34AM +0100, Ben Hutchings wrote:
>On Sat, 2019-04-06 at 16:54 +0100, Steve McIntyre wrote:
>> Actually...
>> 
>> On Sat, Apr 06, 2019 at 04:36:59PM +0100, Steve McIntyre wrote:
>> > We need to run update-dev *after* the filesystem creation scripts and
>> > this fixes things. I've just copiet it to 99update-dev locally while
>> > testing and that made all the difference. It could probably also just
>> > be moved instead of copied - at this point I'm not sure if anything in
>> > the other scripts also depend on the udev updates for their
>> > functionality. Fundamentally, it's a fairly harmless thing to run
>> > repeatedly so I'm tempted to just run it twice. Thoughts?
>> 
>> I think we're definitely going to need this, actually - new device
>> entries may not show up otherwise.
>> 
>> I'm also seeing in my testing that I *do* need to force a "udevadm
>> trigger" in the second script. Fundametally, it you don't get new
>> kernel events when a mkfs happens so udev will never notice.
>
>Closing a block device that is opened for writing should trigger a
>change event.  I tested this now with Linux 4.19.28 and it still seems
>to happen.

OK, that's a useful thing to check - thanks!

To see WTF is going om, I've just re-run test installations of both
stretch (9.8.0) and buster (a netinst from last week). In each case,
I've started "udevadm monitor | logger -t udevmon" in the background
in the installer. I've run a basic installation through to completion,
then on first boot I've run:

 # udevadm monitor > log &
 # swapoff -av
 # mkfs.ext4 /dev/vda3

I've grepped out the udev monitor log lines from both the installer
and the installed system - see attached.

*In the installer*, we're not seeing *any* "change" events for the
hard disk (vda in my case), in either stretch or buster. We just get
the "add" and "remove" events. In the buster installer, my temporary
hack of forcing the "udevadm trigger" means that the UUIDs are updated
for Grub to use, but it's clearly not a correct final solution.

Yet... in both cases in the post-installer runtime we're getting the
"change" events when I do the mkfs.

Is udev maybe built differently for the installer, or do we have some
missing config somewhere? Digging there next.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Every time you use Tcl, God kills a kitten." -- Malcolm Ray


buster-normal-udev.log.gz
Description: application/gzip


buster-installer-udev.log.gz
Description: application/gzip


stretch-normal-udev.log.gz
Description: application/gzip


stretch-installer-udev.log.gz
Description: application/gzip

Re: Debian Installer Buster RC 1 release

[Domenico Andreoli]

On Fri, Apr 19, 2019 at 12:37:56PM +0100, Steve McIntyre wrote:
> On Fri, Apr 19, 2019 at 01:12:43PM +0200, Miroslav Kure wrote:
> >On Mon, Apr 15, 2019 at 10:47:40PM +0200, Cyril Brulebois wrote:
> >> 
> >> This release includes Secure Boot support on amd64, which should work
> >> out of the box on most Secure Boot enabled machines. This means there
> >> should be no need to disable Secure Boot support in the firmware
> >> configuration anymore.
> >
> >I have this little HP EliteDesk 705 G2 Desktop Mini and trying to boot
> >the RC1 installer[1] from usb stick with Secure Boot enabled:

I have an HP EliteBook 850 G3. It's completely locked up with SB enabled
(BIOS is password protected and I've not access to it). Luckily I can
choose the boot device and I can boot a carefully installed USB3 SSD
(Debian + Ubuntu shim). Of course it boots also the pre-installed
Windows 10.

> >
> > 1) d-i boot menu appears (in the past - alpha3 - even this step failed
> >on this machine something along "no bootloader found")

yes, I can see the GRUB menu and also the "booting in insecure mode"
that happears right before it.

> >
> > 2) no matter which option I choose (Graphical install, Advanced, ...)
> >the following error appears:
> >
> >error: /install.amd/vmlinuz has invalid signature.
> >error: you need to load the kernel first.
> >  
> >Press any key to continue

yes, I also get this same error independently from the choice is select.

> 
> Hmmm, odd. Have you done anything special with the SB key setup on
> this machine, like reset the keys database or similar?

I did not do any of these actions (BIOS is locked etc etc). I doubt
that any custom key has been installed, the Ubuntu shim works and,
once it is confiured so to ignore the kernel signature, it also boots
my existing SSD.

> 
> >The usb stick seems to be created correctly as installation on my
> >other machine (although no Secure Boot there) works as expected.

I cannot state this, it is the first time I use this stick. Anyway
I'm sure it's the Buster RC1, it's in the grub description.

thanks,
Dom

-- 
3B10 0CA1 8674 ACBA B4FE  FCD2 CE5B CF17 9960 DE13


signature.asc
Description: PGP signature

Re: Bug#927376: haveged: please ship haveged-udeb to help solve entropy starvation in debian-installer

[Cyril Brulebois]

Hi,

Jérémy Bobbio  (2019-04-18):
> Go ahead. I trust you to do the right thing!

Thanks for the vote of confidence!

I've double checked again, and that still looks satisfactory inside d-i;
just uploaded 1.9.1-7 which should be hitting NEW in a moment.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#914712: Add the touchpad drivers to be able to use any compatible touchpad during the installations

[Cyril Brulebois]

Control: tag -1 - d-i + moreinfo

Hi,

21na...@gmail.com <21na...@gmail.com> (2018-11-26):
> Package: debian-installer
> Severity: important
> Tags: d-i

What hardware is this? We have touchpad drivers already, but some bits
can be missing (see #926057).
 

Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: Re: Bug#914712: Add the touchpad drivers to be able to use any compatible touchpad during the installations

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - d-i + moreinfo
Bug #914712 [debian-installer] Add the touchpad drivers to be able to use any 
compatible touchpad during the installations
Removed tag(s) d-i.
Bug #914712 [debian-installer] Add the touchpad drivers to be able to use any 
compatible touchpad during the installations
Added tag(s) moreinfo.

-- 
914712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#927437: unblock: openssl/1.1.1b-2

[Kurt Roeckx]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

Can you please unblock openssl. It fixes 2 important bugs.
debdiff attached.


Kurt

diff -Nru openssl-1.1.1b/debian/changelog openssl-1.1.1b/debian/changelog
--- openssl-1.1.1b/debian/changelog 2019-02-26 19:52:12.0 +0100
+++ openssl-1.1.1b/debian/changelog 2019-04-16 21:31:11.0 +0200
@@ -1,3 +1,11 @@
+openssl (1.1.1b-2) unstable; urgency=medium
+
+  * Fix BUF_MEM regression (Closes: #923516)
+  * Fix error when config can't be opened (Closes: #926315)
+  * Ship an openssl.cnf in libssl1.1-udeb.dirs
+
+ -- Kurt Roeckx   Tue, 16 Apr 2019 21:31:11 +0200
+
 openssl (1.1.1b-1) unstable; urgency=medium
 
   [ Sebastian Andrzej Siewior ]
diff -Nru openssl-1.1.1b/debian/libcrypto1.1-udeb.dirs 
openssl-1.1.1b/debian/libcrypto1.1-udeb.dirs
--- openssl-1.1.1b/debian/libcrypto1.1-udeb.dirs2019-02-26 
19:25:16.0 +0100
+++ openssl-1.1.1b/debian/libcrypto1.1-udeb.dirs2019-04-16 
21:31:11.0 +0200
@@ -1 +1,2 @@
 usr/lib
+usr/lib/ssl
diff -Nru 
openssl-1.1.1b/debian/patches/0001-Fix-for-BIO_get_mem_ptr-and-related-regressions.patch
 
openssl-1.1.1b/debian/patches/0001-Fix-for-BIO_get_mem_ptr-and-related-regressions.patch
--- 
openssl-1.1.1b/debian/patches/0001-Fix-for-BIO_get_mem_ptr-and-related-regressions.patch
1970-01-01 01:00:00.0 +0100
+++ 
openssl-1.1.1b/debian/patches/0001-Fix-for-BIO_get_mem_ptr-and-related-regressions.patch
2019-04-16 21:23:57.0 +0200
@@ -0,0 +1,118 @@
+From 43bb4dec99f4bed1ec20836c79967ea790594fce Mon Sep 17 00:00:00 2001
+From: Tomas Mraz 
+Date: Wed, 3 Apr 2019 12:31:32 +0200
+Subject: [PATCH 1/5] Fix for BIO_get_mem_ptr and related regressions
+
+Reviewed-by: Bernd Edlinger 
+Reviewed-by: Matt Caswell 
+(Merged from https://github.com/openssl/openssl/pull/8649)
+
+(cherry picked from commit b238fb79709a180ba9b4d837101c9f75e2978dc0)
+---
+ crypto/bio/bss_mem.c | 40 
+ 1 file changed, 28 insertions(+), 12 deletions(-)
+
+diff --git a/crypto/bio/bss_mem.c b/crypto/bio/bss_mem.c
+index 10fcbf7a7c..abf0f04111 100644
+--- a/crypto/bio/bss_mem.c
 b/crypto/bio/bss_mem.c
+@@ -57,7 +57,12 @@ static const BIO_METHOD secmem_method = {
+ NULL,  /* mem_callback_ctrl */
+ };
+ 
+-/* BIO memory stores buffer and read pointer  */
++/*
++ * BIO memory stores buffer and read pointer
++ * however the roles are different for read only BIOs.
++ * In that case the readp just stores the original state
++ * to be used for reset.
++ */
+ typedef struct bio_buf_mem_st {
+ struct buf_mem_st *buf;   /* allocated buffer */
+ struct buf_mem_st *readp; /* read pointer */
+@@ -192,6 +197,8 @@ static int mem_read(BIO *b, char *out, int outl)
+ BIO_BUF_MEM *bbm = (BIO_BUF_MEM *)b->ptr;
+ BUF_MEM *bm = bbm->readp;
+ 
++if (b->flags & BIO_FLAGS_MEM_RDONLY)
++bm = bbm->buf;
+ BIO_clear_retry_flags(b);
+ ret = (outl >= 0 && (size_t)outl > bm->length) ? (int)bm->length : outl;
+ if ((out != NULL) && (ret > 0)) {
+@@ -241,29 +248,36 @@ static long mem_ctrl(BIO *b, int cmd, long num, void 
*ptr)
+ BIO_BUF_MEM *bbm = (BIO_BUF_MEM *)b->ptr;
+ BUF_MEM *bm;
+ 
++if (b->flags & BIO_FLAGS_MEM_RDONLY)
++bm = bbm->buf;
++else
++bm = bbm->readp;
++
+ switch (cmd) {
+ case BIO_CTRL_RESET:
+ bm = bbm->buf;
+ if (bm->data != NULL) {
+-/* For read only case reset to the start again */
+-if ((b->flags & BIO_FLAGS_MEM_RDONLY) || (b->flags & 
BIO_FLAGS_NONCLEAR_RST)) {
+-bm->length = bm->max;
++if (!(b->flags & BIO_FLAGS_MEM_RDONLY)) {
++if (b->flags & BIO_FLAGS_NONCLEAR_RST) {
++bm->length = bm->max;
++} else {
++memset(bm->data, 0, bm->max);
++bm->length = 0;
++}
++*bbm->readp = *bbm->buf;
+ } else {
+-memset(bm->data, 0, bm->max);
+-bm->length = 0;
++/* For read only case just reset to the start again */
++*bbm->buf = *bbm->readp;
+ }
+-*bbm->readp = *bbm->buf;
+ }
+ break;
+ case BIO_CTRL_EOF:
+-bm = bbm->readp;
+ ret = (long)(bm->length == 0);
+ break;
+ case BIO_C_SET_BUF_MEM_EOF_RETURN:
+ b->num = (int)num;
+ break;
+ case BIO_CTRL_INFO:
+-bm = bbm->readp;
+ ret = (long)bm->length;
+ if (ptr != NULL) {
+ pptr = (char **)ptr;
+@@ -278,8 +292,9 @@ static long mem_ctrl(BIO *b, int cmd, long num, void *ptr)
+ break;
+ case BIO_C_GET_BUF_MEM_PTR:
+ if (ptr != NULL) {
+-mem_buf_sync(b);
+-bm = bbm->readp;
++if (!(b->flags & BIO_FLAGS_MEM_RDONLY))
++mem_buf_sync(b);
++   

Bug#927440: Debian 10 RC1 successfuly installed at AMD-A10 Desktop

[Bernhard]

Package: installation-reports

Boot method: USB-Drive
Image version: Self-made installation image with Debian 10 RC1
Date: 2019-04-19

Machine: Self-made desktop PC with AMD-A10
Processor: AMD A10-5700 APU with Radeon(tm) HD Graphics
Memory: 4GB
Partitions: 

> DateisystemTyp  1K-Blöcke  Benutzt Verfügbar Verw% Eingehängt auf
> udev   devtmpfs   15887080   15887080% /dev
> tmpfs  tmpfs   321056 48883161682% /run
> /dev/sda1  ext4 111556948 18176128  87670996   18% /
> tmpfs  tmpfs  160527225112   15801602% /dev/shm
> tmpfs  tmpfs 51204  51161% /run/lock
> tmpfs  tmpfs  16052720   16052720% /sys/fs/cgroup
> tmpfs  tmpfs   321052   763209761% /run/user/1000

Output of lspci -knn:

> 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
> (Models 10h-1fh) Processor Root Complex [1022:1410]
>   Subsystem: ASUSTeK Computer Inc. Family 15h (Models 10h-1fh) Processor 
> Root Complex [1043:8526]
> 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
> [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901]
>   Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7660D] [1043:8526]
>   Kernel driver in use: radeon
>   Kernel modules: radeon
> 00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity 
> HDMI Audio Controller [1002:9902]
>   Subsystem: ASUSTeK Computer Inc. Trinity HDMI Audio Controller 
> [1043:8526]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel
> 00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> XHCI Controller [1022:7812] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. FCH USB XHCI Controller [1043:8527]
>   Kernel driver in use: xhci_hcd
>   Kernel modules: xhci_pci
> 00:10.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> XHCI Controller [1022:7812] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. FCH USB XHCI Controller [1043:8527]
>   Kernel driver in use: xhci_hcd
>   Kernel modules: xhci_pci
> 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA 
> Controller [AHCI mode] [1022:7801] (rev 40)
>   Subsystem: ASUSTeK Computer Inc. FCH SATA Controller [AHCI mode] 
> [1043:8527]
>   Kernel driver in use: ahci
>   Kernel modules: ahci
> 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> OHCI Controller [1022:7807] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. FCH USB OHCI Controller [1043:8527]
>   Kernel driver in use: ohci-pci
>   Kernel modules: ohci_pci
> 00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> EHCI Controller [1022:7808] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. FCH USB EHCI Controller [1043:8527]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> OHCI Controller [1022:7807] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. FCH USB OHCI Controller [1043:8527]
>   Kernel driver in use: ohci-pci
>   Kernel modules: ohci_pci
> 00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> EHCI Controller [1022:7808] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. FCH USB EHCI Controller [1043:8527]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
> [1022:780b] (rev 14)
>   Subsystem: ASUSTeK Computer Inc. FCH SMBus Controller [1043:8527]
>   Kernel driver in use: piix4_smbus
>   Kernel modules: i2c_piix4, sp5100_tco
> 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
> Controller [1022:780d] (rev 01)
>   Subsystem: ASUSTeK Computer Inc. F2A85-M Series [1043:8444]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel
> 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge 
> [1022:780e] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. FCH LPC Bridge [1043:8527]
> 00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge 
> [1022:780f] (rev 40)
> 00:15.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Hudson PCI to 
> PCI bridge (PCIE port 0) [1022:43a0]
>   Kernel driver in use: pcieport
> 00:15.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Hudson PCI to 
> PCI bridge (PCIE port 1) [1022:43a1]
>   Kernel driver in use: pcieport
> 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
> (Models 10h-1fh) Processor Function 0 [1022:1400]
> 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
> (Models 10h-1fh) Processor Function 1 [1022:1401]
> 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
> (Models 10h-1fh) Processor Function 2 [

Re: Bug#927437: unblock: openssl/1.1.1b-2

[Cyril Brulebois]

Hi Kurt,

Kurt Roeckx  (2019-04-19):
> Can you please unblock openssl. It fixes 2 important bugs.
> debdiff attached.

(And thanks for the cc.)

I have been able to confirm during my work on haveged (#923675) that
your upload indeed fixes the wget issues we had in d-i (#926315); so
thanks also for that, and no objections on the d-i side regarding the
unblock request.

> diff -Nru openssl-1.1.1b/debian/changelog openssl-1.1.1b/debian/changelog
> --- openssl-1.1.1b/debian/changelog   2019-02-26 19:52:12.0 +0100
> +++ openssl-1.1.1b/debian/changelog   2019-04-16 21:31:11.0 +0200
> @@ -1,3 +1,11 @@
> +openssl (1.1.1b-2) unstable; urgency=medium
> +
> +  * Fix BUF_MEM regression (Closes: #923516)
> +  * Fix error when config can't be opened (Closes: #926315)
> +  * Ship an openssl.cnf in libssl1.1-udeb.dirs

The last entry is slightly odd, as that's the parent directory
(/usr/lib/ssl) for openssl.cnf that's being added to its fellow
companion (libcrypto1.1-udeb.dirs), rather than libssl1.1-udeb.dirs
itself? The changelog entry could be fixed in the next upload though,
not a huge issue.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#927440: marked as done (Debian 10 RC1 successfuly installed at AMD-A10 Desktop)

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2019 02:13:12 +0200
with message-id <20190420001312.v6lteychpe2bz...@mraw.org>
and subject line Re: Bug#927440: Debian 10 RC1 successfuly installed at AMD-A10 
Desktop
has caused the Debian Bug report #927440,
regarding Debian 10 RC1 successfuly installed at AMD-A10 Desktop
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: USB-Drive
Image version: Self-made installation image with Debian 10 RC1
Date: 2019-04-19

Machine: Self-made desktop PC with AMD-A10
Processor: AMD A10-5700 APU with Radeon(tm) HD Graphics
Memory: 4GB
Partitions: 

> DateisystemTyp  1K-Blöcke  Benutzt Verfügbar Verw% Eingehängt auf
> udev   devtmpfs   15887080   15887080% /dev
> tmpfs  tmpfs   321056 48883161682% /run
> /dev/sda1  ext4 111556948 18176128  87670996   18% /
> tmpfs  tmpfs  160527225112   15801602% /dev/shm
> tmpfs  tmpfs 51204  51161% /run/lock
> tmpfs  tmpfs  16052720   16052720% /sys/fs/cgroup
> tmpfs  tmpfs   321052   763209761% /run/user/1000

Output of lspci -knn:

> 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
> (Models 10h-1fh) Processor Root Complex [1022:1410]
>   Subsystem: ASUSTeK Computer Inc. Family 15h (Models 10h-1fh) Processor 
> Root Complex [1043:8526]
> 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
> [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901]
>   Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7660D] [1043:8526]
>   Kernel driver in use: radeon
>   Kernel modules: radeon
> 00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity 
> HDMI Audio Controller [1002:9902]
>   Subsystem: ASUSTeK Computer Inc. Trinity HDMI Audio Controller 
> [1043:8526]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel
> 00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> XHCI Controller [1022:7812] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. FCH USB XHCI Controller [1043:8527]
>   Kernel driver in use: xhci_hcd
>   Kernel modules: xhci_pci
> 00:10.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> XHCI Controller [1022:7812] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. FCH USB XHCI Controller [1043:8527]
>   Kernel driver in use: xhci_hcd
>   Kernel modules: xhci_pci
> 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA 
> Controller [AHCI mode] [1022:7801] (rev 40)
>   Subsystem: ASUSTeK Computer Inc. FCH SATA Controller [AHCI mode] 
> [1043:8527]
>   Kernel driver in use: ahci
>   Kernel modules: ahci
> 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> OHCI Controller [1022:7807] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. FCH USB OHCI Controller [1043:8527]
>   Kernel driver in use: ohci-pci
>   Kernel modules: ohci_pci
> 00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> EHCI Controller [1022:7808] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. FCH USB EHCI Controller [1043:8527]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> OHCI Controller [1022:7807] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. FCH USB OHCI Controller [1043:8527]
>   Kernel driver in use: ohci-pci
>   Kernel modules: ohci_pci
> 00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> EHCI Controller [1022:7808] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. FCH USB EHCI Controller [1043:8527]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
> [1022:780b] (rev 14)
>   Subsystem: ASUSTeK Computer Inc. FCH SMBus Controller [1043:8527]
>   Kernel driver in use: piix4_smbus
>   Kernel modules: i2c_piix4, sp5100_tco
> 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
> Controller [1022:780d] (rev 01)
>   Subsystem: ASUSTeK Computer Inc. F2A85-M Series [1043:8444]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel
> 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH 

Processed: Bug #923675 in debian-installer marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #923675 [debian-installer] debian-installer: consider using haveged to 
gather entropy
Added tag(s) pending.

-- 
923675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#923675: debian-installer: consider using haveged to gather entropy

[Cyril Brulebois]

Control: tag -1 patch pending

Hi,

Ben Hutchings  (2019-04-17):
> Ideally it would only be used if there isn't a hardware RNG available.
> Currently we don't include any hardware RNG modules in udebs, but that
> can be changed.  So please first check that:
> 
> * /sys/devices/virtual/misc/hw_random/rng_current is absent or
>   contains "none"
> * (x86 only) /proc/cpuinfo does not mention rdrand (I can't find an
>   arch-independent way to check for this, and Linux doesn't yet
>   support an equivalent feature on any other architecture)
> 
> Something like this should work:
> 
> if [ "$(cat /sys/devices/virtual/misc/hw_random/rng_current 2>/dev/null || 
> echo none)" = none ] \
>&& ! grep -q '^flags\b.*\brdrand\b' /proc/cpuinfo; then
> # use software entropy daemon
> fi

Many thanks for your input and for the suggested implementation.

I've tweaked it a little so that we log whether haveged is available,
and whether it should be started, in case we need to investigate:
  
https://salsa.debian.org/installer-team/rootskel/blob/master/src/lib/debian-installer-startup.d/S50entropy-source


I think I've tested all cases:
 - when haveged-udeb hasn't been added to src:debian-installer's
   pkg-lists yet
 - with the default Skylake-Client in libvirt, which leads to an rdrand
   CPU flag;
 - with a core2duo CPU instead, which has no such flag;
 - with the same CPU, but with a VirtIO RNG enabled, and those extra
   kernel modules in my netboot-gtk image:
 lib/modules/4.19.0-4-amd64/kernel/drivers/char/hw_random/rng-core.ko
 lib/modules/4.19.0-4-amd64/kernel/drivers/char/hw_random/virtio-rng.ko
 lib/modules/4.19.0-4-amd64/kernel/drivers/virtio/virtio.ko
 lib/modules/4.19.0-4-amd64/kernel/drivers/virtio/virtio_ring.ko
   which leads to a virtio_rng.0 in …/hw_random/rng_current.


So I've just uploaded a new version of rootskel (1.129), and pushed a
new commit to debian-installer:
  
https://salsa.debian.org/installer-team/debian-installer/commit/c470001925d067b42cdf613339634f4d54ed01b6

The haveged-udeb addition was already uploaded and also ACCEPTED from
NEW. I'll keep an eye on the daily builds.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: Re: Bug#923675: debian-installer: consider using haveged to gather entropy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch pending
Bug #923675 [debian-installer] debian-installer: consider using haveged to 
gather entropy
Added tag(s) patch.

-- 
923675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processing of rootskel_1.129_source.changes

[Debian FTP Masters]

rootskel_1.129_source.changes uploaded successfully to localhost
along with the files:
  rootskel_1.129.dsc
  rootskel_1.129.tar.xz
  rootskel_1.129_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

rootskel_1.129_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 20 Apr 2019 02:24:53 +0200
Source: rootskel
Binary: rootskel
Architecture: source
Version: 1.129
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Description:
 rootskel   - Skeleton root filesystem used by debian-installer (udeb)
Changes:
 rootskel (1.129) unstable; urgency=medium
 .
   * S50entropy-source: start haveged when appropriate, to avoid entropy
 starvation (See: #923675). This means when the haveged binary is
 available, and when there's no hardware RNG available.
Checksums-Sha1:
 b08506d599f24b1954fcccbf3231793776bf60ae 1744 rootskel_1.129.dsc
 1d2cf3161b3b861130cf02cc51253126f09629e1 33424 rootskel_1.129.tar.xz
 81f955f679acff2f88cc9a5f00aad994b52b225c 5787 rootskel_1.129_source.buildinfo
Checksums-Sha256:
 13c991f6e591f954d62b2a4a3f2b4c01050631e3c32c844a7f37cb2f07075a81 1744 
rootskel_1.129.dsc
 322538b2b7fd1243bd1802f06bce70626dd41d60598c321d5f2cdcec47f6b3e1 33424 
rootskel_1.129.tar.xz
 a9b24486082d9bef7a71b2153d7bfcb2b34cb331000304e8531e9f8cd89c3ca8 5787 
rootskel_1.129_source.buildinfo
Files:
 4e400b3835d328f23fd773562e44c8a5 1744 debian-installer standard 
rootskel_1.129.dsc
 1a972f48613dca64496aaee0a2d9555f 33424 debian-installer standard 
rootskel_1.129.tar.xz
 c979cd6144db7dc90d3b6e2092a959a7 5787 debian-installer standard 
rootskel_1.129_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAly6ZyYACgkQ/5FK8MKz
VSD3sw/5Ae63wcW9wxGkx0uXfBN1loJAt2bGe9v6ZDSQqiVGEjuG6KKoicJ3cPpi
6B+pL74Y1h2Dw2eXFiXlYP4NZzRHUepb662b9Lu4S3i8FXHSHS3fiwgLoqhIz/c/
XWbi7iaOX8WXxizp+PzIzq9zNOHfpL43nCU83hzSBzCsWeBCxkZMVYW/bm/F9Rey
BiC72tBrPWGwkYMawFWhaZTM2eJ2jlGEm/oZTbyiCoZgIneLiirTWC9zI26f0rf3
Hw0A1mlY6BcobHT9oUB6fgfeeFu9LXkBjyjb/ZAj9udbhK8+Kq+KgESQQh8UzMgm
G6VoQc0pQoainrL+FE45W71jhIupq00j6jRmokRZgX1CciS5TjY5NDbWmRUeYk+y
gRAZXA16pFXGOsa+ChLqSdZzFtYh/6LMqhViNv/NxmngTw0nDTk3Lu23Qm7Qfvvy
NblumvzGijSRdQTRjNpZ62JMQP0myDWB0OfWOh0cetD7lsxhCTFBpRJ1GkOZ1XAD
aRgFzRVM0QLHZhNY+aMV/TkTOtb/drx5ygrsMeyPREQ3i41WFJGg2TxULPCY59P6
Hkjl9sBl/iJ8269bkU2c0LwGePwBcJakl5LugkjgtsMxK9pxqGv9H1uxAJeMP5Hw
cmOyqzMSulonDZ2H+ACuAgodTluUyKqbxXSbU/C7q7DosLz6AZs=
=4k5Q
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Re: Bug#927437: unblock: openssl/1.1.1b-2

[Niels Thykier]

Cyril Brulebois:
> Hi Kurt,
> 
> Kurt Roeckx  (2019-04-19):
>> Can you please unblock openssl. It fixes 2 important bugs.
>> debdiff attached.
> 
> (And thanks for the cc.)
> 
> I have been able to confirm during my work on haveged (#923675) that
> your upload indeed fixes the wget issues we had in d-i (#926315); so
> thanks also for that, and no objections on the d-i side regarding the
> unblock request.
> 
>> diff -Nru openssl-1.1.1b/debian/changelog openssl-1.1.1b/debian/changelog
>> --- openssl-1.1.1b/debian/changelog  2019-02-26 19:52:12.0 +0100
>> +++ openssl-1.1.1b/debian/changelog  2019-04-16 21:31:11.0 +0200
>> @@ -1,3 +1,11 @@
>> +openssl (1.1.1b-2) unstable; urgency=medium
>> +
>> +  * Fix BUF_MEM regression (Closes: #923516)
>> +  * Fix error when config can't be opened (Closes: #926315)
>> +  * Ship an openssl.cnf in libssl1.1-udeb.dirs
> 
> The last entry is slightly odd, as that's the parent directory
> (/usr/lib/ssl) for openssl.cnf that's being added to its fellow
> companion (libcrypto1.1-udeb.dirs), rather than libssl1.1-udeb.dirs
> itself? The changelog entry could be fixed in the next upload though,
> not a huge issue.
> 
> 
> Cheers,
> 

Unblocked, thanks.
~Niels