Clarify consequences of disabling the login_required setting
|Assignee:||Go MAEDA||% Done:|
When an administrator disabled the
login_required setting and/or sets projects as public, this can have grave consequences for the protection of the data in-house projects. If this is done carelessly, confidential data might be exposed to undesired audiences (e.g. the global unauthenticated internet).
The attached patches try to make the consequences of these settings clearer by making them more prominent and explain their consequences to the user. This helps admins and project managers make the correct decisions.
We use these patches on Planio where all accounts require authentication by default. But even for "older" Redmine installations which might have some internal public projects it might still be surprising that they are suddenly public when not enforcing authentication anymore.
#2 Updated by Go MAEDA about 1 year ago
- Target version changed from Candidate for next minor release to 4.1.0
I think this patch is very valuable because sometimes I find a Redmine instance which unintentionally exposes internal projects on the internet. This patch can prevent users from making such inappropriate settings.
I am setting target version to 4.1.0.
I think we should slightly change messages in the patch, replace the word "Internet" with "network" because Redmine may be deployed on intranets.
When not requiring authentication, public projects and their contents are openly available on the
Public projects and their contents are openly available on the
#5 Updated by Holger Just 5 months ago
- File 0001-Clarify-consequences-of-disabling-the-login_required.patch added
- File 0002-Clarify-consequences-of-setting-a-project-as-public.patch added
I just updated the patches with the wording changes proposed by Maeda-san.
I also rebased the patches on the current trunk at r17295.