For the oper passwords I used the /mkpasswd md5 password command to get an encrypted hash and put that in the opers.conf file.
This worked perfectly with no problems up until I restarted my server earlier today, when I could no longer oper when connecting to my server. I stopped my server, changed the password to an unhashed value for my oper account, started the server again, used the /mkpasswd command again, and then put what was returned into the opers.conf file in place of the plaintext password before rehashing the configuration files again, after which I could oper again using my original password with no problems again.
The following is my opers.conf file:
Note: I have left the password for my account unhashed for now, and so have starred it out. The password for my bot's account is hashed, but I have starred certain parts of that out to ensure the security of my server.oper Vista {
class clients;
from {
userhost *;
};
password "*";
flags
{
netadmin;
can_die;
can_restart;
can_zline;
can_gkline;
can_gzline;
get_umodew;
get_host;
can_override;
can_addline;
};
snomask +cFfkejvGnNqsSo;
};
oper Ace {
class clients;
from {
userhost *;
};
password "*vSdtOpN1*k6Vqaw==";
flags
{
netadmin;
can_zline;
can_gzline;
can_gkline;
can_die;
can_restart;
global;
can_rehash;
helpop;
can_globops;
can_wallops;
};
snomask +cFfkejvGnNqsSo;
};
Is it normal for the password hash to change on restarting the server, and if not, has anyone got any idea what could be causing the issue?
Edit: I have just tried hashing exactly the same password on both servers on our network, and a different value was returned by each server despite the password being the same each time. However, I would guess that this cannot be normal behaviour since it would cause major problems if a server with hundreds or even thousands of operators went down for a restart and all their passwords were encrypted.