Browser 106

no file limit

Inspector security/pgp-encrypt-message

PGP Bericht Versleutelen

Overview

Encrypt a text message to one or more OpenPGP public keys and get back a standard ASCII-armored block ready to paste into an email, a ticket or a chat window. The message is encrypted once with a session key, and that session key is wrapped separately for every recipient you add, so each of them opens the same block with their own private key and none of them needs a shared password. If you want the recipient to be able to tell the message came from you, turn on signing as well and unlock your own key — encryption on its own hides the contents but proves nothing about the author. All of it runs on openpgp.js in your browser: the plaintext, the recipients' keys and your passphrase stay on the device, nothing is uploaded, and the output decrypts with GnuPG on the other end. You can type the message or drop a file if you would rather; the file-first version of the same operation lives on the PGP Encrypt File page.

Sending something sensitive by emailEncrypt the message body to your correspondent's public key and paste the block in, so the contents survive the mail servers in between without being readable by them.
Handing over a credentialWrap an API key, a password or a connection string in PGP before it goes into Slack or a ticket, where it would otherwise sit in plaintext and in the search index forever.
Writing to a whole teamAdd each colleague's public key and send one block everyone on the list can open with their own key — no shared secret, and no re-encrypting per person.
Encrypting and signing in one stepFor a message where both privacy and authorship matter — a security disclosure, an instruction to move money — encrypt to the recipient and sign with your own key at the same time.
Working without a local GPG setupSend an encrypted message from a machine that has no GnuPG installed, using a public key pasted straight in and nothing left behind on the device afterwards.

Set

Beveiligingstools 26

Neighbours

01 AES Bestand & Tekst Encryptor 02 Base64 Decoderen 03 Base64 Coderen 04 CSR Generator 05 DER naar PEM Converter 06 Hash Generator

Specification

Command: security.pgp_encrypt_message
Set: Security
Input: text
Output: ASC
Max. bestand: no limit
Batch: single file

Runtime

Engine: WebCrypto · OpenPGP.js
Threads: single
Isolated: —
WebGPU: —
Memory: —

Transport 0 B

The file is opened, worked on and written back inside this tab. No upload step exists in this tool — there is nowhere for the bytes to go.

Keys

Zoeken: ⌘K
Panels: ⌘1 · ⌘2
Full width: F
All keys: ⌘/

How it works

Pick the recipients

Choose keys from this browser's keyring, or paste a public key straight in. Add as many as you need — the message is encrypted once and the session key is wrapped separately for each recipient, so any one of them opens it with their own private key.

Type the message

Write or paste the text. If you also want the recipient to be able to tell it came from you, turn on signing and unlock your own private key with its passphrase — encrypting alone hides the content but says nothing about who wrote it.

Copy the armored block

The result is standard ASCII-armored OpenPGP text starting with -----BEGIN PGP MESSAGE-----, safe to paste into an email, an issue tracker or a chat window. Anyone using GnuPG can decrypt it.

Frequently asked

How does encrypting to a public key work?

The message is encrypted once with a randomly generated session key, and that session key is then wrapped with each recipient's public key. Only the matching private key can unwrap it, so only the people you addressed can read the message — and you never need anything secret from them.

Do I need my own key to encrypt?

No. Encrypting needs only the recipient's public key. You need your own private key only if you also want to sign the message, which is what tells the recipient it came from you rather than from someone else who happened to have their public key.

Can I encrypt to several people at once?

Yes. Add every recipient's public key and you get one block that each of them can open independently with their own private key. Nobody has to share a password and no recipient needs to know who else was addressed.

Does encrypting prove who sent the message?

No, and this is the most misunderstood thing about PGP. Encryption hides the contents from everyone but the recipient; it says nothing about the author, because anyone can encrypt to a public key. Sign the message as well if authorship matters.

What if I don't have the recipient's public key?

You cannot encrypt to them until you do. Ask them for it — most people who use PGP will send the armored block or point you at a published copy. Check the fingerprint they give you against the one shown when you import it, over a channel you already trust.

Keys

Zoeken: ⌘K
Panels: ⌘1 · ⌘2
Full width: F
All keys: ⌘/

Gerelateerd · Beveiligingstools