Processing changes file: linux_3.16.51-3+deb8u1_mipsel.changes
ACCEPT
Processing changes file: linux_3.16.51-3+deb8u1_ppc64el.changes
ACCEPT
Processing changes file: linux_3.16.56-1_multi.changes
ACCEPT
Processing changes file: linux_3.16.56-1_amd64.changes
ACCEPT
Processing changes file: l
On Thu, 2018-05-10 at 10:41 -0700, Russ Allbery wrote:
> It means that the configured timeout for which it's reasonable to wait for
> randomness is centralized in one service that can set that based on
> understanding of what's necessary in practice, and timeouts to catch other
> startup problems
On Thu, May 10, 2018 at 07:30:46PM +0200, Michael Biebl wrote:
>
> So we'd shift the waiting for randomness-to-be-available from one
> service to another? I don't quite see yet, where the benefit is in that.
> What's better if a wait-for-rng-ready binary blocks on getrandom()
> instead of the krb5
On 5/10/18 7:30 PM, Michael Biebl wrote:
> So we'd shift the waiting for randomness-to-be-available from one
> service to another? I don't quite see yet, where the benefit is in that.
> What's better if a wait-for-rng-ready binary blocks on getrandom()
> instead of the krb5-kdc binary itself? We wo
Michael Biebl writes:
> Am 10.05.2018 um 19:22 schrieb Russ Allbery:
>> I may be misunderstanding the nature of the issue, but I believe that a
>> Type=oneshot service that runs a small C program that calls getrandom()
>> and then exit(0) when it returns would provide a useful facility.
>> krb5-k
Hi Russ
Am 10.05.2018 um 19:22 schrieb Russ Allbery:
> Michael Biebl writes:
>> Am 10.05.2018 um 00:46 schrieb Ben Hutchings:
>
>>> One of the krb5 maintainers (Benjamin Kaduk) favours option 2b, and
>>> also proposed that systemd could provide a wait-for-rng-ready unit to
>>> support this.
>
>
Michael Biebl writes:
> Am 10.05.2018 um 00:46 schrieb Ben Hutchings:
>> One of the krb5 maintainers (Benjamin Kaduk) favours option 2b, and
>> also proposed that systemd could provide a wait-for-rng-ready unit to
>> support this.
> What exactly would such a wait-for-rng-ready service do and how
On 2018-03-25 21:51 +0200, Sven Joachim wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> I would like to start a transition for ncurses, changing the soname of
> the libraries from 5 to 6.
The results thus far look q
Am 10.05.2018 um 00:46 schrieb Ben Hutchings:
> 1. Add entropy to the kernel during boot; either:
>a. Improve systemd-random-seed
>b. Recommend use of haveged
> 2. For each affected userland package, either:
>a. Revert to using /dev/urandom
>b. Tolerate a longer wait for getrandom(
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
libtermkey1 on kfrebsd currently depends on libunibilium0, which is not
installable. It has to be rebuilt against libunibilium4.
nmu libtermkey_0.20-3 . kfreebsd-amd64 kfreebsd-i386 . unstab
Package: release.debian.org
Severity: normal
As quoted in Debian Bug #898151
bpfcc didn't migrate to testing. I see you have tried to request RoM
but still not migrated. After consulting on #debian-dev
12:18 I think it is because arch-all packages are depending on
packages that only exist
11 matches
Mail list logo
