Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-72836

Update security.txt for 4.1 release and related minors


    • MDL-72836-master
    • Hide

      Visit <wwwroot>/security.txt and CONFIRM:

      1. The expiry date is now : 2023-05-29T01:00:00.000Z
      2. The policy URL now points to the docs on moodledev.io and not moodle.org - visit the URL should show you the "Security Procedures" documentation.
      Visit <wwwroot>/security.txt and CONFIRM: The expiry date is now : 2023-05-29T01:00:00.000Z The policy URL now points to the docs on moodledev.io and not moodle.org - visit the URL should show you the "Security Procedures" documentation.
    • 1
    • Team Hedgehog 4.1 sprint 0.4B, Team Hedgehog 4.1 sprint 0 rev

      In MDL-69877 a new security.txt file, following the information @ security.txt was introduced.

      The security.txt file located in /security.txt must be updated regularly, shortly before it expires (defined by the Expires element within the file). This task should be completed two weeks prior to the next major release (or at the earliest, after the major release -2 months minors are released).

      As a minimum, this will involve updating the Expires value, which needs to be set to [expected major release date] + 3 WEEKS. If any of other details in the security.txt need to be amended, they should also be completed at the same time.

      The updates should be made to master, as well as all other security supported Moodle versions that contain security.txt. This means all supported versions have an identical security.txt file (including the same expiry).

      For this release, we also need to update the policy URL to the new moodledev.io docs version of the Security Procedures docs: https://moodledev.io/general/development/process/security


      Detailed information (to be modified for each clone of this issue):

      • Branches affected: master (41), 40, 311, 39
      • Expiry (major release + 3 weeks): 8 May 2023 + 3 weeks = 29 May 2023
      • Other changes: ... add any further changes required here

      Exact formatted expiry date to use: 2023-05-29T01:00:00.000Z

      How the date format was calculated (in line with the latest spec):

      date --date='29 May 2023 01:00' -u +"%FT%H:%M:%S.000Z"

      (This issue is part of the release process, 2 weeks before release, and will be cloned as part of it.)

        1. MDL-72836_master.webm
          1.22 MB
        2. MDL-72836_v311.webm
          1.28 MB
        3. MDL-72836_v39.webm
          1.16 MB
        4. MDL-72836_v400.webm
          1.15 MB

            michaelh Michael Hawkins
            michaelh Michael Hawkins
            David Woloszyn David Woloszyn
            Sara Arjona (@sarjona) Sara Arjona (@sarjona)
            Angelia Dela Cruz Angelia Dela Cruz
            0 Vote for this issue
            3 Start watching this issue


                Original Estimate - 0 minutes
                Remaining Estimate - 0 minutes
                Time Spent - 3 hours, 13 minutes
                3h 13m

                  Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.