Just found this
http://drupal.org/project/encrypted_text

It is for D4 though :)

It would be cool though to have a checbox on CCK Text field config screen to encrypt submissions. :)

Perhaps it would make the module more popular as well, since it would shield users from any programming.

Comments

giorgio79’s picture

giorgio79 CreditAttribution: giorgio79 commented

And a new one for D7
http://drupal.org/project/encset, it seems like this is a field integration, quite nice.

jdwfly’s picture

jdwfly CreditAttribution: jdwfly commented

I actually created a module that integrates into this module to encrypt cck fields for D6. Never committed it though, but if there was enough interest I might put it in my sandbox.

giorgio79’s picture

giorgio79 CreditAttribution: giorgio79 commented

Would love it. I think the adoption of these encryption modules is hindered by their developer focus. As simple as a checkbox on CCK fields to encrypt them would give them some incentive to grow :)

Meanwhile though I had to come up with sg for my site, and I put up a little example for others here
#1143106: Usage example for encrypting and decrypting fields

jdwfly’s picture

jdwfly CreditAttribution: jdwfly commented

Basically that is what my module did. Just a simple check box on the configuration page for a field and you could either encrypt or not. What I did not do was work out particulars about converting previous data from encrypted to decrypted and so forth. I would need some feedback about what people think should happen to that data that is already there.

giorgio79’s picture

giorgio79 CreditAttribution: giorgio79 commented

If we expose encrypt and decrypt functions as action hooks, they can be included in a VBO, and users can put their site in offline mode, do a backup and encrypt existing node fields.

Also, this could be enabled for text cck types I guess.

zzolo’s picture

zzolo CreditAttribution: zzolo commented

Good thoughts. I would love to see this happen. My time for this module is pretty slim these days.

My question though, is this: Say a user is inputting data, and chooses to "Encrypt" it. From the user's perspective, is user assuming the data will be encrypted only to the user, or only to the site. Meaning that the former would require the user to enter in a password for the encryption. If I was given the option to encrypt data, I would assume it was encrypted only to me, not to the site.

giorgio79’s picture

giorgio79 CreditAttribution: giorgio79 commented

I think these are two different use cases.

First one is where all instanced of a CCK field are encrypted with a key stored somewhere by the webmaster like the http://www.drupal.org/project/aes module

The 2nd, is what zzolo just described, that is enabling a user to protect a field by entering their password, and using that as key to encryption (as I understand). I saw a module that takes care of the password stuff here: http://drupal.org/project/protected_node, although I dont see any encryption in the db.

I guess both options have merit :)

jdwfly’s picture

jdwfly CreditAttribution: jdwfly commented

Module I created is in my sandbox.

http://drupal.org/sandbox/jdwfly/1085708

giorgio79’s picture

giorgio79 CreditAttribution: giorgio79 commented

Great stuff, works fine for me!

This is the missing piece from the Encryption API module :)

jdwfly’s picture

jdwfly CreditAttribution: jdwfly commented

It's definitely not complete, but it does work. Like I said before if you go changing from encrypted/decrypted midstream after data has already been input you will have some data encrypted and some not. It doesn't decrypt or encrypt any data that is already in the database, just new data. It is something you set once and leave it.

theunraveler’s picture

theunraveler CreditAttribution: theunraveler commented

I would encourage you to release this as a contrib module separate from Encryption API.

As indicated by the name of the module, Encryption API is meant to be an API module. It is meant to provide low-level functionality that other modules/code can use. It is not designed to cater to one specific use case.

theunraveler’s picture

theunraveler CreditAttribution: theunraveler commented
Status: Active » Closed (won't fix)
giorgio79’s picture

giorgio79 CreditAttribution: giorgio79 commented

An API is a great thing, but I guess integration with CCK in D6 and Fields in D7 would cover like 80% of the use cases?

crossmedia’s picture

crossmedia CreditAttribution: crossmedia commented

You may integrate Encrypt module with CCK fields as well, as i done for one of my client and you can visit here http://drupal.org/node/754466