[SOLVED] Using OneRNG: OneRNG Talk: OneRNG

I tired to use onerng in a virtual Ubuntu and this is what I found. The best
distribution to use is 18.04 LTS. The newer ones do not support all the
necessary components.

After installing the necessary components and onerng package, attached the
onerng device to USB port and make sure that VMWARE is connecting the USB to
the Ubuntu machine by default. Next restart the machine not by restart option
in VMware, but only by using command "sudo shutdown -r now" while the usb is
connected. That should work.

For me , if I shutdown the Ubuntu virtual machine and turn it on, I need to
connect the onerng to usb and restart the machine and then it will work.

Hope this helps.

I am running 18.04 LTS on Virtualbox 16.1 and followed your post but when I try
the cat test the orange onerng led never dims so I think it is not working. The
only thing I have found is the onerng dev should be ttyA... but I have no
devices like that and dmesg and dev/kmsg give no help. Any ideas what the dev
should be or any help on knowing if the device is there. The only usb
connection from virtualbox is 1.1?

You will probably need to install the Virtualbox Extension Pack in order to
enable the full ability to map in USB devices and other extra features.

Did that, have tried with USB 2.0 and 3.0 but cannot find the device. I
expected /dev/random to be linked to onerng if it was ok but it isn't. Is there
something else I have to do in virtualbox to map devices?

The OneRNG supplements the kernel randomness by injecting it via a specific
mechanism, it doesn't replace /dev/random or /dev/urandom itself.

My mistak, I thought an empty filter would allow all through. Have now selected
the moonbase device and ttyASM0 has appeared.

Thanks for help.
Now I have a dev/ttyACM0, the onerng package installed but cat /dev/random
>/dev/null never dims the led. Have tried all the things in the moonbase doc
but nothing changes.
cat and dd on /dev/ttyACM0 give no output.

Sounds like you're getting on well, albeit a little slowly.

OneRNG presents itself as a serial device, as you've found; on Linux
/dev/ttyACM0 is often what the OS chooses to call it.

By default, there's no connection between this serial device and the Linux
OS's internal random number generators (/dev/random, /dev/urandom). That's
what the software package for OneRNG tries to provide - but there have been
a bunch of changes in recent distributions that stop it from working
properly (python has been upgraded, systemd has taken control of more
things, the entire internals of /dev/random have been re-written). We have
a new version of the helper software in development according to Paul,
it'll come when he's ready :-)

So with a current Linux and the current state of the software, just
plugging it in is unlikely to do much. However, you can still talk directly
to the device over the serial interface and collect data for use directly
with your own software. The "Generic" instructions provided from the
Moonbase Otago site http://www.moonbaseotago.com/onerng/#Generic are still
accurate, and will lead you to connect to the device and issue
instructions, and eventually run 'rngd' manually to link up our device with
/dev/random.

Some of the comments about extended demand from /dev/random causing the
OneRNG LEDs to light are probably inaccurate now, as I don't think
/dev/random re-seeds itself following usage in the same way that it used
to. Instead I suspect the better approach is to just cram data down the
pipeline periodically regardless of usage - but again I defer to Paul. I'm
guessing some documentation rewriting will be needed.

As for Windows itself, we're still not clear on how the OS might accept
external entropy - it's likely that only hardware services Microsoft want
to support (e.g. TPM devices and CPU services) will ever have a way in.
However, if you have a specialist use for entropy you can talk directly to
the OneRNG over the serial interface and process its data with your own
software.

-jim

Rest of post

Jim,
Thanks for info
I have failed to get it to work in Vmware and Linux (probably me). MS have
stated that USB devices will not work under current WSL with no timescale for
when it will.
However I can use it for what I want to do under Windows, using it as a serial
device. I the "dimming" doesn't happen for me which I admit did fool me for a
while. Strangely I did notice the led blinked when I opened the serial device
under Windows.
Perhaps an update to documentation about installing driver under Windows 10. Of
course signing the driver would be best but that is probably not worth the
effort.

On Monday, 2 November 2020 11:04:10 PM NZDT onerng wrote:
> I have failed to get it to work in Vmware and Linux (probably me). MS have
> stated that USB devices will not work under current WSL with no timescale
> for when it will. However I can use it for what I want to do under Windows,
> using it as a serial device. I the "dimming" doesn't happen for me which I
> admit did fool me for a while. Strangely I did notice the led blinked when
> I opened the serial device under Windows. Perhaps an update to
> documentation about installing driver under Windows 10. Of course signing
> the driver would be best but that is probably not worth the effort.

I actually do much of my debug under vmware (so I can test different distros),
you need to click on the little icon in the bottom right corner of the window
to attach the device to the particular VM

I will be releasing a new set of the linux startup script, it's been taking a
lot longer than I expected, it gets around the issues caused by the recent
changes to the kernel (and python versions on new systems) - would people be
interested in an early preview posted here?

Paul

Rest of post

I am happy to wait.

On 11/2/20 5:15 AM, Paul Campbell wrote:
>
> would people be interested in an early preview posted here?

Yes, I am interested.

Thanks.

I also would be interested.

From: OneRNG Talk <onerng-talk@lists.onerng.info> On Behalf Of Paul Campbell
Sent: Monday, November 2, 2020 5:16 AM
To: onerng-talk@lists.onerng.info
Cc: onerng <<email obscured>>
Subject: Re: [onerng talk] [SOLVED] Using OneRNG

Rest of post

[SOLVED] Using OneRNG

Already a member?

Not a member?