[onerng talk] OneRNG not working after reinstalling onerng_3.6-1_all.deb

[mark.diamond at yahoo.co.uk]

Hello Brian,

I reinstalled the debian package and made the change in onerng.sh that you asked me to do.

Running "/sbin/onerng.sh daemon ttyACM0" (exactly like that) produces a whole lot of "permission denied" error messages. Running the same command with "sudo" gives the output in the attached "onerngsh-daemon-output-1.txt"  ... Sorry about having to attach so short a file. For some bizarre reason, Yahoo mail isn't letting me paste any text into the message ... a fact that turns out to have had a fortunate side-effect ...

... Now for the thing that likely reveals the problem. Because of the problem about copying the terminal output and pasting into Yahoo, I decided to rerun the command and redirect the output into a file. But the first behaviour was not repeated. Instead, I got the message "nohup: redirecting stderr to stdout". So, on the off-chance that the change in error message indicated that the daemon was up and running properly, I tried "cat /dev/random > /dev/null" which results in the much-wanted dimming of the LED on the device.

In the light of the behaviour I have described, I looked to see if I could repeat it. I removed the device, reinserted it and ran onerng.sh as before (producing the same output as in the attached file --- i.e., a non-working device). Rerunning produced the same thing. Waiting 15 seconds and rerunning produced the "nohup" message, and a fuctioning device once more. 

Repeating the process produces inconsistent results. It never works the first time but equally, there appears to be no consistent relationship between the success of the command and the number of later repetitions or the waiting time between commands. I don't know how useful it is, but I have also attached some of the output from 'dmesg'.

Cheers,
Mark






On Tuesday, 26 February 2019, 23:13:13 GMT+11, bsr <presspound at buckeye-access.com> wrote: 

  
No, not a death knell. My first response to your original post included this: 
  
..."If it is failing firmware validation for some reason (which can cause the behavior you 
describe)"... 
  
because I suspected it from the start. 
  
Failing firmware verification doesn't immediately mean that your board is bad or your firmware is compromised. The firmware image must be extracted from the device to check its signature. The output you received from manually running /sbin/onerng.sh daemon ttyACM0 showed a dd read failure right before the firmware gets extracted so you aren't getting the fw image either, thus the failure. I had an idea why dd was failing and gave you a suggested fix to try (direct email communication) which you told me did not solve the problem. 
  
Could you please change back to my suggested fix and re-run /sbin/onerng.sh daemon ttyACM0 manually and give the output, without all the echo statements - I already knew where it was failing. I think it would be best to send it to me directly for now. Sorry if I sound curt, but we need to go one step at a time trying to resolve your issue. 
  


________________________________ 
  ⮪ Reply     🖂 New topic     View topic…   
  Unsubscribe    •    Switch to a daily digest   


  
  

  
  

  
  
     
    *  Privacy      
    *  Acceptable Use      
    *  Terms of Service      
  
  

  


-------------- next part --------------
mrd:~/Desktop$ sudo /sbin/onerng.sh daemon ttyACM0 
[sudo] password for mrd:    
dd: error reading '/dev/ttyACM0': Resource temporarily unavailable
1536+0 records in
1536+0 records out
6144 bytes (6.1 kB, 6.0 KiB) copied, 0.0201494 s, 305 kB/s
/sbin/onerng.sh: 80: kill: No such process

-------------- next part --------------
OUTPUT OF dmesg after inserting OneRNG but before running onerng.sh manually

[62055.626474] usb 4-1: new full-speed USB device number 13 using uhci_hcd
[62055.827495] usb 4-1: New USB device found, idVendor=1d50, idProduct=6086
[62055.827499] usb 4-1: New USB device strings: Mfr=1, Product=3, SerialNumber=3
[62055.827502] usb 4-1: Product: 00
[62055.827505] usb 4-1: Manufacturer: Moonbase Otago http://www.moonbaseotago.com/random
[62055.827507] usb 4-1: SerialNumber: 00
[62055.830743] cdc_acm 4-1:1.0: ttyACM0: USB ACM device
[62113.135711] [UFW BLOCK] IN=enp3s0 OUT= MAC=01:00:5e:00:00:01:10:13:31:1f:b3:2a:08:00 SRC=10.1.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 

Unsuccessful running of onerng.sh produces no additional output to dmesg but when it runs successfully, dmesg reports:

[62238.136829] [UFW BLOCK] IN=enp3s0 OUT= MAC=01:00:5e:00:00:01:10:13:31:1f:b3:2a:08:00 SRC=10.1.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2