Added the setup.py wizard : Run setup.py using Python3 in order to input your matricule, password, and locally store a hashed version of your password (can be modified to also store the email, or store the hashed password in a database for security purposes). This allows for a new update in the MUSchedule-x.py files, making it more user-friendly.

Setup steps :

1. The user runs the setup ;
2. The user inputs its email and password and confirm them ;
3. We locally store the email and password (or store the encrypted password in a database) ;
4. When the user runs a MUSchedule-x.py file, the script will retrieve the email from a config file and the password either from the config file or from the database, and decrypt it for use.

Positive aspects :

• The setup.py allows for a more user-friendly experience than asking the user to modify his email and password in the python files ;
• Using a hash, we never store the real password.

Negative aspects :

• Storing the hashed password locally allows for an easier decryption and leakage (solution : store the password in a database and retrieve it from there)

Using a config file should be a pretty good idea since it will be easier for the end user to set it up instead of editing the python code. And if we setup a docker version of the project it will be much much simple to use a config file external to the code.

If you entered a incorrectly formatted matricule, then a correctly formatted one and confirmed, the script would ask you to confirm the incorrectly formatted one. Bug fixed.

When the user inputs its matricule and password, the script encrypts them with the public key found in keys/public_key.pem. The encrypted matricule and password are then stored in config/login.idd. They can be retrieved by using the retrieve_login() method from the setup.py file. Encrypted matricule and password can then be decrypted using the decrypt() method from encrypt.py. Further details can be found in the setup.py file.