Change randombytes/1 so it always executes on a DS
Investigation shows erratic behaviour of the CSPRNG. It may block at times because it needs to go to the kernel and obtain more random information in the system. Once this happens, you are blocked for quite a long time, but we don't generally know when this happens. So just execute these directly on the dirty scheduler.
Showing with 1 addition and 6 deletions