aboutsummaryrefslogtreecommitdiffstats
path: root/manual/basic/symmetric-encrypt-decrypt.md
diff options
context:
space:
mode:
Diffstat (limited to 'manual/basic/symmetric-encrypt-decrypt.md')
-rw-r--r--manual/basic/symmetric-encrypt-decrypt.md60
1 files changed, 0 insertions, 60 deletions
diff --git a/manual/basic/symmetric-encrypt-decrypt.md b/manual/basic/symmetric-encrypt-decrypt.md
deleted file mode 100644
index 7436fd02..00000000
--- a/manual/basic/symmetric-encrypt-decrypt.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# Symmetric Encryption & Decryption of Text & File
-
-## About Symmetric Encryption & Decryption
-
-Symmetric encryption, in contrast to asymmetric encryption, uses a single key
-for both the encryption of plaintext and the decryption of ciphertext. This
-method is characterized by its simplicity and speed, making it a popular choice
-for encrypting large volumes of data or for scenarios where the sharing of keys
-between the sender and receiver can be securely managed. GpgFrontend provides a
-user-friendly interface for implementing symmetric encryption, streamlining the
-process for users who may not be familiar with the intricacies of cryptographic
-operations.
-
-The process of symmetric encryption with GpgFrontend begins when a user opts to
-encrypt data without selecting a recipient's public key from the Key Toolbox.
-This action signals the software to use symmetric encryption for the task at
-hand. At this point, the user is prompted to create a password. This password
-acts as the encryption key, transforming the plaintext into ciphertext through a
-cryptographic algorithm. It's crucial that this password is strong and unique,
-as the security of the encrypted data directly depends on the password's
-complexity and unpredictability.
-
-Once the password is established, GpgFrontend proceeds to encrypt the data. The
-resulting ciphertext can only be decrypted with the exact password used for its
-encryption. This means that anyone who wishes to access the encrypted data must
-know the password, highlighting the importance of securely sharing this password
-between the sender and receiver.
-
-Decrypting symmetrically encrypted data with GpgFrontend requires the same
-password used during the encryption phase. When the 'Decrypt' function is
-initiated, the software prompts the user to enter the password. Upon successful
-authentication with the correct password, the software decrypts the ciphertext
-back into readable plaintext. This decryption process, like encryption, is
-straightforward and efficient, but the security of the data relies entirely on
-the password's confidentiality.
-
-Symmetric encryption is particularly useful in scenarios where encrypted data
-needs to be stored securely or transmitted over a secure channel, and where the
-overhead of managing public and private keys is not desirable. However, the
-challenge of securely exchanging the password between the sender and receiver
-cannot be understated. If this password is intercepted or guessed by an
-unauthorized party, the encrypted data's security is compromised.
-
-In summary, GpgFrontend's support for symmetric encryption provides a powerful
-tool for users needing to secure their data with a password. This method is
-distinguished by its reliance on a single password for both encryption and
-decryption, offering a balance between simplicity and security. Users must
-exercise caution in creating a strong password and ensure its secure exchange to
-maintain the confidentiality and integrity of their encrypted data. Symmetric
-encryption with GpgFrontend is a testament to the versatility of cryptographic
-practices, catering to a wide range of security needs with user-friendly
-solutions.
-
-## How to use it?
-
-Symmetric encryption is initiated when you click the 'Encrypt' button without
-selecting any key in the Key Toolbox. For this type of encryption, a password
-must be established for the encryption process. Subsequently, to decrypt the
-data, you will need to provide the same password that was used during the
-encryption phase.