I like the concept but your requirement to NOT store the Password Of the
Day and generate it every time it's needed means you can't pick other
external inputs to feed the process. For example you could call a web
service to check the temperature in some known location as one bit of
the seed, then check the water level in some river, toss in the cycle of
the moon, and the date, mix in the percent full of the disks, and add a
pinch of the faulting rate for the *BASE pool. Oh but all of those
things change constantly except the date, rats.
Maybe you could
architect it so the P.O.D. is kept in a running program only and
requested from that program. Each time the program starts or when some
magic time each day occurs it generates the P.O.D and holds it. Just a
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.