ankane / ankane/lockbox

Idea: Ability to disable automatic encryption/decryption in a block

Open
#208 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
1.6k
Forks
78
PR merge metrics
No merged PRs in 30d

Description

Related to #181, it looks like the main thing needed to be able to build an integration with Console1984 is the ability to disable automatic decryption/encryption within a block. This could have other use cases as well.

ActiveRecord encryption supports two modes: without_encryption and protecting_encrypted_data. The former saves data into the ciphertext unencrypted. The latter prevents writing to an encrypted attribute at all.

We could support both for parity, but even just supporting one of them would be helpful.

Happy to dig into this, but wanted to validate whether this is something you would be willing to support.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by reviewing the block encryption/decryption behavior and related issue #181, then determine whether to support ActiveRecord's without_encryption, protecting_encrypted_data, or both; done means a block can explicitly disable automatic encryption/decryption as intended.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.