首页 全栈极客与开发辅助内容详情

Text Encrypt / Decrypt: AES-GCM With a Passphrase, In Your Browser - Real encryption, zero keys stored

2026-11-17 3 访客
Text Encrypt / Decrypt: AES-GCM With a Passphrase, In Your Browser

站点名称:Text Encrypt / Decrypt: AES-GCM With a Passphrase, In Your Browser

所属分类:全栈极客与开发辅助

官方网址:https://www.9314.cn/tools/text-encrypt/en/

SEO查询: 爱站网 站长工具

进入网站

站点介绍

Text Encrypt / Decrypt: AES-GCM With a Passphrase, In Your Browser

Sending a database password to a teammate over chat in plaintext felt wrong, and Base64 is a sticky note anyone can peel. The habit that stuck: encrypt with AES, send the ciphertext in chat, and speak the passphrase over the phone - a different channel. This page does exactly that job - set a passphrase, seal the text, all inside the browser, past no server at all.

The short version

  • Encryption, not encoding: AES-256-GCM (the symmetric cipher banking protocols use), with the key derived from your passphrase through 100,000 PBKDF2 iterations - without the passphrase, not one bit of plaintext comes out.
  • Shareable ciphertext: v1: prefix plus Base64 survives any chat window, note app or ticket; every encryption draws a fresh random salt/IV, so the same passphrase never yields the same ciphertext twice (no comparison leaks).
  • Failures are loud: wrong passphrase or corrupted data gets rejected by the GCM authenticity check - you never receive wrong plaintext.
  • Nothing persists: no passphrase, no key, no ciphertext ever stored; refresh wipes the page; zero uploads, works offline.

The nature of encryption: no key, no opening

The warning bar at the top is not legal boilerplate - it is the math. The key derives from your passphrase, and your passphrase lives in your head. There is nothing on the server that could help you recover it, because this page uploads nothing anywhere. A lost passphrase is a lost key; do not gamble on brute force, AES-256 does not lose to patience. Memorize the passphrase before you press Lock.

Why encrypting the same text twice gives different results

Every run generates a fresh random salt (16 bytes) and IV (12 bytes), both packed into the ciphertext. That is not instability - it is standard practice in serious cryptographic designs: if identical plaintext always produced identical ciphertext, an attacker could compare ciphertexts and infer "these two secrets are the same" - two tickets sharing a password, say, would share a ciphertext too. Randomization cuts that inference chain.

FAQ

I forgot the passphrase. Can the text be recovered?

No, and there is no workaround. The key is derived from your passphrase with PBKDF2; this page stores neither the passphrase nor the key anywhere (it uploads nothing at all), so a forgotten passphrase is a lost key. Do not burn an afternoon guessing - brute-forcing AES-256 is not engineering-feasible. Store the passphrase somewhere solid before you encrypt.

How is this different from Base64 "encryption"?

Base64 is an encoding, not encryption: anyone can paste it into a decoder and read the original - a letter in a transparent envelope. This is real encryption: AES-256-GCM is the symmetric cipher used in banking protocols, and without the passphrase not a single bit of plaintext can be derived. Use Base64 to fool the eye; use this for actual confidentiality.

Why does the same text encrypt differently each time?

By design, not by accident. Every encryption run generates a fresh random salt and a fresh random initialization vector, both packed into the ciphertext - so encrypting "hello" twice yields two completely different Base64 strings. The upside: an attacker cannot compare ciphertexts to learn whether two plaintexts match. That is standard practice in serious cryptographic designs.

What does "wrong passphrase or corrupted data" mean?

Two possibilities: the passphrase is wrong (case, trailing spaces, wrong keyboard layout all count), or the ciphertext was truncated or altered during copy-paste. GCM carries a built-in authenticity check and refuses to decrypt if a single bit is off - it would rather fail than hand you wrong plaintext. Check the passphrase first, then verify the ciphertext is complete (starts with v1:, nothing missing at the end).

Are my passphrase or ciphertext uploaded or logged?

No. Encryption and decryption run in this device's browser via WebCrypto - no upload endpoint, works offline. The page stores no passphrase, key or ciphertext: refresh it and every input box is empty, nothing kept anywhere.

中文版:https://www.9314.cn/tools/text-encrypt/

 暂无评论,快来抢沙发吧~

发布评论