Permalink
Browse files

Merge pull request #21 from jmazzi/patch-1

Fix a typo.
  • Loading branch information...
2 parents d8c1f1b + f77e7b6 commit d28d0973ec08844e4ed82120d7e73dd801662f3c @spikex committed Apr 10, 2012
Showing with 1 addition and 1 deletion.
  1. +1 −1 README.textile
View
@@ -2,7 +2,7 @@ h1. Strongbox
Strongbox provides Public Key Encryption for ActiveRecord. By using a public key sensitive information can be encrypted and stored automatically. Once stored a password is required to access the information.
-Because the largest amount of data that can practically be encrypted with a public key is 245 byte, by default Strongbox uses a two layer approach. First it encrypts the attribute using symmetric encryption with a randomly generated key and initialization vector (IV) (which can just be through to as a second key), then it encrypts those with the public key.
+Because the largest amount of data that can practically be encrypted with a public key is 245 byte, by default Strongbox uses a two layer approach. First it encrypts the attribute using symmetric encryption with a randomly generated key and initialization vector (IV) (which can just be thought of as a second key), then it encrypts those with the public key.
Strongbox stores the encrypted attribute in a database column by the same name, i.e. if you tell Strongbox to encrypt "secret" then it will be store in "secret" in the database, just as the unencrypted attribute would be. If symmetric encryption is used (the default) two additional columns "secret_key" and "secret_iv" are needed as well.

0 comments on commit d28d097

Please sign in to comment.