Bug#923675: Add related bug #916690 info

2019-04-16 Thread Daniel Lange

This is related to #916690.

getrandom() essentially blocks during many use cases where the system
does not have enough entropy. This is somewhat mitigated by the Debian 
kernel now trusting the RDRAND (CONFIG_RANDOM_TRUST_CPU) for AMD64 
(https://lists.debian.org/debian-devel/2019/02/msg00170.html) which has 
this CPU instruction on somewhat recent hardware. Other architectures 
and a number of virtualization setups on AMD64 are still running into 
this issue.


The Debian Installer variant of this issue is the hardest* to solve.
So I fear we're in "add it to the release notes"-land again.

For Bullseye (or a point release) we should solve the problem more 
comprehensively.


* The Debian Installer media cannot have a (carried over consecutive 
boots) seed file embedded. This makes it the hardest case to solve as 
one needs to "reach out" for entropy sources.
Downloading some random bytes from {random.org | random.debian.org} and 
feeding to the entropy pool proper (ioctl RNDADDENTROPY) would solve 
this for networked hosts, able to reach such an external entropy source. 
Of course there is an attack vector added by reaching out to the net. So 
this would need proper configurability to make it safe to use. Note: we 
cannot use cryptography to protect this ... the PRNG is the very thing 
in need of proper initialization here.
And for non-network hosts or ones shielded from the Internet and not run 
in a proper data center environment (that would probably supply a 
random.the-hoster.tld service) this will not improve the situation.


Thorsten Glaser (CC) has produced a prototype early-rng-init-tools (cf. 
https://lists.debian.org/debian-devel/2019/02/msg00327.html) which could 
be extended to try reading entropy off the network when it doesn't have 
a carried-over seed (as in the Debian Installer case).




Bug#927045: marked as done (^C doesn't work when booting into recovery mode)

2019-04-16 Thread Debian Bug Tracking System
Your message dated Tue, 16 Apr 2019 15:16:03 +0800
with message-id <87d0lma098.8@jidanni.org>
and subject line Re: Bug#927045: ^C doesn't work when booting into recovery mode
has caused the Debian Bug report #927045,
regarding ^C doesn't work when booting into recovery mode
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.)


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

Just want to let you know after a fresh install, when booting into
"(recovery mode)" from the grub menu, and typing the root passwd,
# cat
^C
doesn't interrupt cat, etc.
One needs ^Z, then "kill %" to stop it.

Yes, these just reported the same as on a normal fully working terminal:
# stty -a
speed 38400 baud; rows 48; columns 128; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ;
eol2 = ; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; discard = ^O; min = 1; time = 0;
-parenb -parodd -cmspar cs8 hupcl -cstopb cread -clocal -crtscts
-ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
-iuclc -ixany imaxbel iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke -flusho -extproc
# stty -g
6502:5:4bf:8a3b:3:1c:7f:15:4:0:1:0:11:13:1a:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0

So I don't know what the problem is.

Note I had only installed the packages contained on
Debian GNU/Linux 9.8.0 _Stretch_ - Official amd64 NETINST 20190216-11:59";
with no internet connection.

Sure, after adding more packages and rebooting, the problem went away.
So do try it with the bare bones install from just
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/
with no network connection to download extra packages.

The only other odd thing I did was add nomodeset to
linux   /boot/vmlinuz-4.9.0-8-amd64 ...
in grub.
--- End Message ---
--- Begin Message ---
OK thanks for testing. As I have already finished installation, I don't
want to test further, so will close this.--- End Message ---


Bug#926539: rootskel: steal-ctty no longer works on at least sparc64

2019-04-16 Thread John Paul Adrian Glaubitz
Hi Ben!

On 4/7/19 1:53 AM, Ben Hutchings wrote:
>> root@landau:~# cat /proc/consoles 
>> ttyHV0   -W- (EC p  )4:64
>> tty0 -WU (E )4:1
>> root@landau:~# readlink /sys/dev/char/4:64
>> ../../devices/root/f0299a70/f029b788/tty/ttyS0
> 
> The inconsistent name seems like a kernel bug...

Yes. I'm trying to convince Dave Miller to fix this.

Do you think we could carry a patch in src:linux for the time being?

>> root@landau:~#
>>
>> And this is what used to make it work [1]:
>>
>>  *) # >= 2.6.38
>>  console_major_minor="$(get-real-console-linux)"
>>  console_raw="$(readlink "/sys/dev/char/${console_major_minor}")"
>>  console="${console_raw##*/}"
>>  ;;
> 
> So maybe rootskel should use that again, but applied to each console's
> char device number.
> 
> (Though directly using the symlinks under /dev/char seems cleaner than
> poking in sysfs.)

I agree.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Bug#923675: Add related bug #916690 info

2019-04-16 Thread Petter Reinholdtsen
Debian Edu ran into this problem when installing Kerberos as a server from d-i, 
and solved it by running a process in the background to monitor the entropy 
level, 
and when it was running low, it would flush the file buffers and run 'find 
/target' to force some IO operations that would add entropy to the kernel.

The code can be found in
https://salsa.debian.org/debian-edu/debian-edu-config/blob/master/share/debian-edu-config/d-i/finish-install
 >
and look like this:


# Try to add entropy when running low
(
   cd /
   while true ; do
   entropy="$(cat /proc/sys/kernel/random/entropy_avail)"
   if [ 130 -gt "$entropy" ] ; then
   log "low on entropy, pool is $entropy. trying to add more"
   # Disk IO add entropy to the kernel.  Flush cache to ensure find and 
   # touch/rm causes disk IO.
   sync
   echo 3 > /proc/sys/vm/drop_caches
   find /target > /dev/null || true
   touch /target/var/tmp/foo
   sync
   rm /target/var/tmp/foo
   sync
   entropy="$(cat /proc/sys/kernel/random/entropy_avail)"
   log "entropy pool is $entropy after trying to add"
   fi
   sleep 20
   done ) < /dev/null 2>&1 3>/dev/null 4>&3 5>&3 6>&3 | logger -t 
edu-entropy-add 
& epid=$!

... install stuff ...

# Ignore errors in case the entropy gathering is no longer running
if kill $epid ; then
:
else
log "error: killing the entropy gathering job failed - exited?"
fi

Perhaps a similar approach could be inserted into the default Debian Installer?

-- 
Happy hacking
Petter Reinholdtsen



Bug#923675: Add related bug #916690 info

2019-04-16 Thread Ben Hutchings
On Tue, 2019-04-16 at 12:19 +0200, Petter Reinholdtsen wrote:
> Debian Edu ran into this problem when installing Kerberos as a server from 
> d-i, 
> and solved it by running a process in the background to monitor the entropy 
> level, 
> and when it was running low, it would flush the file buffers and run 'find 
> /target' to force some IO operations that would add entropy to the kernel.
[...]

This is a pretty terrible approach.  Especially as the world has moved
on to SSDs and they provide very little entropy from interrupts.

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered
an expert.



signature.asc
Description: This is a digitally signed message part


Bug#926539: rootskel: steal-ctty no longer works on at least sparc64

2019-04-16 Thread Ben Hutchings
On Tue, 2019-04-16 at 11:47 +0200, John Paul Adrian Glaubitz wrote:
> Hi Ben!
> 
> On 4/7/19 1:53 AM, Ben Hutchings wrote:
> > > root@landau:~# cat /proc/consoles 
> > > ttyHV0   -W- (EC p  )4:64
> > > tty0 -WU (E )4:1
> > > root@landau:~# readlink /sys/dev/char/4:64
> > > ../../devices/root/f0299a70/f029b788/tty/ttyS0
> > 
> > The inconsistent name seems like a kernel bug...
> 
> Yes. I'm trying to convince Dave Miller to fix this.
> 
> Do you think we could carry a patch in src:linux for the time being?
[...]

I would rather not do that until it's accepted, as if it that doesn't
happen we either have to switch back or carry it forever.

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered
an expert.




signature.asc
Description: This is a digitally signed message part


Bug#926539: rootskel: steal-ctty no longer works on at least sparc64

2019-04-16 Thread John Paul Adrian Glaubitz
On 4/16/19 1:16 PM, Ben Hutchings wrote:
>> Do you think we could carry a patch in src:linux for the time being?
> [...]
> 
> I would rather not do that until it's accepted, as if it that doesn't
> happen we either have to switch back or carry it forever.

Hmm, okay. Then I don't really have a way of building updated images
now for the time being.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Processed: severity of 926315 is serious, severity of 927165 is serious ..., usertagging 926315 ...

2019-04-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 926315 serious
Bug #926315 [openssl] openssl: wget https://google.com fails in d-i
Severity set to 'serious' from 'important'
> severity 927165 serious
Bug #927165 [debian-installer] debian-installer: improve support for LUKS
Severity set to 'serious' from 'important'
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 926315 buster-is-blocker
There were no usertags set.
Usertags are now: buster-is-blocker.
> usertags 927165 buster-is-blocker
There were no usertags set.
Usertags are now: buster-is-blocker.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
926315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926315
927165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#923675: Add related bug #916690 info

2019-04-16 Thread Petter Reinholdtsen
[Ben Hutchings]
> This is a pretty terrible approach.  Especially as the world has moved
> on to SSDs and they provide very little entropy from interrupts.

Absolutely.  But it has solved the  problem with too little entropy since 2011.
Do you have any better ways to force the kernel to add some entropy when running
low?

-- 
Happy hacking
Petter Reinholdtsen



Bug#923675: Add related bug #916690 info

2019-04-16 Thread Thorsten Glaser
Daniel Lange dixit:

> Thorsten Glaser (CC) has produced a prototype early-rng-init-tools (cf.
> https://lists.debian.org/debian-devel/2019/02/msg00327.html) which could be
> extended to try reading entropy off the network when it doesn't have a
> carried-over seed (as in the Debian Installer case).

Sorry, this is deliberately out of scope.

My early-rng-init-tools is exactly for the use case of carrying a random
seed between boots and making it available to the system earlier (as a
stopgap until all bootloaders support passing it to the kernel before
the latter is even run) and *deliberately* does not touch the part where
entropy is collected.

FWIW, downloading entropy can be done (we have this in the MirBSD
installer) but has privacy concerns, so it should perhaps be optional.
This is easily done in d-i components, except for the little fact that
busybox wget in d-i lacks https support.

I’ve built myself a locally patched 'monolith' installer with extra
entropy over the network, but that’s site-dependent.

Also, please don’t assume everyone has amd64. The m68k people will,
among others, thank you ;-)

bye,
//mirabilos
--  
When he found out that the m68k port was in a pretty bad shape, he did
not, like many before him, shrug and move on; instead, he took it upon
himself to start compiling things, just so he could compile his shell.
How's that for dedication. -- Wouter, about my Debian/m68k revival



Bug#923675: Add related bug #916690 info

2019-04-16 Thread Ben Hutchings
On Tue, 2019-04-16 at 13:57 +0200, Petter Reinholdtsen wrote:
> [Ben Hutchings]
> > This is a pretty terrible approach.  Especially as the world has moved
> > on to SSDs and they provide very little entropy from interrupts.
> 
> Absolutely.  But it has solved the  problem with too little entropy since 
> 2011.
> Do you have any better ways to force the kernel to add some entropy when 
> running
> low?

haveged or jitterentropy-rngd are likely to be better.

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered
an expert.



signature.asc
Description: This is a digitally signed message part


Re: Debian Installer Buster RC 1 release

2019-04-16 Thread Holger Wansing
Hi,

Cyril Brulebois  wrote:
> The Debian Installer team[1] is pleased to announce the first release
> candidate of the installer for Debian 10 "Buster".

Sadly, the latest version of tasksel has not been unblocked for migration to
Buster.
(I have been pointed on this by Wolfgang, subscriber of
'Bug#923975: task files should not recommend removed packages' )


Please consider tasksel for unblocking to get that included in Buster.
Thanks


Holger



> 
> Important change in this release
> 
> 
> 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.
> 
> 
> Improvements in this release
> 
> 
>  * apt-setup:
> - Adjust handling of media sets, improving support for Debian Edu.
>  * brltty:
> - Add support for Hedo MobiLine.
>  * cdebconf:
> - Disable paging in text frontend for now, espeakup does not
>   pronounce the keys to change pages (see #690343) and thus users
>   are confounded and think the first page are the only choices.
>  * cryptsetup:
> - The on-disk LUKS format version now defaults to LUKS2 (#919725).
>  * debian-installer:
> - Switch to using buster artwork for the splash screen.
> - Bump Linux kernel ABI from 4.19.0-1 to 4.19.0-4.
> - Improve build reproducibility (#900918, #920631, #920676).
> - gen-tarball: stop using the deprecated GZIP variable.
> - gen-tarball: use pigz automatically if it is available.
> - Add dark theme submenu and shortcut: 'd' (#820911).
> - Fix loading background image on netboot grub.
>  * debian-installer-utils:
> - Stop propagating BOOTIF to the installed system (#921444).
>  * espeakup:
> - Fix writing down sound card ID when the installation finishes.
>  * finish-install:
> - Add support for multiple consoles.
>  * grub-installer:
> - On Linux, mount/unmount /run to work around timeouts during LVM
>   initialization (#918590).
>  * grub2:
> - Fix setup on Secure Boot systems where cryptodisk is in use
>   (#917117).
> - Make grub-efi-amd64-signed recommend shim-signed (#919067).
> - Add help and ls modules to signed UEFI images (#919955).
> - grub-install: Check for arm-efi as a default target (#922104).
> - util: Detect more I/O errors, like insufficient space (#922741).
> - Use libefi* libraries to minimise writes to EFI variable storage
>   (#891434), instead of depending on efibootmgr. (The latter is
>   expected to come back in Recommends in a later release, since
>   that's a useful debugging tool.)
>  * hw-detect:
> - Use 'modprobe -qn' to query available modules (#870448).
>  * libxinerama:
> - Fix udeb dependencies (#921715).
>  * linux:
> - certs: Replace test signing certificate with production signing
>   certificate.
> - certs: include both root CA and direct signing certificate
>   (#924545).
>  * live-installer:
> - Add calamares-settings-debian as package to be removed at the
>   end of the installation.
>  * nano:
> - Add patch to avoid showing ^S and ^Q options in nano-tiny, as
>   using those can cause problems on some d-i environments, like
>   installs over serial console (#915017).
>  * network-console:
> - Drop “beep” support for arm*/ixp4xx and arm*/iop32x; it was used
>   to notify users their devices was ready to be installed, but
>   support for those platforms was removed from the Linux kernel
>   and therefore d-i (#921951).
>  * partman-base:
> - Make sure UUIDs are available in /dev/disk/by-uuid/ so that the
>   bootloader can be configured to use them (#852323).
>  * partman-lvm:
> - Really fix invalid characters in volume group names (#911036),
>   the the previous attempt was not entirely functional (#922230,
>   #922100).
>  * partman-partitioning:
> - Use GPT by default on armhf/efi, MSDOS otherwise.
>  * rootskel:
> - Make theme=dark install and enable Compiz in MATE.
> - Make theme=dark make grub use a dark theme.
> - Run d-i on multiple consoles independently where configured.
> - Add error-handling to steal-ctty.
> - Add early logging so we can later see what consoles are detected
>   and chosen.
>  * rootskel-gtk:
> - Integrate Buster theme: futureprototype.
>  * systemd:
> - udev: Run programs in the specified order (#925190).
> - udev: Prevent mass killings when not running under systemd
>   (#918764).


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: Debian Installer Buster RC 1 release

2019-04-16 Thread Cyril Brulebois
Hi,

Holger Wansing  (2019-04-16):
> Cyril Brulebois  wrote:
> > The Debian Installer team[1] is pleased to announce the first release
> > candidate of the installer for Debian 10 "Buster".
> 
> Sadly, the latest version of tasksel has not been unblocked for
> migration to Buster.
> (I have been pointed on this by Wolfgang, subscriber of
> 'Bug#923975: task files should not recommend removed packages' )
> 
> 
> Please consider tasksel for unblocking to get that included in Buster.

I'd be happy to have someone from the release team check it; so I'd
welcome an unblock request following the usual procedure. Thanks!


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


signature.asc
Description: PGP signature


Bug#923675: Add related bug #916690 info

2019-04-16 Thread Cyril Brulebois
Ben Hutchings  (2019-04-16):
> On Tue, 2019-04-16 at 13:57 +0200, Petter Reinholdtsen wrote:
> > [Ben Hutchings]
> > > This is a pretty terrible approach.  Especially as the world has moved
> > > on to SSDs and they provide very little entropy from interrupts.
> > 
> > Absolutely.  But it has solved the  problem with too little entropy since 
> > 2011.
> > Do you have any better ways to force the kernel to add some entropy when 
> > running
> > low?
> 
> haveged or jitterentropy-rngd are likely to be better.

The former was on my list of things to try; thanks for mentioning the latter.


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


signature.asc
Description: PGP signature


Re: Debian Installer Buster RC 1 release

2019-04-16 Thread Holger Wansing
Hi,

Cyril Brulebois  wrote:
> Hi,
> 
> Holger Wansing  (2019-04-16):
> > Cyril Brulebois  wrote:
> > > The Debian Installer team[1] is pleased to announce the first release
> > > candidate of the installer for Debian 10 "Buster".
> > 
> > Sadly, the latest version of tasksel has not been unblocked for
> > migration to Buster.
> > (I have been pointed on this by Wolfgang, subscriber of
> > 'Bug#923975: task files should not recommend removed packages' )
> > 
> > 
> > Please consider tasksel for unblocking to get that included in Buster.
> 
> I'd be happy to have someone from the release team check it; so I'd
> welcome an unblock request following the usual procedure. Thanks!

Done.


Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#923675: Add related bug #916690 info

2019-04-16 Thread Petter Reinholdtsen
[Ben Hutchings]
> haveged or jitterentropy-rngd are likely to be better.

Is there any hope to run them within d-i in Buster before /target/ is
set up?

-- 
Happy hacking
Petter Reinholdtsen



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

2019-04-16 Thread Cyril Brulebois
Control: retitle -1 debian-installer: consider using haveged to gather entropy

Cyril Brulebois  (2019-04-16):
> The former was on my list of things to try; thanks for mentioning the
> latter.

I'm no cryptographer so I cannot judge haveged from that angle.

But from a /proc/sys/kernel/random/entropy_avail standpoint, starting
the haveged daemon inside d-i, a couple of screens after the graphical
installer start-up, I'm getting a bump from ~150 to ~2500.

This needs to be polished before submitting the addition of haveged-udeb
and of course proper integration needs to happen, with real tests… For
wget, we're hitting #926315, but it was luckily closed a couple hours
ago; arm devices that need so much time to generate a keypair should get
a nice improvement…


My initial thought would be to launch it on demand when one is about to
get to wget calls that needs HTTPS; but we could probably benefit from
it in case HTTP is requested but redirections to HTTPS happens… There
are also the obvious keypair generations mentioned above. But then over
time maybe some other operations could be needing entropy (the
cryptsetup case is discussed in a separate thread[1]).

 1. https://lists.debian.org/debian-boot/2019/04/msg00153.html

So it might be best to start it unconditionally at start-up?


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


signature.asc
Description: PGP signature


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

2019-04-16 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 debian-installer: consider using haveged to gather entropy
Bug #923675 [debian-installer] debian-installer: delays when using an https 
mirror due to rng
Changed Bug title to 'debian-installer: consider using haveged to gather 
entropy' from 'debian-installer: delays when using an https mirror due to rng'.

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



Processing of partman-basicfilesystems_147_source.changes

2019-04-16 Thread Debian FTP Masters
partman-basicfilesystems_147_source.changes uploaded successfully to localhost
along with the files:
  partman-basicfilesystems_147.dsc
  partman-basicfilesystems_147.tar.xz
  partman-basicfilesystems_147_amd64.buildinfo

Greetings,

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



partman-basicfilesystems_147_source.changes ACCEPTED into unstable

2019-04-16 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 16 Apr 2019 23:26:01 +0200
Source: partman-basicfilesystems
Architecture: source
Version: 147
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 partman-basicfilesystems (147) unstable; urgency=medium
 .
   * Team upload
 .
   [ Updated translations ]
   * Arabic (ar.po) by Yaron Shahrabani
   * Hebrew (he.po) by Yaron Shahrabani
Checksums-Sha1:
 50ebf0742f95745327536d89278a383371303eb2 1834 partman-basicfilesystems_147.dsc
 29aaac84ef01c72784fa8f37fae6d3c22b3a041f 190432 
partman-basicfilesystems_147.tar.xz
 05e0003c7ee870aa840b8c2d106e2e0981e22fb1 5396 
partman-basicfilesystems_147_amd64.buildinfo
Checksums-Sha256:
 4cda248bea0a0b65fc0e4779206ee6b357961bf63b4742dca0a686abce2fa594 1834 
partman-basicfilesystems_147.dsc
 3f98fee3ceb79caeeac9f8f0e04225e6f79c52f9130cacb7763bba787b98d42b 190432 
partman-basicfilesystems_147.tar.xz
 a4ecb90353c7124bc6777f1ed0e01550e89a6202b76b6ea06bf13ed7bc21a636 5396 
partman-basicfilesystems_147_amd64.buildinfo
Files:
 4848fb9e1be291ef48b8c4631aa761e1 1834 debian-installer standard 
partman-basicfilesystems_147.dsc
 d750b1c17f093f71885b2e253958b372 190432 debian-installer standard 
partman-basicfilesystems_147.tar.xz
 aec2e3857139896abd8921393417cfe4 5396 debian-installer standard 
partman-basicfilesystems_147_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAly2SncVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2mGIQALoxLomZa1yl+uN1tD/X1IzK9W0C
Stg8Rl3amnVx0uQy+WKb08yhU08kH9KvMP3VID43obocLAwKt4Bw1wVhXzOUVSP9
JEs0RAS06HD3To74od9q+3n+dRkFSij6lNz8dbztiLAoTAI73o0VIeF2cb9OkLrR
19Tm+2yqlWfC6rVMHYfEHeiJCKqa3jZgD7sM4u6grU8ot5N7duX0QTb2eeiFnBZT
aha1AV7lDjzwP8LnVGd3+06EUne/E/VVseaOxzZTefdIEpqcFq6BKDNAyCake+3w
XprANKX1mslOcijS+rG/5nJvwhXUOYJ5Yp5zSPyDgBsUGMc1N3pAlC3KeyOtCbrr
dRyC3R/IJulLO8dmciyIvol59Vv46oyPL1lv5487xD5BBY+UjkAxniwKNoBt7O90
qKP9Rz5elykXoJ1j9nQxY69xxQh+ysO1gwuQIt/NCZ0FmgKtCj+gj70qGFTex5k5
kbcWUdDqTyFcqPFM4J6oEN7+PKaMQJxj6PBCXcYR4008jvKHWSUlSYYnEX6aejg0
j7rVP08TZIcDNi20IcML9xBS1iSZkmwHkBCj3CYQdSUFHz778d5tFya/8JxFiRfC
IfvTDaXzU9WgV9kTSTy247Tsi7SlxdAX8pA8796IUC/dgXLAAfaQ7Gsa1boQLy5l
LXbmgJuyPNxyLX4t
=DWTj
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



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

2019-04-16 Thread Steve McIntyre
On Tue, Apr 16, 2019 at 11:45:08PM +0200, Cyril Brulebois wrote:
>Cyril Brulebois  (2019-04-16):
>> The former was on my list of things to try; thanks for mentioning the
>> latter.

...

>My initial thought would be to launch it on demand when one is about to
>get to wget calls that needs HTTPS; but we could probably benefit from
>it in case HTTP is requested but redirections to HTTPS happens… There
>are also the obvious keypair generations mentioned above. But then over
>time maybe some other operations could be needing entropy (the
>cryptsetup case is discussed in a separate thread[1]).
>
> 1. https://lists.debian.org/debian-boot/2019/04/msg00153.html
>
>So it might be best to start it unconditionally at start-up?

I'd go with that, yes. What's the down-side?

I'm also pondering doing something similar with "udevadm monitor" -
start it unconditionally, logging to the installer syslog. It'd be a
good extra bit of debug to have.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Google-bait:   http://www.debian.org/CD/free-linux-cd
  Debian does NOT ship free CDs. Please do NOT contact the mailing
  lists asking us to send them to you.



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

2019-04-16 Thread Jonathan Carter
On 2019/04/16 23:45, Cyril Brulebois wrote:
> I'm no cryptographer so I cannot judge haveged from that angle.

Ditto here, but...

> But from a /proc/sys/kernel/random/entropy_avail standpoint, starting
> the haveged daemon inside d-i, a couple of screens after the graphical
> installer start-up, I'm getting a bump from ~150 to ~2500.
> 
> This needs to be polished before submitting the addition of haveged-udeb
> and of course proper integration needs to happen, with real tests… For
> wget, we're hitting #926315, but it was luckily closed a couple hours
> ago; arm devices that need so much time to generate a keypair should get
> a nice improvement…

Yeah debian-live was unusable without haveged (as in, some sessions
wouldn't start up for hours unless users pounded on the keyboard for a
while). Some people quickly get hand-wavy about haveged, but it seems
like the theory of how it works is reasonably solid and I really tried
to find evidence of it being harmful or not generating enough randomness
in typical use cases, but couldn't find anything, so we went ahead and
included it in the live media and it seems to work for us there.

Debian's official documentation probably just needs a section explaining
what haveged is and that if someone needs to create a mass amount of
keys for commercial applications or such then it's really recommended
that they get a decent hardware RNG or use an external service to seed that.

-Jonathan