We need a user/password manager

[GoogleCodeExporter]

With Crunchy requiring authentication, it will need to be able to create
users & password.  Given the importance of authentication, this has to be
included in the 1.0 release.

Original issue reported on code.google.com by andre.ro...@gmail.com on 11 Jun 2008 at 8:30

[GoogleCodeExporter]

Just recording some thoughts originally written on crunchy-discuss, with 
modifications.

* We should have two versions of Crunchy: single-user and classroom-server. Both
should require authentication, but the mechanism could be simpler in the 
single-user
mode.

* When Crunchy starts (in the server version?), it should look for the
password file.  If none is found, we have many possible choices:
- create one, with default passwords, and use it for that session.
- or, ask the user to create one, using the password manager, and
quit.  (This would be the most secure way to proceed I think.)

*. The password file should be encrypted, with a master password.

*. Since a second user accessing Crunchy will have access to all the
same files as the user that started Crunchy, he or she could always
find the password file (using Crunchy and the os module).  Therefore,
there is no need to try to hide the password file.  The simplest place
to keep it is in Crunchy's home directory.  If problems occurs, it's a
simple matter to delete the file.

A simple GUI program (Tkinter based) should be written as a user/password 
manager.

With the "classroom server", one would have to disable
"exit" so that Crunchy could only be stopped via the command line (or
equivalent) by the teacher.

Original comment by andre.ro...@gmail.com on 12 Jun 2008 at 2:42

[GoogleCodeExporter]

Considered to be completed - with a simple command line interface.

Original comment by andre.ro...@gmail.com on 28 Sep 2008 at 4:57

• Changed state: Fixed