🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: sci.crypt.random-numbers
Article #1

Re: Gathering entropy for PRNGs on MVS

#1
From: Andrew Swallow
Date: Mon, 10 Mar 2003 20:44
53 lines
3793 bytes
"Duke Arber" <duke_arber@yahoo.com> wrote in message
news:b4ihfk$4oh$1@slb0.atl.mindspring.net...
> >
> > How accurately can you measure time?
> >
> > Read the time and date.  Reschedule so the operating system
> > runs and read the time when you are reactivated.  The
> > entropy comes from the run time of the other programs and
> > the date.  You may be able to play games with the disks and
> > operator reply times.
> >
> > Andrew Swallow
> >
>
> The hardware clock resolution depends on the actual hardware model.  The
> Time-Of-Day (TOD) API returns a microsecond resolution.  I think it's
"safe
> to say" that most of the models produced in the last 5 years have <=20
> microsecond resolution.  Others in the IBM-MAIN newsgroup may be able to
> fill in the details.
>
> Basically, use the current O/S activity rate as a basis for entropy.  Hand
> off control back to the O/S and depending on its activity, it will hand
> control back in some period of time.  During an IPL, there is a lot of
> activity.  During other periods of the day, there may be very little.
Would
> this hold up during periods of low activity?
>
If the crypto program is the only one running the time delays
will be very similar making the values guessable.  This gives
low entropy.  Where there is a complicated mixture of programs
running the delay on a low priority program becomes
unpredictable producing lots of entropy.

Disk reads and writes, when the program waits until the
peripheral has completely finished, gains entropy from
several places.  First the random speed variations that all
motors have, second the variable distance between the
current location of the head and the required sector (assuming
that the disk is already run up) and third disk activity due to
other programs.

On PCs other measures such as amount of disk and
ram being used are also used as a source of entropy
by some web browsers.

Fitting a proper random number generator to the
computer would be a better source for random data.
If one is not made for your mainframe, buying a
PC random number generator module and fitting it
into a dedicated PC is a cheap way of making one.

Andrew Swallow
Technical Details
Message-ID: <b4itf7$ac5$1@knossos.btinternet.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.stueberl.de!newsr1.ipcore.viaginterkom.de!btnet-peer1!btnet-feed5!btnet!news.btopenworld.com!not-for-mail
References: <b4ieak$2qn$1@slb9.atl.mindspring.net> <b4if1a$jte$1@helle.btinternet.com> <b4ihfk$4oh$1@slb0.atl.mindspring.net>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fd4af,4336d2c2bccbde14
X-Google-Attributes: gidfd4af,public
X-Google-Thread: fb57f,4336d2c2bccbde14
X-Google-Attributes: gidfb57f,public
X-Google-Thread: fed83,4336d2c2bccbde14
X-Google-Attributes: gidfed83,public
X-Google-ArrivalTime: 2003-03-10 12:45:02 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.stueberl.de!newsr1.ipcore.viaginterkom.de!btnet-peer1!btnet-feed5!btnet!news.btopenworld.com!not-for-mail
From: "Andrew Swallow" <am.swallow@eatspam.btinternet.com>
Newsgroups: sci.crypt.random-numbers,bit.listserv.ibm-main,sci.crypt
Subject: Re: Gathering entropy for PRNGs on MVS
Date: Mon, 10 Mar 2003 20:44:23 +0000 (UTC)
Organization: BT Openworld
Lines: 54
Message-ID: <b4itf7$ac5$1@knossos.btinternet.com>
References: <b4ieak$2qn$1@slb9.atl.mindspring.net> <b4if1a$jte$1@helle.btinternet.com> <b4ihfk$4oh$1@slb0.atl.mindspring.net>
Reply-To: "Andrew Swallow" <am.swallow@btinternet.com>
NNTP-Posting-Host: host81-132-11-191.in-addr.btopenworld.com
Mime-Version: 1.0
Content-Type: text/plain;
 charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Trace: knossos.btinternet.com 1047329063 10629 81.132.11.191 (10 Mar 2003 20:44:23 GMT)
X-Complaints-To: news-complaints@lists.btinternet.com
NNTP-Posting-Date: Mon, 10 Mar 2003 20:44:23 +0000 (UTC)
X-Priority: 3
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1123
X-Newsreader: Microsoft Outlook Express 6.00.2800.1123
X-MSMail-Priority: Normal