Release: 4.1.0

[craddm]

✅ Checklist

Refer to the Deployment section of our documentation when completing these steps.

• Consult the data-safe-haven/VERSIONING.md guide and determine the version number of the new release. Record it in the title of this issue.
• Create a release branch called e.g. release-v0.0.1
• Draft a changelog for the release similar to our previous releases, see https://github.com/alan-turing-institute/data-safe-haven/releases
• Deploy an SHM from this branch and save a transcript of the deployment logs
• Build an SRE compute image (SRD) and save transcripts of the logs
• Using the new image, deploy two SREs which between them cover tiers 2 and 3 and Guacamole/Microsoft RDS
  • Save the transcript of your tier 2 SRE deployment
  • Save the transcript of your tier 3 SRE deployment
• Complete the Security evaluation checklist from the deployment documentation

For MAJOR releases:

• Confirm that a third party has carried out a full penetration test evaluating:
  1. external attack surface
  2. ability to exfiltrate data from the system
  3. ability to transfer data between SREs
  4. ability to escalate privileges on the SRD.

💻 Release information

• Version number: 4.1.0
• SHM ID: green (https://github.com/alan-turing-institute/trusted-research/issues/267)
• T2 SRE ID: t2msrds (https://github.com/alan-turing-institute/trusted-research/issues/268)
• T3 SRE ID: t3guac (https://github.com/alan-turing-institute/trusted-research/issues/269)

🌳 Deployment problems

MS-SQL databases failed to deploy correctly for both SREs. A fix was implemented in #1582.

The PyPi mirrors failed to populate with packages due to an upstream change in the Python packages used to run the server. A fix was implemented in #1582