not required
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 29 2021
Decryption works as expected for any type and size of data. Tested up to file-sizes of 200GB
Fix: Set encoding output for decryption result.
ASCII above 127 are encoded as triplets of values "239,191,189" (=UTF8 65533). From 128+ information is compromised.
Individual decrypted blocks (chunks) are "glued" together.
Jun 22 2021
back in action ... Implementing the decryption routine >1 year after coding the related encryption method. Just to keep myself busy, encryption and decryption is done with different APIs *sarcasm" :D
Mar 2 2021
Dec 7 2020
At least for XNAT this was recently resolved in T26449: XNAT connection failes due to missing OpenSSL connections.
Sep 10 2020
Closed because of very long inactivity and drift to current code.
Deleted branch T23244-XNAT-nrrd-convenient-upload-feature.
Jun 15 2020
This is also already on the TODO list of the packaging rewrite.
I am re-opening this since I think this will also become more relevant with the foreseeable use of other REST APIs from MITK , e.g. how did the nvidia segmentation tool resolve this issue for the windows installer? @kislinsk could you comment?
May 26 2020
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Apr 18 2020
There are two approaches:
- Encrypt file and split it into blocks of max size 1MB
- Split file into blocks of max size 1MB and then encrypt each block
Aug 26 2019
encryption works as expected
Aug 21 2019
- encoding File/Blob object to ArrayBuffer (needed as input for AES encryption) crashes browser (tested on Chrome) if file is bigger 1GB:
- check chunking
Aug 20 2019
Aug 17 2019
ToDos
- implement final caseID socketbased
- port encryptData to socketbased
- distinguish between uploading sites (such as CSI, E010, etc.)
- when decrypting, differentiate between files and string
- include IV of encrypted file
- include client PublicKey
- can formData be transported by websockets
- compile needed socket.emit statement. emit supports Buffer
First initialize a TLS based websocket connection between browser and server. In addition encrypt the files using AES-GCM 256. Key to encrypt files is computed using ECDH P-384. Private/Public Key for ECDH is generated independently from the TLS secured websocket connection.
Koa.js is the way to go in this case
First initialize a TLS based websocket connection between browser and server. In addition encrypt the files using AES-GCM 256. Key to encrypt files is computed using ECDH P-384. Private/Public Key for ECDH is generated independently from the TLS secured websocket connection.
cannot be accomplished using cornerstone, since errors are thrown if non-dicom filesize is below "proper" DICOM file. Therefore we implemented our own routine to check if incoming filesize is below 132 bits, otherwise check if bits from 128 to 132 represent "DICM".
Jul 11 2019
Apr 30 2019
Keep in mind:
Feb 22 2019
Updated Section C
Feb 8 2019
Dec 13 2018
Nov 30 2018
Nov 5 2018
check naming consistency:
Oct 23 2018
Since it seems to be quite a hassle to establish a working connection with the sftp server, a more sophisticated approach is planned.