Skip to content

Comments

[Security] Default most LORIS modules to be disabled on new installs#10354

Open
driusan wants to merge 1 commit intoaces:mainfrom
driusan:DefaultDisabledModules
Open

[Security] Default most LORIS modules to be disabled on new installs#10354
driusan wants to merge 1 commit intoaces:mainfrom
driusan:DefaultDisabledModules

Conversation

@driusan
Copy link
Collaborator

@driusan driusan commented Feb 9, 2026

This changes the default schema to populate the 'Active' column to 'N' for most modules.

The exceptions are:

  1. login module
  2. user_accounts module
  3. module_manager
  4. configuration module
  5. dashboard module

which are the modules that are required to do very basic administration (such as enabling new modules that are desired or logging in to LORIS) on a new install.

This is intended to lower the attack surface of new installs, so that projects will only enable modules on an as-needed basis.

Existing projects are unaffected as they are already set up.

This changes the default schema to populate the 'Active' column to
'N' for most modules.

The exceptions are:
1. login module
2. user_accounts module
3. module_manager
4. configuration module
5. dashboard module

which are the modules that are required to do very basic administration
(such as enabling new modules that are desired or logging in to LORIS)
on a new install.

This is intended to lower the attack surface of new installs, so that
projects will only enable modules on an as-needed basis.

Existing projects are unaffected as they are already set up.
@github-actions github-actions bot added the Language: SQL PR or issue that update SQL code label Feb 9, 2026
@driusan driusan added Category: Cleanup PR or issue introducing/requiring at least one clean-up operation Category: Security PR or issue that aims to improve security and removed Language: SQL PR or issue that update SQL code labels Feb 9, 2026
@christinerogers
Copy link
Contributor

Suggest a followup issue to clearly document this early in the install/setup documentation, with a clear walkthrough of how to activate modules quickly and easily. (Ideally without navigating to module readmes to figure out what each one does.)

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

Labels

Category: Cleanup PR or issue introducing/requiring at least one clean-up operation Category: Security PR or issue that aims to improve security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants