Commit a6ce66b8 authored by Dillenn Terumalai's avatar Dillenn Terumalai
Browse files

Fixed some typo

parent d3ca187a
Pipeline #1221 passed with stage
in 2 minutes and 39 seconds
.gitlab/diagram.png

163 KB | W: | H:

.gitlab/diagram.png

164 KB | W: | H:

.gitlab/diagram.png
.gitlab/diagram.png
.gitlab/diagram.png
.gitlab/diagram.png
  • 2-up
  • Swipe
  • Onion skin
......@@ -17,11 +17,11 @@ This is the GitLab repo of the official transfer-tool for SPSP.
## How does the Transfer Tool (TT) work?
To understand how the TT works, it helps to look at a diagram. In the example below, Labo1 wants to send DNA sequences of bacteria/viruses in a protected manner. The SPSP server has a public key and a private key, which are two mathematically related encryption key. The public key can be shared with anyone, but only the SPSP server has the private key.
To understand how the TT works, it helps to look at a diagram. In the example below, Labo1 wants to send DNA sequences of bacteria/viruses in a protected manner. The SPSP server has a public key and a private key, which are two mathematically related encryption keys. The public key can be shared with anyone, but only the SPSP server has the private key.
First, Lab1 uses the TT to compress the sequences files (*.fastq) and metadata file (*.xlsx) into a tar.gz archive.
Then, the TT signs the previously generated archive using SHA-256 algorithm which generates a hash specific to the archive, meaning that if the content changes even slightly, the hash will be completely different.
After that, the TT uses SPSP’s public key to encrypt the archive, turning it into somehting called ciphertext – scrambled, seemingly random characters.
After that, the TT uses SPSP’s public key to encrypt the archive, turning it into something called ciphertext – scrambled, seemingly random characters.
Finally, the encrypted archive and the hash are uploaded using SFTP protocol which runs over the SSH protocol (which provides communication security and strong encryption).
On the server side, once the archive is properly uploaded, the server will try to decrypt the encrypted archive using its own private key. Then, it will compare the uploaded hash to the hash generated by the server from the decrypted archive to ensure that the content was never changed during the transfer. Finally, if everything goes well, the metadata file is parsed and loaded inside the database. As the server cannot guess for which project of the laboratory the uploaded sequences belong to, an assignment task will be generated.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment