diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 6695bb4d46019c9aaef7d3bd5c870ca6ff58f806..2ab86859513211d8101e1622ea69863ff0474e4c 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -176,7 +176,7 @@ deploy:vm:
- echo "$KNOWNHOSTS" > ~/.ssh/known_hosts
- chmod 644 ~/.ssh/known_hosts
rules:
- - if: '$CI_PIPELINE_SOURCE != "merge_request_event" && $CI_COMMIT_REF_NAME == "develop" && $CI_PROJECT_PATH == "R3/howto-cards"'
+ #- if: '$CI_PIPELINE_SOURCE != "merge_request_event" && $CI_COMMIT_REF_NAME == "develop" && $CI_PROJECT_PATH == "R3/howto-cards"'
- if: '$CI_PIPELINE_SOURCE != "merge_request_event" && $CI_COMMIT_REF_NAME == "master" && $CI_PROJECT_PATH == "R3/howto-cards"'
script:
- ssh -p $SSHPORT $SSHCONNECT "mkdir -p ~/$CI_COMMIT_REF_NAME/sources/public/$CI_JOB_ID ~/$CI_COMMIT_REF_NAME/public"
diff --git a/external/exchange-channels/atlas-hpc/atlas-hpc.md b/external/exchange-channels/atlas-hpc/atlas-hpc.md
index a2945058077e5486e1af706d514860fbbc916353..4bcad74cb19dd3cb3facd3bbc8e8837f0283ef9f 100644
--- a/external/exchange-channels/atlas-hpc/atlas-hpc.md
+++ b/external/exchange-channels/atlas-hpc/atlas-hpc.md
@@ -12,9 +12,9 @@ redirect_from:
# Data transfer between Atlas and UL HPC Clusters
A recommended storage pattern is to have the master copy of data on Atlas (project folder) and only store data on the UL HPC Clusters temporarily for the required practical duration of computational analysis. The derived data and results should hereafter be transferred back to Atlas. This How-to Card describes the different methods to transfer data between Atlas and the UL HPC Clusters. The three recommended methods to transfer data are:
-1. [Via laptop with ```scp``` or ```rsync```](#1. Via laptop using scp or rsync)
-2. [Via dedicated Virtual Machine (VM)](#2. Via dedicated Virtual Machine (VM) using rsync)
-3. [Via Large File Transfer (LFT)](#3. Via Large File Transfer (LFT))
+1. [Via laptop with ```scp``` or ```rsync```](#1-via-laptop-using-scp-or-rsync)
+2. [Via dedicated Virtual Machine (VM)](#2-via-dedicated-virtual-machine-using-rsync)
+3. [Via Large File Transfer (LFT)](#3-via-large-file-transfer-lft)
Please refer to the dedicated knowledge bases to see how to [connect to UL HPC Clusters](https://hpc-docs.uni.lu/connect/access/) and to [mount Atlas](https://service.uni.lu/sp?id=kb_article_view&sysparm_article=KB0010233).
@@ -27,7 +27,7 @@ When using the UL laptop to transfer data between UL HPC Clusters and Atlas, you
Please visit the [UL HPC documentation](https://hpc-docs.uni.lu/data/transfer/#data-transfer-tofromwithin-ul-hpc-clusters) to see how to use `rsync` and `scp`.
-## 2. Via dedicated Virtual Machine (VM) using rsync
+## 2. Via dedicated Virtual Machine using rsync
Data can be transferred via a dedicated VM, which can be requested via [ServiceNow](https://service.uni.lu/sp?id=sc_cat_item&table=sc_cat_item&sys_id=49956812db3fa010ca53454039961978).
Instead of transferring data between Atlas and UL HPC Clusters through the laptop as described above, the transfer will go through the dedicated VM. Once connected to the VM and mounted to Atlas, the ```rsync``` command can be used in the same way as described in the [UL HPC documentation](https://hpc-docs.uni.lu/data/transfer/#data-transfer-tofromwithin-ul-hpc-clusters). This method is recommended for **recurring transfers of very large datasets** that benefit from high-speed network connection between the VM and the HPC.
diff --git a/external/integrity/transfer/owncloud-privatebin/img/7zpassword.png b/external/integrity/transfer/owncloud-privatebin/img/7zpassword.png
new file mode 100644
index 0000000000000000000000000000000000000000..9becc6e75354be1e288e6aafacf45c7d2783f2fd
Binary files /dev/null and b/external/integrity/transfer/owncloud-privatebin/img/7zpassword.png differ
diff --git a/external/integrity/transfer/owncloud-privatebin/img/encryptionpassword.png b/external/integrity/transfer/owncloud-privatebin/img/encryptionpassword.png
new file mode 100644
index 0000000000000000000000000000000000000000..872244461df5aee0a801c4b13f080853cf403394
Binary files /dev/null and b/external/integrity/transfer/owncloud-privatebin/img/encryptionpassword.png differ
diff --git a/external/integrity/transfer/owncloud-privatebin/img/keka-encryption.png b/external/integrity/transfer/owncloud-privatebin/img/keka-encryption.png
new file mode 100644
index 0000000000000000000000000000000000000000..a49f9ea0d7f2ecf69782ff15016759b5b32c14bd
Binary files /dev/null and b/external/integrity/transfer/owncloud-privatebin/img/keka-encryption.png differ
diff --git a/external/integrity/transfer/owncloud-privatebin/img/owncloudshare.png b/external/integrity/transfer/owncloud-privatebin/img/owncloudshare.png
new file mode 100644
index 0000000000000000000000000000000000000000..f2f97909a1c616f991ae85c1e0d86db663808852
Binary files /dev/null and b/external/integrity/transfer/owncloud-privatebin/img/owncloudshare.png differ
diff --git a/external/integrity/transfer/owncloud-privatebin/img/passwordLink.png b/external/integrity/transfer/owncloud-privatebin/img/passwordLink.png
new file mode 100644
index 0000000000000000000000000000000000000000..abb62514c5e73bbc5eb32395e4377300c45c6674
Binary files /dev/null and b/external/integrity/transfer/owncloud-privatebin/img/passwordLink.png differ
diff --git a/external/integrity/transfer/owncloud-privatebin/owncloud-privatebin.md b/external/integrity/transfer/owncloud-privatebin/owncloud-privatebin.md
new file mode 100644
index 0000000000000000000000000000000000000000..3dc4bec5ee59eb72e0ebccf7e621c687904157a8
--- /dev/null
+++ b/external/integrity/transfer/owncloud-privatebin/owncloud-privatebin.md
@@ -0,0 +1,38 @@
+---
+layout: page
+permalink: /external/integrity/transfer/owncloud-privatebin/
+shortcut: integrity:transfer:owncloud-privatebin
+redirect_from:
+ - /cards/integrity/transfer:owncloud-privatebin
+ - /external/integrity/transfer:owncloud-privatebin
+ - /integrity/transfer/owncloud-privatebin
+ - /external/external/integrity/transfer/owncloud-privatebin/
+---
+
+# Transfer of Human Data with OwnCloud
+
+This How-to Card provides a step-by-step guide on how to transfer Human Data via LCSB Owncloud securely. Please note that this How-to Card is intended for the use case where data is < 4 GB and categorized as [sensitive]({{ '/?qms:LCSB-POL-BIC-01' | relative_url }}), in which encryption must be in place as well as secure exchange of encryption password with PrivateBin. If you wish to share Human Data **recurrently** with e.g. external collaborators, we recommend using Owncloud with Cryptomator for encryption of data on the cloud. For further information, please visit the dedicated card on [Cryptomator]({{ '/?exchange-channels:cryptomator' | relative_url}}).
+
+**Prerequisite:** LUMS account is needed and can be requested via the [Service Portal](https://service.uni.lu/sp?id=sc_cat_item&table=sc_cat_item&sys_id=c536257ddb336010ca53454039961936).
+
+1. Use a zip software that supports AES256 encryption to zip your file(s) with a strong password.
+* For Windows computer you can use [7-zip](https://www.7-zip.org/download.html), which uses AES256 encryption by default.
+* For Mac you can use [Keka](https://www.keka.io/en/). To enable AES256 encryption, please go to `settings > Compression` and tick the **Use AES-256 encryption** checkbox like displayed below. <br>
+<img src='img/keka-encryption.png' height='350px'> <br>
+2. Use a password generator to generate a strong encryption password.
+* Use an online password generator like [dice ware](https://diceware.dmuth.org/), or a password manager like [BitWarden](https://bitwarden.com/) or [KeePass](https://keepass.info/) to generate a strong password.
+3. Go to [LCSB PrivateBin](https://privatebin.lcsb.uni.lu/) and type/add the password in the Editor tab.
+4. Enable the feature "Burn after reading" by ticking the checkbox. This means that the link to the password can only be used **once** so it expires upon first access.
+<img src="img/encryptionpassword.png">
+* You will be promted to enter your LUMS credentials once you click on "Send".
+* You should be redirected to a page containing the password link.
+<img src="img/passwordLink.png">
+5. Share the password link with your collaborator via your preferred communication channel.
+6. The collaborator (recipient) **must** confirm that the password was successfully received before proceeding with the following steps. If collaborator reports an error, it indicates the password was compromised and data transfer is not secured anymore. In this case the zipped archive should be deleted and the process should started again. This is a crucial step in the data transfer!
+7. Login to [OwnCloud](https://owncloud.lcsb.uni.lu/) with LUMS account.
+* Upload the zipped archive to OwnCloud and make a share link with the collaborator.
+* See a full guide on how to use [OwnCloud]({{ '/?exchange-channels:owncloud' | relative_url }}).
+<img src="img/owncloudShare.png">
+8. Share the access link with your collaborator by typing in their email as shown on the image above.
+* The collaborator will automatically receive a link to the encrypted data on OwnCloud by email.
+9. The collaborator can now decrypt the data with the password received via Privatebin.