Exception occurs with empty string about crypt_keeper HOT 7 CLOSED

@Capncavedan which encryptor are you using?

from crypt_keeper.

The default AES encryptor, like so:

crypt_keeper :social_security_number, encryptor: :aes, key: "super secret"

from crypt_keeper.

One option I can think of is creating a "strict" mode for the AES encryptor, and others really. That would be the default mode. In strict mode, you would receive errors for nil or empty values, like you currently do. In non strict mode:

crypt_keeper :social_security_number, encryptor: :aes, key: "super secret", strict: false

the original value you would be returned for nil or empty strings for decrypt and encrypt. It would look something like this:

def encrypt(value)
  if value.blank? && strict_mode
    value
  else
    # encryption
  end
end

def decrypt(value)
  if value.blank? && strict_mode
    value
  else
    # decryption
  end
end

How do you feel about creating a pull request to do that?

from crypt_keeper.

@Capncavedan let me know what you think about that.

from crypt_keeper.

I think that sounds pretty good, @jmazzi.

I'll work on a pull request.

Note that nil and non-empty strings, e.g. " ", don't generate problems with AES, at least in my experience so far. Just the empty string.

from crypt_keeper.

Hmm, well I'm not sure that's a issue with crypt_keeper then. Non empty strings have a value.

On Friday, March 8, 2013 at 5:07 PM, Dan Buettner wrote:

I think that sounds pretty good, @jmazzi (https://github.com/jmazzi).
I'll work on a pull request.
Note that nil and non-empty strings, e.g. " ", don't generate problems with AES, at least in my experience so far. Just the empty string.

—
Reply to this email directly or view it on GitHub (#31 (comment)).

from crypt_keeper.

closed by #35

from crypt_keeper.