Open SaiDheerajPeketi opened 1 month ago
Thank you sir for assigning the issue. I have started to work on it.
is this open @SaiDheerajPeketi
Yes its open @RITIK-CHAUDHRY
@SaiDheerajPeketi sir i have corrected the code....and commited the changes ......please review it
🚀Feature Request
Description
The requested feature is to implement a mechanism that encrypts data in chunks before transfer, and then decrypts it after the transfer is complete. This system should include the generation of a hash digest to ensure the data’s integrity during transmission. By implementing this, data transfer becomes more secure and prevents tampering or corruption during transit.
Expected behavior
Current behavior
Currently, there is no encryption or verification process for data transfer, which leaves the transfer vulnerable to security issues like interception, tampering, or corruption.
Steps to reproduce
Possible Solution
Encryption: Use the existing AES implementation to encrypt each chunk separately before transferring. Ensure that encryption keys are securely managed.
Hash Digest: Compute a cryptographic hash (e.g., SHA-256) of each chunk before transfer. This hash will serve as a digest to verify that the data hasn’t been altered during transfer.
Decryption and Verification: After the transfer, use the hash digest to verify each chunk or the complete data. If the data passes verification, proceed to decrypt each chunk and reconstruct the original file.
Why is this feature important to you?
This feature is critical to ensuring data security during transfer, especially when dealing with sensitive information. Encrypting the data adds a layer of security, while using a hash digest ensures that the data hasn’t been tampered with or corrupted during the transfer. This will increase user trust and prevent potential security breaches or data loss.