Hello,
I am currently configuring a connection between ngircd 0.8.1 and a machine running irc 2.10.3p5. This failed at first because ngircd restricts passwords to 8 characters in length.
I took a quick glance at RFC 1459, but i couldnt find any specification of a maximum password length, so I bumped CLIENT_PASS_LEN to 17 in src/ngircd/defines.h . Is there a particular reason why it is restricted to 8? (Or why it was chosen in the first place?)
Thanks, Florian
Hi Florian!
I took a quick glance at RFC 1459, but i couldnt find any specification of a maximum password length, so I bumped CLIENT_PASS_LEN to 17 in src/ngircd/defines.h . Is there a particular reason why it is restricted to 8? (Or why it was chosen in the first place?)
It has been choosen because I couldn't find a restriction in the RFCs either, and because UNIX passwords are historically limited to 8 characters. That's it. Not a strong reason ;-)
It should indeed be safe to raise this limit ...
Regards Alex
Alexander Barton alex@barton.de wrote: [Password length limit]
It has been choosen because I couldn't find a restriction in the RFCs either, and because UNIX passwords are historically limited to 8 characters. That's it. Not a strong reason ;-)
Ok, i just looked at the ircd-irc2 sources (more specifically, ircd-irc2_2.10.3p5.orig.tar.gz from backports.org). The Password length is defined to 20 and declared as "char passwd[PASSWDLEN+1];" (in common/struct_def.h).
Perhaps ngircd should do the same for compatibility?
Thanks, Florian
Hi Florian!
Ok, i just looked at the ircd-irc2 sources (more specifically, ircd-irc2_2.10.3p5.orig.tar.gz from backports.org). The Password length is defined to 20 and declared as "char passwd[PASSWDLEN+1];" (in common/struct_def.h).
Perhaps ngircd should do the same for compatibility?
I changed it to "#define CLIENT_PASS_LEN 21": 21 bytes (20 characters plus NULL byte).
Thanks!
Regards Alex
-
Alexander Barton -
Florian Westphal