Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Optional encryption of settings.json to prevent exposing password as cleartext. #2635

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

mmccann-umph
Copy link

This feature addresses the narrow scope security case where misconfigured IIS allows for the downloading of settings.txt or settings.json.

In the current codebase these files store database passwords and user accounts in as unencrypted clear text.

This feature uses dotNet's ProtectedData API (scoped to the account the application is running under) to encrypt the values found in the dataSettings.json file so that in the event the file is exposed the sensitive information isn't available in clear text.

…ured IIS allows for the downloading of settings.txt or settings.json. In the current state these files store database passwords in as unencrypted clear text. This feature uses dotNet's ProtectedData API (scoped to the account the application is running under) to encrypt the values found in the dataSettings.json file so that in the event the file is exposed the sensitive information isn't available in clear text.
@RomanovM RomanovM requested review from skoshelev and removed request for RomanovM October 25, 2017 11:05
@AndreiMaz AndreiMaz self-assigned this Oct 25, 2017
@AndreiMaz AndreiMaz requested review from AndreiMaz and removed request for skoshelev October 25, 2017 12:57
@SamandarHijiakbarovich
Copy link

Can I join this project?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants