News for hackers. Stuff that matters.
Re:Hosting Provider Leaked 63M Records Including Magento and... by duckmysick on Thursday November 05, 2020 @07:11AM (#24997533)
What would be a proper way to handle it?
Re:Hosting Provider Leaked 63M Records Including Magento and... by dboreham on Thursday November 05, 2020 @07:42AM (#24997724)
Implement a proxy authentication scheme for the hosted services (WP, etc). Now an admin working for the hosting provider can log in using a password checked against a hash stored in their hosting system. No plaintext passwords stored.
Re:Hosting Provider Leaked 63M Records Including Magento and... by Closi on Thursday November 05, 2020 @02:35PM (#25001186)
> the hosting provider can log in using a password checked

Hmm, but where is this password stored? This sounds like exactly what they were doing!

Re:Hosting Provider Leaked 63M Records Including Magento and... by part1of2 on Thursday November 05, 2020 @07:20AM (#24997585)
They have access to the DB users. You can craft a new user & password-hash pair and insert it into the DB to create your own Wordpress user to manage on their behalf, or the lazy way is to just update the user’s password hash with your own. Then when you fix the issue, revert it. Worked for me years ago, not sure if something fundamental changed