Security Issue: Exposed Email Addresses in config.yaml File

[ProHaller]

Description

It has been observed that the email addresses of all registered users are currently visible in the config.yaml file. This presents a security and privacy concern as it exposes user data in a publicly accessible configuration file.

Steps to Reproduce

1. Navigate to the config.yaml file in the repository.
2. Observe that the email addresses of registered users are listed and readable.

Expected Behavior

The email addresses of users should not be visible or accessible in any public configuration files. Sensitive data should be securely stored and encrypted to prevent unauthorized access.

Suggested Solution

I recommend implementing one of the following solutions:

1. Outsource Configuration to the Database
2. Encrypt Personal Information:

Additional Context

Ensuring the privacy and security of user data is crucial for maintaining trust and complying with data protection regulations. The visibility of email addresses in a configuration file poses a significant risk and should be addressed promptly.

@Epiju Do you have any advice on this matter?

[Epiju]

Hi @ProHaller,

Yes you're right, this could lead to a leak of public information!

Since you are dealing here with user data, I would suggest to leverage the DB and pre-populate it with existing users. That way, the information won't be accessible anymore.

For the rest (cookies, pre-authorized users) I you could use the "secrets" file https://docs.streamlit.io/streamlit-community-cloud/deploy-your-app/secrets-management and add it to the .gitignore file.

Hope it'll help!