aboutsummaryrefslogtreecommitdiffstats
path: root/src/content/docs/guides/symmetric-encrypt-decrypt.md
diff options
context:
space:
mode:
authorsaturneric <[email protected]>2025-07-06 14:14:21 +0000
committersaturneric <[email protected]>2025-07-06 14:14:21 +0000
commit4fdef6f71dfddbefe4de386597dd58de962f1a8f (patch)
tree52b7f1c5cf37942b98b91e326bb1d2519b4c1a8f /src/content/docs/guides/symmetric-encrypt-decrypt.md
parentrefactor(ci): simplify runner configuration for Docker job (diff)
downloadmanual-4fdef6f71dfddbefe4de386597dd58de962f1a8f.tar.gz
manual-4fdef6f71dfddbefe4de386597dd58de962f1a8f.zip
feat(docs): add guide for symmetric encryption and decryption
- Introduced a comprehensive guide on symmetric encryption, detailing its definition, functionality, and usage. - Included steps for encrypting and decrypting data using GpgFrontend. - Provided security tips and scenarios for appropriate use of symmetric encryption.
Diffstat (limited to 'src/content/docs/guides/symmetric-encrypt-decrypt.md')
-rw-r--r--src/content/docs/guides/symmetric-encrypt-decrypt.md92
1 files changed, 0 insertions, 92 deletions
diff --git a/src/content/docs/guides/symmetric-encrypt-decrypt.md b/src/content/docs/guides/symmetric-encrypt-decrypt.md
deleted file mode 100644
index 30512fa..0000000
--- a/src/content/docs/guides/symmetric-encrypt-decrypt.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: Symmetric Encryption & Decryption
-sidebar:
- label: Symmetric Crypto
----
-
-## ๐Ÿ” What Is Symmetric Encryption?
-
-**Symmetric encryption** is a method of securing data where the **same
-password** is used to both encrypt and decrypt information.
-
-Unlike **asymmetric encryption**, which uses a public/private key pair,
-symmetric encryption relies on a single shared secret (the password). This
-approach is:
-
-- โœ… Fast and efficient
-- โœ… Ideal for large files or quick one-time sharing
-- โ— Best used when both parties can safely share the password
-
-> ๐Ÿ“Œ If someone intercepts the password, the encrypted data is no longer secure
-> โ€” so always handle password exchange carefully.
-
-## ๐Ÿ”„ How It Works
-
-1. You choose a **strong password**.
-2. That password is used to **encrypt** the data.
-3. Anyone with the **same password** can **decrypt** it.
-4. No key pair is required โ€” only the shared password.
-
-> ๐Ÿ“Ž Encryption security depends entirely on the strength and secrecy of the
-> password used.
-
-## โœ๏ธ Encrypting Data Symmetrically
-
-To encrypt text using symmetric encryption in GpgFrontend (v2.1.9 and later):
-
-Enable Symmetric Encryption Feature
-
-1. Go to the Settings.
-2. Under the Appearance tab, check the `Sym. Encrypt` checkbox to enable symmetric encryption functionality.
-
-Access the Symmetric Encryption Button
-
-1. After enabling, youโ€™ll see a dedicated `Sym. Encrypt` button on the main interface.
-
-Enter the Text or Select a File
-
-- Input the plaintext you wish to protect in the text editor.
-- Select a file to encrypt using the file panel.
-
-Symmetric Encryption
-
-1. Without selecting any public key, click the `Sym. Encrypt` button.
-2. When prompted, enter a strong, unique password.
-3. This password becomes your encryption key.
-4. The text or file will be encrypted into ciphertext.
-5. You can save or share the encrypted result.
-
-> ๐Ÿ” The recipient will need the **exact same password** to decrypt the message.
-
-## ๐Ÿ”“ Decrypting Symmetric Encrypted Data
-
-To decrypt content that was encrypted symmetrically:
-
-1. Paste the Ciphertext: The message should begin with `-----BEGIN PGP MESSAGE-----` and end with `-----END PGP MESSAGE-----`.
-2. Initiate Decryption: Choose to decrypt the message.
-3. Enter the Password: Input the **same password** that was used for
- encryption.
-4. View the Plaintext: If the password is correct, the original message will be revealed.
-
-> ๐Ÿง  If the password is incorrect or mistyped, decryption will fail.
-
-## ๐Ÿ’ก When to Use Symmetric Encryption?
-
-Symmetric encryption is a great choice when:
-
-- Youโ€™re encrypting something **for yourself** (e.g. storing private notes or
- backup files).
-- Youโ€™re sharing data over a **secure channel**, and can **safely provide the
- password**.
-- You donโ€™t want to manage public/private key infrastructure.
-
-However, it is **not ideal** for public communication where secure password
-exchange is difficult.
-
-## ๐Ÿ›ก๏ธ Tips for Better Security
-
-- Always use a **strong, complex password** (longer is better).
-- Never send passwords through insecure channels (e.g., unencrypted email).
-- Consider using symmetric encryption as a supplement to public-key encryption โ€”
- e.g., encrypt a file symmetrically, then encrypt the password with the
- recipientโ€™s public key.