public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: rng-tools PKCS#11 and rtlsdr
Date: Tue, 06 Oct 2020 15:19:11 +0200	[thread overview]
Message-ID: <a38ede7c484b71d85dcc48cc7e72ffb422ed6e50.camel@ipfire.org> (raw)
In-Reply-To: <76CC7BD2-DC12-47FA-B824-AE7DEADFCB1E@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

Hi Michael,
alright will disable it then.

Best,

Erik

Am Dienstag, den 06.10.2020, 12:57 +0100 schrieb Michael Tremer:
> Hello Erik,
> 
> I would say that we can disable both things.
> 
> We do not encourage people to add any SDRs and we do not need any
> PKCS#11 support here either. rngd isn’t very useful at all any more,
> and we should not encourage people to feed arbitrary entropy into
> their pools.
> 
> -Michael
> 
> > On 5 Oct 2020, at 17:31, ummeegge <ummeegge(a)ipfire.org> wrote:
> > 
> > Hi all,
> > am currently updating the rng-tools and there are some new compile
> > options needed to compile it.
> > 
> >  --without-pkcs11        Disable pkcs11 support.
> >  --without-rtlsdr        Disable rtlsdr support.
> > 
> > so a question arises for me, should we enable Smartcards -->
> > https://github.com/OpenSC/OpenSC/wiki
> > and also DVB dongles as entropy resources -->
> > https://github.com/librtlsdr/librtlsdr
> > for the rng-tools --> https://github.com/nhorman/rng-tools/releases
> >  in
> > IPFire, whereby two new libs are needed ?
> > 
> > Best,
> > 
> > Erik
> > 
> 
> 


      reply	other threads:[~2020-10-06 13:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 16:31 ummeegge
2020-10-06 11:57 ` Michael Tremer
2020-10-06 13:19   ` ummeegge [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a38ede7c484b71d85dcc48cc7e72ffb422ed6e50.camel@ipfire.org \
    --to=ummeegge@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox