如何解决用纯php更新wordpress但用户密码需要保持不变
我想将我的小网站更新为纯 PHP。但是,用户将尝试使用他们的旧密码登录。
但是,我不能再使用 wordpress 身份验证功能了。如何,我将能够做到这一点?
如何验证我的用户?我想,我需要弄清楚wordpress的散列和加盐过程。 在哪里可以找到?
解决方法
WordPress 的默认散列机制是 MD5。并且用户数据存储在db中的wp_users
表中。
因此,您首先要考虑的是如何存储当前网站(非 WordPress)的密码。如您所知,PHP 具有内置的 md5()
函数。
如果您以纯文本格式存储它(根本不推荐),那么您可以简单地遍历当前数据库中的这些密码并将它们插入到 wp_users
表中(在您的新 WordPress 站点中) ),将密码传递给 md5()
函数。
如果您以加密形式存储它,即。稍后可以解密(不推荐),然后您也可以遍历密码,解密它,然后像上面那样插入到 wp_users
表中。
但是如果您使用的是单向加密(散列),并且是 MD5,那么您可以立即将存储在当前数据库中的散列密码插入到 WordPress 数据库中,它应该可以工作!
但如果不是MD5,那将是一项艰巨的任务。在这种情况下,我建议在 WordPress db 中插入用户数据,并在 user_pass
字段中插入临时随机密码。然后向用户发送一封电子邮件,其中包含以编程方式重置密码的链接。 WordPress 有一个名为 get_password_reset_key() 的内置函数,您可以使用类似的方法发送它:https://wordpress.stackexchange.com/a/275269/60666
我找到了确切的解决方案,我一直在寻找。如果你遇到同样的问题,我把它放在这里。
我只想用我的 wordpress 网站哈希验证我的密码。给你!!
您想使用 Core PHP 来实现,对吗?
这是给你的代码!
首先你需要添加一个类:
-> 只需从 wp-includes/class-phpass.php
复制它
-> 别担心。它是用核心 PHP 编写的。
class PasswordHash {
var $itoa64;
var $iteration_count_log2;
var $portable_hashes;
var $random_state;
/**
* PHP5 constructor.
*/
function __construct( $iteration_count_log2,$portable_hashes )
{
$this->itoa64 = './0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz';
if ($iteration_count_log2 < 4 || $iteration_count_log2 > 31)
$iteration_count_log2 = 8;
$this->iteration_count_log2 = $iteration_count_log2;
$this->portable_hashes = $portable_hashes;
$this->random_state = microtime() . uniqid(rand(),TRUE); // removed getmypid() for compatibility reasons
}
/**
* PHP4 constructor.
*/
public function PasswordHash( $iteration_count_log2,$portable_hashes ) {
self::__construct( $iteration_count_log2,$portable_hashes );
}
function get_random_bytes($count)
{
$output = '';
if ( @is_readable('/dev/urandom') &&
($fh = @fopen('/dev/urandom','rb'))) {
$output = fread($fh,$count);
fclose($fh);
}
if (strlen($output) < $count) {
$output = '';
for ($i = 0; $i < $count; $i += 16) {
$this->random_state =
md5(microtime() . $this->random_state);
$output .=
pack('H*',md5($this->random_state));
}
$output = substr($output,$count);
}
return $output;
}
function encode64($input,$count)
{
$output = '';
$i = 0;
do {
$value = ord($input[$i++]);
$output .= $this->itoa64[$value & 0x3f];
if ($i < $count)
$value |= ord($input[$i]) << 8;
$output .= $this->itoa64[($value >> 6) & 0x3f];
if ($i++ >= $count)
break;
if ($i < $count)
$value |= ord($input[$i]) << 16;
$output .= $this->itoa64[($value >> 12) & 0x3f];
if ($i++ >= $count)
break;
$output .= $this->itoa64[($value >> 18) & 0x3f];
} while ($i < $count);
return $output;
}
function gensalt_private($input)
{
$output = '$P$';
$output .= $this->itoa64[min($this->iteration_count_log2 +
((PHP_VERSION >= '5') ? 5 : 3),30)];
$output .= $this->encode64($input,6);
return $output;
}
function crypt_private($password,$setting)
{
$output = '*0';
if (substr($setting,2) == $output)
$output = '*1';
$id = substr($setting,3);
# We use "$P$",phpBB3 uses "$H$" for the same thing
if ($id != '$P$' && $id != '$H$')
return $output;
$count_log2 = strpos($this->itoa64,$setting[3]);
if ($count_log2 < 7 || $count_log2 > 30)
return $output;
$count = 1 << $count_log2;
$salt = substr($setting,4,8);
if (strlen($salt) != 8)
return $output;
# We're kind of forced to use MD5 here since it's the only
# cryptographic primitive available in all versions of PHP
# currently in use. To implement our own low-level crypto
# in PHP would result in much worse performance and
# consequently in lower iteration counts and hashes that are
# quicker to crack (by non-PHP code).
if (PHP_VERSION >= '5') {
$hash = md5($salt . $password,TRUE);
do {
$hash = md5($hash . $password,TRUE);
} while (--$count);
} else {
$hash = pack('H*',md5($salt . $password));
do {
$hash = pack('H*',md5($hash . $password));
} while (--$count);
}
$output = substr($setting,12);
$output .= $this->encode64($hash,16);
return $output;
}
function gensalt_extended($input)
{
$count_log2 = min($this->iteration_count_log2 + 8,24);
# This should be odd to not reveal weak DES keys,and the
# maximum valid value is (2**24 - 1) which is odd anyway.
$count = (1 << $count_log2) - 1;
$output = '_';
$output .= $this->itoa64[$count & 0x3f];
$output .= $this->itoa64[($count >> 6) & 0x3f];
$output .= $this->itoa64[($count >> 12) & 0x3f];
$output .= $this->itoa64[($count >> 18) & 0x3f];
$output .= $this->encode64($input,3);
return $output;
}
function gensalt_blowfish($input)
{
# This one needs to use a different order of characters and a
# different encoding scheme from the one in encode64() above.
# We care because the last character in our encoded string will
# only represent 2 bits. While two known implementations of
# bcrypt will happily accept and correct a salt string which
# has the 4 unused bits set to non-zero,we do not want to take
# chances and we also do not want to waste an additional byte
# of entropy.
$itoa64 = './ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789';
$output = '$2a$';
$output .= chr(ord('0') + $this->iteration_count_log2 / 10);
$output .= chr(ord('0') + $this->iteration_count_log2 % 10);
$output .= '$';
$i = 0;
do {
$c1 = ord($input[$i++]);
$output .= $itoa64[$c1 >> 2];
$c1 = ($c1 & 0x03) << 4;
if ($i >= 16) {
$output .= $itoa64[$c1];
break;
}
$c2 = ord($input[$i++]);
$c1 |= $c2 >> 4;
$output .= $itoa64[$c1];
$c1 = ($c2 & 0x0f) << 2;
$c2 = ord($input[$i++]);
$c1 |= $c2 >> 6;
$output .= $itoa64[$c1];
$output .= $itoa64[$c2 & 0x3f];
} while (1);
return $output;
}
function HashPassword($password)
{
if ( strlen( $password ) > 4096 ) {
return '*';
}
$random = '';
if (CRYPT_BLOWFISH == 1 && !$this->portable_hashes) {
$random = $this->get_random_bytes(16);
$hash =
crypt($password,$this->gensalt_blowfish($random));
if (strlen($hash) == 60)
return $hash;
}
if (CRYPT_EXT_DES == 1 && !$this->portable_hashes) {
if (strlen($random) < 3)
$random = $this->get_random_bytes(3);
$hash =
crypt($password,$this->gensalt_extended($random));
if (strlen($hash) == 20)
return $hash;
}
if (strlen($random) < 6)
$random = $this->get_random_bytes(6);
$hash =
$this->crypt_private($password,$this->gensalt_private($random));
if (strlen($hash) == 34)
return $hash;
# Returning '*' on error is safe here,but would _not_ be safe
# in a crypt(3)-like function used _both_ for generating new
# hashes and for validating passwords against existing hashes.
return '*';
}
function CheckPassword($password,$stored_hash)
{
if ( strlen( $password ) > 4096 ) {
return false;
}
$hash = $this->crypt_private($password,$stored_hash);
if ($hash[0] == '*')
$hash = crypt($password,$stored_hash);
return $hash === $stored_hash;
}
}
你快完成了。
$password = 'binary1001';//password you want to verify
$hasher = new PasswordHash(8,TRUE);
$passnya = '$P$BFG8I1k171qgRKqZvj0K3tn3bBSrsW/';//hash of that password from wp db
// compare plain password with hashed password
if ($hasher->CheckPassword( $password,$passnya )){
echo "MATCHED";
} else {
echo "NO MATCHED";
}
我通过反复试验做到了这一点。现在,是时候进入正题了。 快乐编码!!!
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。