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.

Sign up for GitHub

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

Jump to bottom

Create limited girder key secret for deployment #188

Open
JavierCladellas opened this issue Dec 13, 2024 · 0 comments
Open

Create limited girder key secret for deployment #188

JavierCladellas opened this issue Dec 13, 2024 · 0 comments
Assignees
@prudhomm @vincentchabannes @JavierCladellas
Labels
ci-cd Continuous Integration/Continuous Deployment data-privacy Handling sensitive or personal data data-security Ensuring the security of data storage and access

Comments

@JavierCladellas
Copy link
Collaborator

JavierCladellas commented Dec 13, 2024 •
edited
Loading

The deploy workflow will move all reports saved under a Girder staging/ folder to either denied/ or production/.
This can lead to a major security issue (e.g. someone changes the staging folder id to an important folder).

@prudhomm @vincentchabannes Could we create a GitHub secret (GIRDER_BENCHMARKING) that has read+write permissions exclusively on this folder https://girder.math.unistra.fr/#collection/6493e7c2b0e9570499e1c9b8/folder/66e94858b0e95728eb00fcfb ?
@JavierCladellas JavierCladellas added ci-cd Continuous Integration/Continuous Deployment data-security Ensuring the security of data storage and access data-privacy Handling sensitive or personal data labels Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@prudhomm prudhomm

@vincentchabannes vincentchabannes

@JavierCladellas JavierCladellas

Labels
ci-cd Continuous Integration/Continuous Deployment data-privacy Handling sensitive or personal data data-security Ensuring the security of data storage and access
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@prudhomm @vincentchabannes @JavierCladellas