Rehi, On Mo, 2016-09-12 at 21:34 +0100, Santiago Vila wrote: > On Mon, Sep 12, 2016 at 07:34:09PM +0200, Daniel Kahn Gillmor wrote: > > > > > An even easier approach might be to do the following within the > > build: > > > > * ln -sf /dev/urandom /dev/random > > > > why would we need the blocking kernel RNG in the buildd anyway? > Either that, or maybe a build-depends on a package specifically > created to do that (as I'm not sure we could really ask all buildd > operators to make the symlink permanently). > > A good solution should be automatic and not need manual intervention, > and should be independent of the machine on which the build is done.
Exactly ;). > > Lastly, one other option for gnupg at least is to patch upstream to > > use > > --debug-quick-random in the build-time test. > > > > do any of these options sound more appealing than the others? > I didn't know about --debug-quick-random, it seems perfect to me. > > Stephan, do you think it would be possible to patch mini-buildd so > that --debug-quick-random is added to gnupg command line, but only > when the package is doing the tests following the build? Yeah, I will check this out (though it's not an option to gpg directly, afair). Or maybe going with a pre-generated key. Thx, S
