Hi Esa, thats a bug: The password code for ssh in 5.4 only supports the old password encoding (obfuskation) and not the new PBKDF2 password hashes. Thats fixed in Github now. Regards, Jan -- Jan Willamowius, Founder of the GNU Gatekeeper Project EMail : jan@xxxxxxxxxxxxxx Website: https://www.gnugk.org Support: https://www.willamowius.com/gnugk-support.html Relaxed Communications GmbH Frahmredder 91, 22393 Hamburg, Germany Geschäftsführer: Jan Willamowius HRB 125261 (Amtsgericht Hamburg) USt-IdNr: DE286003584 Esa Nyrhinen via gnugk-users wrote: > Hi, > > I'm a little confused about this. > I set up the usual password protected logins to the status port > and it works just fine but as soon as I flipped SshStatusPort from 0 to 1 > in the config the gatekeeper starts complaining about the passwords > and doesn't want to let me in. The lines in the log look normal > to me: > > STATUS Authentication rule 'explicit' accepted the client > STATUS Authentication rule 'password' accepted the client > STATUS New connection from a.b.c.d:eeee=>f.g.h.i:7000 accepted > > but then it says: > > GK Failed to decode config password for [GkStatus::Auth] => asdf > STATUS Could not find password in the config for user asdf > > Do I need to switch to a different password format or something for ssh? > I've been staring at the code and the logs but I can't figure out why > switching on the ssh would cause this. I've missed something in the docs? > > Regards, > Esa _______________________________________________________ Posting: mailto:gnugk-users@xxxxxxxxxxxxxxx Archive: https://lists.gnugk.org/pipermail/gnugk-users/ Unsubscribe: https://lists.gnugk.org/lists/listinfo/gnugk-users Homepage: https://www.gnugk.org/
