From 990311318dd9c28fa20ca288454bf0cf0d73909f Mon Sep 17 00:00:00 2001 From: Warren Date: Sun, 17 May 2026 00:43:34 +0800 Subject: [PATCH] fix: Use correct bcrypt hash for demo123 password MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Critical fix: - Previous hash was for admin123, not demo123 - Generated fresh bcrypt hash specifically for 'demo123' - Verified hash with bcrypt::verify() = true ✅ Database updates: - PostgreSQL users.password (demo) - 60 chars ✅ - SQLite sftpgo_users.password_hash (demo) - 60 chars ✅ - PostgreSQL admins.password (admin) - 60 chars ✅ - SQLite sftpgo_admins.password_hash (admin) - 60 chars ✅ Test result: ✅ demo/demo123 login returns token ✅ admin/demo123 login returns token Password (unified): demo123 Test users: - File Tree: demo / demo123 - Settings: admin / demo123 Files: - data/auth.sqlite --- data/auth.sqlite | Bin 73728 -> 73728 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/data/auth.sqlite b/data/auth.sqlite index f025e42607385c54daf2f25d0215bf7e97404250..13e7a0dbc5000370ae56bf3499aaa036eb12ae91 100644 GIT binary patch delta 206 zcmZoTz|wGlWr8&0%84@0tScGxstPuyOqOMgn*2j{BTHVRLgeJNa`S- delta 201 zcmZoTz|wGlWr8&0yooZ-tn(Q3dVg$8nJmi~GWmz>Mi%u(h2Y6+<>mt!DnXM2