search for: _priv

...looking at the access control entries for the wp > and mw dbs, (in the mysql.db table). Based on what you are trying > here, there should be matching entries in that table for the "Db"s > "jokefire" and "jfwiki" (e.g., for the Host as well as the various > _priv fields). > > select * from db where Db='jokefire' or Db='jfwiki' order by Host\g > > There may be something else going on, but without knowing that the > access control is as it should be there's not much value in > speculating. > > _____________________...

Hey guys, I'm running both a wordpress site as well as a mediawiki off of the same web servers. The mediawiki site works great! The wordpress site, meh. Not so much. I keep getting the common database connection error: Error establishing a database connection And as far as I can tell the settings between the mediawiki site and the wordpress site are nearly identical. Here's the media

...es for the wp > >> and mw dbs, (in the mysql.db table). Based on what you are trying > >> here, there should be matching entries in that table for the "Db"s > >> "jokefire" and "jfwiki" (e.g., for the Host as well as the various > >> _priv fields). > >> > >> select * from db where Db='jokefire' or Db='jfwiki' order by > >> Host\g > >> > >> There may be something else going on, but without knowing that the > >> access control is as it should be there's not muc...

....] I would start by looking at the access control entries for the wp and mw dbs, (in the mysql.db table). Based on what you are trying here, there should be matching entries in that table for the "Db"s "jokefire" and "jfwiki" (e.g., for the Host as well as the various _priv fields). select * from db where Db='jokefire' or Db='jfwiki' order by Host\g There may be something else going on, but without knowing that the access control is as it should be there's not much value in speculating.

...access control entries for the wp >> and mw dbs, (in the mysql.db table). Based on what you are trying >> here, there should be matching entries in that table for the "Db"s >> "jokefire" and "jfwiki" (e.g., for the Host as well as the various >> _priv fields). >> >> select * from db where Db='jokefire' or Db='jfwiki' order by >> Host\g >> >> There may be something else going on, but without knowing that the >> access control is as it should be there's not much value in >> speculat...

...and mw dbs, (in the mysql.db table). Based on what you are > >> >> trying here, there should be matching entries in that table > >> >> for the "Db"s "jokefire" and "jfwiki" (e.g., for the Host as > >> >> well as the various _priv fields). > >> >> > >> >> select * from db where Db='jokefire' or Db='jfwiki' order by > >> >> Host\g > >> >> > >> >> There may be something else going on, but without knowing that > >> >> the...

...gt; >> wp and mw dbs, (in the mysql.db table). Based on what you are >> >> trying here, there should be matching entries in that table >> >> for the "Db"s "jokefire" and "jfwiki" (e.g., for the Host as >> >> well as the various _priv fields). >> >> >> >> select * from db where Db='jokefire' or Db='jfwiki' order by >> >> Host\g >> >> >> >> There may be something else going on, but without knowing that >> >> the access control is as it sho...

...(in the mysql.db table). Based on what you are >> >> >> trying here, there should be matching entries in that table >> >> >> for the "Db"s "jokefire" and "jfwiki" (e.g., for the Host as >> >> >> well as the various _priv fields). >> >> >> >> >> >> select * from db where Db='jokefire' or Db='jfwiki' order by >> >> >> Host\g >> >> >> >> >> >> There may be something else going on, but without knowing that >&g...

...sitive(key->q); + kfree_sensitive(key->dp); + kfree_sensitive(key->dq); + kfree_sensitive(key->qinv); + kfree_sensitive(key->tmp1); + kfree_sensitive(key->tmp2); kfree(key->e); kfree(key->n); memset(key, 0, sizeof(*key)); @@ -1018,17 +1018,17 @@ static void caam_rsa_set_priv_key_form(struct caam_rsa_ctx *ctx, return; free_dq: - kzfree(rsa_key->dq); + kfree_sensitive(rsa_key->dq); free_dp: - kzfree(rsa_key->dp); + kfree_sensitive(rsa_key->dp); free_tmp2: - kzfree(rsa_key->tmp2); + kfree_sensitive(rsa_key->tmp2); free_tmp1: - kzfree(rsa_key->...

...sitive(key->q); + kfree_sensitive(key->dp); + kfree_sensitive(key->dq); + kfree_sensitive(key->qinv); + kfree_sensitive(key->tmp1); + kfree_sensitive(key->tmp2); kfree(key->e); kfree(key->n); memset(key, 0, sizeof(*key)); @@ -1014,17 +1014,17 @@ static void caam_rsa_set_priv_key_form(struct caam_rsa_ctx *ctx, return; free_dq: - kzfree(rsa_key->dq); + kfree_sensitive(rsa_key->dq); free_dp: - kzfree(rsa_key->dp); + kfree_sensitive(rsa_key->dp); free_tmp2: - kzfree(rsa_key->tmp2); + kfree_sensitive(rsa_key->tmp2); free_tmp1: - kzfree(rsa_key->...

...sitive(key->q); + kfree_sensitive(key->dp); + kfree_sensitive(key->dq); + kfree_sensitive(key->qinv); + kfree_sensitive(key->tmp1); + kfree_sensitive(key->tmp2); kfree(key->e); kfree(key->n); memset(key, 0, sizeof(*key)); @@ -1018,17 +1018,17 @@ static void caam_rsa_set_priv_key_form(struct caam_rsa_ctx *ctx, return; free_dq: - kzfree(rsa_key->dq); + kfree_sensitive(rsa_key->dq); free_dp: - kzfree(rsa_key->dp); + kfree_sensitive(rsa_key->dp); free_tmp2: - kzfree(rsa_key->tmp2); + kfree_sensitive(rsa_key->tmp2); free_tmp1: - kzfree(rsa_key->...

v5: - Break the btrfs patch out as a separate patch to be processed independently. - Update the commit log of patch 1 to make it less scary. - Add a kzfree backward compatibility macro in patch 2. v4: - Break out the memzero_explicit() change as suggested by Dan Carpenter so that it can be backported to stable. - Drop the "crypto: Remove unnecessary

v4: - Break out the memzero_explicit() change as suggested by Dan Carpenter so that it can be backported to stable. - Drop the "crypto: Remove unnecessary memzero_explicit()" patch for now as there can be a bit more discussion on what is best. It will be introduced as a separate patch later on after this one is merged. This patchset makes a global rename of the kzfree()

v4: - Break out the memzero_explicit() change as suggested by Dan Carpenter so that it can be backported to stable. - Drop the "crypto: Remove unnecessary memzero_explicit()" patch for now as there can be a bit more discussion on what is best. It will be introduced as a separate patch later on after this one is merged. This patchset makes a global rename of the kzfree()

This patchset makes a global rename of the kzfree() to kfree_sensitive() to highlight the fact buffer clearing is only needed if the data objects contain sensitive information like encrpytion key. The fact that kzfree() uses memset() to do the clearing isn't totally safe either as compiler may compile out the clearing in their optimizer. Instead, the new kfree_sensitive() uses