version and parameter divergence from Debian

Bug #1333293 reported by Thorsten Glaser
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rng-tools (Debian)
Fix Released
Unknown
rng-tools (Ubuntu)
Won't Fix
Wishlist
Dimitri John Ledkov

Bug Description

The command line parametres “rngd” takes differ between Debian and *buntu, which leads to loss of operation (rng stream import no longer works, leading to loss of entropy on devices) and script failures in the latter:

*buntu

 [-d, --no-drng=1|0]
 [-n, --no-tpm=1|0]
 [-q, --quiet]
 [-v, --verbose]

debian

 [-B n | --rng-buffers=n]
 [--hrng=name]
 [-R name | --rng-driver=name]
 [-H n.nnn | --rng-entropy=n.nnn]
 [-Q quality | --rng-quality=quality]
 [-T n | --rng-timeout=n]
 [-t n | --feed-interval=n]

The other parametres are the same.

Please fix this by updating to the Debian version of this package.

information type: Private Security → Public Security
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

The debian package is very out of date, so I don't think this bug report makes sense.

In any case, it's not a security issue.

information type: Public Security → Public
Revision history for this message
Thorsten Glaser (mirabilos) wrote : Re: [Bug 1333293] Re: version and parameter divergence from Debian

Marc Deslauriers dixit:

>The debian package is very out of date, so I don't think this bug report
>makes sense.

Well, the (newer?) Ubuntu package lacks parameters.

>In any case, it's not a security issue.

Probably not, except it breaks our scripts pulling entropy from
a central server (using stunnel piped into rngd).

bye,
//mirabilos
--
Yay for having to rewrite other people's Bash scripts because bash
suddenly stopped supporting the bash extensions they make use of
 -- Tonnerre Lombard in #nosec

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Ubuntu is using this upstream for rng-tools: http://sourceforge.net/projects/gkernel/files/rng-tools/

Same as many other distributions out there. If you look at changelogs in Debian, you will see that a different fork of this project is used with indeed many optional flags added that haven't been up-streamed. It would be great if someone submitted changes from the codebase used in Debian to the upstream. Failing that, it might make sense to import debian's rng-tools, as rng-tools-debian into Ubuntu.

Changed in rng-tools (Ubuntu):
status: New → Won't Fix
assignee: nobody → Dimitri John Ledkov (xnox)
importance: Undecided → Wishlist
Revision history for this message
Thorsten Glaser (mirabilos) wrote :

Hm, I fail to find the correct source there, or a mailing list, or… anything useful.

However, your suggestion to import rng-tools-debian sounds nice.
What do I need to do to make this happen?

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

On 9 October 2014 13:08, Thorsten Glaser <email address hidden> wrote:
> Hm, I fail to find the correct source there, or a mailing list, or…
> anything useful.
>

Source tarball is here:
http://sourceforge.net/projects/gkernel/files/rng-tools/5/rng-tools-5.tar.gz/download

And matches checksum with orig tarball that is in ubuntu.

Documentation is in the kernel listing that as upstream location for
user space utility:

https://www.kernel.org/doc/Documentation/hw_random.txt

> However, your suggestion to import rng-tools-debian sounds nice.
> What do I need to do to make this happen?

Rename source/binary package(s) and upload into ubuntu.

--
Regards,

Dimitri.

Revision history for this message
Thorsten Glaser (mirabilos) wrote :

Dimitri John Ledkov dixit:

>> However, your suggestion to import rng-tools-debian sounds nice.
>> What do I need to do to make this happen?
>
>Rename source/binary package(s) and upload into ubuntu.

How do I do that? I know about subscribing ubuntu-sponsors
for sync/merge requests on existing packages, but…

Sorry to bother.

bye,
//mirabilos
--
<ch> you introduced a merge commit │<mika> % g rebase -i HEAD^^
<mika> sorry, no idea and rebasing just fscked │<mika> Segmentation
<ch> should have cloned into a clean repo │ fault (core dumped)
<ch> if I rebase that now, it's really ugh │<mika:#grml> wuahhhhhh

Revision history for this message
Thorsten Glaser (mirabilos) wrote :

I’ve done a first test cut of it into my PPA:

https://launchpad.net/~mirabilos/+archive/ubuntu/ppa/+sourcepub/4628516/+listing-archive-extra

(Ugh. Some of the compiler warnings deserve being handled, although in Debian itself.)

This is now up for review and testing. I’ll test it, too.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Heya,

On 19 December 2014 at 09:35, Thorsten Glaser
<email address hidden> wrote:
> I’ve done a first test cut of it into my PPA:
>
> https://launchpad.net/~mirabilos/+archive/ubuntu/ppa/+sourcepub/4628516
> /+listing-archive-extra
>
> (Ugh. Some of the compiler warnings deserve being handled, although in
> Debian itself.)
>
> This is now up for review and testing. I’ll test it, too.
>

On the surface that looks correct way to do it.

I guess it might make sense to do a Castling move:
rename ubuntu's rng-tools _source_ package to be rng-tools-gkernel but
make it keep the binary package names.
keep debian's rpng-tools _source_ package name but rename binary to be
rng-tools-debian.

That way we don't need to blacklist things and merges.ubuntu.com and
the like will operate correctly and provide sensible outputs.

--
Regards,

Dimitri.

Revision history for this message
Thorsten Glaser (mirabilos) wrote :

Dimitri John Ledkov dixit:

>> This is now up for review and testing. I’ll test it, too.

>On the surface that looks correct way to do it.

OK, thanks. My first tests look okay as well (after I have
changed the Depends in the package *using* it to allow for
rng-tools-debian; it might sense to use a versioned Provides
in vivid…) so far.

>I guess it might make sense to do a Castling move:
>rename ubuntu's rng-tools _source_ package to be rng-tools-gkernel but
>make it keep the binary package names.
>keep debian's rpng-tools _source_ package name but rename binary to be
>rng-tools-debian.

Hm, interesting. Yes, might make sense, but I didn’t want to
impose at first. How difficult is it to get something like
this accepted?

>That way we don't need to blacklist things and merges.ubuntu.com and
>the like will operate correctly and provide sensible outputs.

Ah okay. That will certainly be of aid when we indeed push
further code fixes into Debian.

bye,
//mirabilos
--
<diogenese> Beware of ritual lest you forget the meaning behind it.
<igli> yeah but it means if you really care about something, don't
    ritualise it, or you will lose it. don't fetishise it, don't
    obsess. or you'll forget why you love it in the first place.

Revision history for this message
Thorsten Glaser (mirabilos) wrote : Bug #916147: rng-tools: replaced with inferior version

Putting the Launchpad bug into Cc.

---------- Forwarded message ----------
Message-ID: <email address hidden>
Date: Mon, 10 Dec 2018 18:23:56 +0100 (CET)
Subject: rng-tools: replaced with inferior version

Source: rng-tools
Version: 5-1
Severity: serious
Justification: breaks existing uses of this package

This is the same as Launchpad bug #1333293 now arrived
in Debian itself.

The options (at least) -B, -H, -T, -t are gone, which
breaks my application using rngd.

I had to create this…
https://launchpad.net/~mirabilos/+archive/ubuntu/ppa/+sourcepub/4628516/+listing-archive-extra
… in order to be able to continue using rngd as before.

Will we be reintroducing rng-tools 2.x as rng-tools-debian
into Debian buster/sid? Otherwise, support for all those
missing functionality and options MUST be added to the
new rng-tools package.

Thanks,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Changed in rng-tools (Debian):
status: Unknown → New
Changed in rng-tools (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.