I'd like to add a few queries to the drushcore sanitize area. Here's a start.

I'm currently gathering these from http://drupalcode.org/project/infrastructure.git/tree/refs/heads/master:... (which of course inspired and also draw from http://drupalscout.com/knowledge-base/creating-sanitized-drupal-database... )

CommentFileSizeAuthor
#8 paranoia.drush_.inc_.txt2.08 KBgreggles
#2 1565686_sanitize_more_thorough_2.patch2.34 KBgreggles
#1 1565686_sanitize_more_thorough.patch934 bytesgreggles

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Needs review
StatusFileSize
new 1565686_sanitize_more_thorough.patch934 bytes
greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
StatusFileSize
new 1565686_sanitize_more_thorough_2.patch2.34 KB

Patch in #1 included what is currently in the common.raw.sql.

This patch includes code from common.dev.sql

moshe weitzman’s picture

moshe weitzman commented

I would remove the users_data item since I think that could cripple developers who are using these sanitized copies. I understand why some sites would want this sanitized, and they should use a Contrib project for it.

I'm not too inclined to partially delete those blocked users. That leaves the DB in an inconsistent state. Whats the use case for removing these? Might be better done in Contrib as well.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Yeah, the more paranoid of these can live in...paranoia.drush.inc ;)

The inconsistent db state (nodes or comments referring to non-existent users) should be cleaned up by later patches I'm working on. I think the motivation is creating a database that, if accidentally exposed to the world, would show expose no new information beyond what is publicly visible in a typical Drupal site.

moshe weitzman’s picture

moshe weitzman commented
Status: Needs review » Needs work
greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

I think emails and passwords are the main things to "fix" and those are already handled. The rest of these are a bit more extreme and maybe could all live in paranoia. Are you in favor of any of these being in drush? They only get more paranoid from here...

moshe weitzman’s picture

moshe weitzman commented
Project: Drush » Paranoia
Version: » 7.x-1.x-dev
Component: SQL » Code
Status: Needs work » Active

OK, I committed the truncate for sessions table into core drush. The rest can go to paranoia

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Needs work
StatusFileSize
new paranoia.drush_.inc_.txt2.08 KB

So, this doesn't work, but it's a start.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Needs work » Fixed

Now committed - http://drupalcode.org/project/paranoia.git/commit/45cea70

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.