reidmorrison.com valid

Symmetric Encryption

Symmetric Encryption encrypts data at rest in Ruby and Rails applications using OpenSSL, with the encryption keys held outside of the source code in a keystore. It encrypts Active Record attributes, Mongoid fields, passwords in configuration files, and entire files and streams of any size. Every encrypted value records which key version encrypted it, so keys can be rotated without re-encrypting existing data or taking the application down.

For agents: Ruby/Rails library docs for encrypting data at rest with OpenSSL: Active Record and Mongoid fields, config passwords, files and streams, with key rotation.

rubyrailssymmetric-encryptionopensslencryption-at-restkey-rotation

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T16:48:50.054Z. Cached copy · Source on reidmorrison.com

# Symmetric Encryption

> Symmetric Encryption encrypts data at rest in Ruby and Rails applications using OpenSSL, with the encryption keys held outside of the source code in a keystore. It encrypts Active Record attributes, Mongoid fields, passwords in configuration files, and entire files and streams of any size. Every encrypted value records which key version encrypted it, so keys can be rotated without re-encrypting existing data or taking the application down.

Key facts:

- Install with `gem install symmetric-encryption` or `gem "symmetric-encryption"` in a Gemfile. Requires Ruby 3.2 or later, and Rails 7.2 or later when used with Rails.
- If everything you need to encrypt is an Active Record attribute, prefer Rails' built-in [Active Record encryption](https://guides.rubyonrails.org/active_record_encryption.html). This gem covers what that does not: Mongoid fields, whole files and streams, standalone Ruby, passwords in `database.yml`, keys in AWS KMS or Google Cloud KMS, and rotating the key of a queryable (deterministic) value.
- Generate a configuration file and keys with `symmetric-encryption --generate --app-name my_app`. `config/symmetric-encryption.yml` belongs in source control; the key files it points at never do.
- Encrypted Active Record attributes are declared `attribute :ssn, :encrypted`. The database column is always `string` or `text`, whatever the attribute's declared type.
- `symmetric-encryption --generate` writes `aes-256-gcm`, which is authenticated: it detects any change to an encrypted value. `aes-256-cbc`, generated by earlier versions, keeps data secret but does not detect tampering. A cipher entry that omits `cipher_name` still defaults to `aes-256-cbc`, so existing configurations are unaffected.
- Human-readable documentation lives at https://encryption.reidmorrison.com. The links below point at the raw markdown sources of the same pages.
- The complete documentation concatenated into a single file: https://encryption.reidmorrison.com/llms-full.txt
- Source code: https://github.com/reidmorrison/symmetric-encryption

## Documentation

- [Introduction](https://raw.githubusercontent.com/reidmorrison/symmetric-encryption/main/docs/index.md): What Symmetric Encryption is, whether you need it given Active Record encryption exists, a quick start, and how ciphers, the binary header, and keystores fit together.
- [Guide](https://raw.githubusercontent.com/reidmorrison/symmetric-encryption/main/docs/guide.md): The library one step at a time, from encrypting a single string to model attributes, choosing a type, making a value searchable, keeping values out of logs and JSON, encrypting a password in a configuration file, and encrypting a file.
- [Configuration](https://raw.githubusercontent.com/reidmorrison/symmetric-encryption/main/docs/configuration.md): `symmetric-encryption.yml`, deploying keys, and every keystore: file, environment variable, Heroku, AWS KMS, and Google Cloud KMS. Includes key file permissions and ownership
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=reidmorrison.com · GET /v1/domain/reidmorrison.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for reidmorrison.com:
1. POST https://agentwebmap.com/v1/sites/reidmorrison.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://reidmorrison.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/reidmorrison.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/reidmorrison.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.