empus
commented
4 years ago That password needs to be md5 hashed, which is why it's not working.
It's better to just insert any pass value and update 'curnick' to your current nickname and 'curhost' to your current user@host. Then let autologin authenticate you. Then once authenticated you can use 'newpass' to set your password for manual logins in future.
Passwords are actually optional tough. You can just rely on autologin.
on SSH sqlite3 armour.db SQLite version 3.27.2 2019-02-25 16:06:06 Enter ".help" for usage hints. sqlite> INSERT INTO users (user,xuser,level,pass) VALUES('user1','user1',500,'foo' ); sqlite> .quit
on IRC [21:17:40] <(s)pop> Rehashing. [21:17:40] <(s)pop> [21:17:39] Rehashing ... (all went well) [21:17:44] >pop< login user1 foo [21:17:44] <(s)pop> [21:17:44] triggering bind userdb:msg:login [21:17:44] <(s)pop> [21:17:44] userdb:uline:get: userlist get pass where user=user1 [21:17:44] <(s)pop> [21:17:44] userdb:uline:get: userlist get user where user=user1 [21:17:44] <(s)pop> [21:17:44] userdb:msg:login password mismatch for tabb, login failed [21:17:44] <(s)pop> [21:17:44] triggered bind userdb:msg:login, user 0.342ms sys 3.485ms [21:17:44] -pop- login failed.