As it stands now, the module needs the key file to be writable at all times, even if the key file already exists and has a key inside. This patch allows administrators to set permissions on the key file to be read-only, to protect against accidental (or malicious) overwrites. Patch attached.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Status: Needs review » Needs work

The last submitted patch, encrypt.install.patch, failed testing.

Nathan Goulding’s picture

Not sure why this didn't pass. Can someone take a look?

Nathan Goulding’s picture

Version: 6.x-1.0-rc5 » 6.x-1.0
Nathan Goulding’s picture

Status: Needs work » Needs review

encrypt.install.patch queued for re-testing.

Status: Needs review » Needs work

The last submitted patch, encrypt.install.patch, failed testing.

greggles’s picture

@Nathan Goulding - see the "view details" link "SummaryFAILED: [[SimpleTest]]: [MySQL] Unable to apply patch encrypt.install.patch. See the log in the details link for more information."

From reading the log it looks like it could be an issue with the way the branches are setup.

davidwhthomas’s picture

Here's an adjusted version of the patch for D7

greggles’s picture

For what it's worth: I believe this feature already works properly in the 7.x-2.x branch.

gisle’s picture

Issue summary: View changes
Status: Needs work » Closed (outdated)

Drupal 6 is depreciated.