🚀 go-pugleaf

shah@wg.com wrote:
>
>Folks,
>
>I had recently posted a query for password encryption/de-cryption scheme. I
>will sum up the replies I got and post them here.  Here is my next question...
>
>The app. that I am writing needs to have a MASTER password for the
>"Supervisor".  If the "supervisor" gets hit by lightining (God forbid !) or if
>the Supervisor forgets his/her password, how does he/she get in the system ?
>Assume that NO ONE else has access level equivalent to the Supervisor.  Also
>this password needs to be different for each instance of the application i.e
>if (hopefully) someday this app. were to be marketed, then I need to have a
>different MASTER password (maybe based on the application serial number) for
>each copy of the app.; otherwise the bulletin boards and news groups will be
>flooded with this SAME MASTER password for all the copies of this app !!!
>
>Please respond directly to my email address if you can...
>
>Thanks
>Ajay Shah
>(ashah@ecevy.ncsu.edu)
>(shah@wg.com)
>
>P.S:  I am using Microsoft Visual C++ as my programming language.
>

What you are proposing seems to contradict itself.

>Assume that NO ONE else has access level equivalent to the Supervisor.

The MASTER password that you are implying would break this rule would it not?
Who ever holds the MASTER key is system GOD.

I recommend you abandon the MASTER key idea and PRINT the SUPERVISOR
key when it is first created.  You could break it into two parts that two other people
would put together at times of necessity.

Unless of course, it is you intention to design an insecure system.  Take the Canadian
government for example, although they will never admit it, they restrict exporting of
encryption technology, becuse they don't want too much security in 'certain' other countries.

Good luck!

Rolande