Hi all! Today I released ngIRCd 21.1, a bug-fix only release for ngIRCd 21. This release doesn't contain new features, but fixes a few "glitches" in ngIRCd 21 that have been reported over the past few months. The NEWS file lists the following: • Don't ignore but use the server password when PAM is compiled in but disabled. Thanks to Roy Sindre Norangshol <roy.sindre@norangshol.no>! • doc/Platforms.txt: Update from master branch. • doc/Services.txt: Update information for Anope 2.x. • configure: add support for the LDFLAGS_END and LIBS_END variables to add linker flags and libraries at the end of the configure run (CFLAGS_END has been implemented already). • Update Copyright notices for 2014 :-) There are no security fixes included, nevertheless all installations should update: ngIRCd 21.1 is fully backwards compatible and the update should be straight forward, no configuration changes are required. You can find the NEWS file (listing all new and changed features) and the ChangeLog file (listing all changes in greater detail) in the distribution archives as well as online: • <http://ngircd.barton.de/doc/NEWS> • <http://ngircd.barton.de/doc/ChangeLog> And even more information can be found here: • Homepage: <http://ngircd.barton.de/> (<http://ngircd.mirror.3rz.org>) • Bug tracker: <http://ngircd.barton.de/bugzilla/> • Downloads: • HTTP 1: <http://ngircd.barton.de/pub/ngircd/> • HTTP 2: <http://ngircd.mirror.3rz.org/pub/ngircd/> Please note: The BerliOS platform is shutting down, so our BerliOS mirror site will become unavailable and all old links to BerliOS will become unreachable! (see <http://developer.berlios.de/forum/forum.php?forum_id=39220>) But don't worry too much, ngIRCd already gained a new mirror site, located at <http://ngircd.mirror.3rz.org>, provided by Götz Hoffart. Thanks a lot! And as usual, a big thanks to all users, bug reporters, contributors, packagers, and supporters! Regards Alex
Alexander Barton <alex@...> writes:
There are no security fixes included, nevertheless all installations should update: ngIRCd 21.1 is fully backwards compatible and the update should be straight forward, no configuration changes are required.
Hello, First of all, i'm a total noob when it comes to IRC and understanding the subtleties of it. However, i use ngircd in the simplest manner as possible just to have a chat between friend, so nothing fancy, no password or anything. It's working fine for me with version 21. I updated to 21.1 and it's a no go for me. I can't connect anymore, i have a "bad password" error. I guess it's coming from this change "Don't ignore but use the server password when PAM is compiled in but disabled.". I have no idea how to get it working again so i had to rollback to 21. I'd appreciate it if you could help me on this. Thank you
Hi Greg! Am 07.05.2014 um 11:46 schrieb Greg <endereoc@gmail.com>:
Alexander Barton <alex@...> writes:
There are no security fixes included, nevertheless all installations should update: ngIRCd 21.1 is fully backwards compatible and the update should be straight forward, no configuration changes are required.
First of all, i'm a total noob when it comes to IRC and understanding the subtleties of it. However, i use ngircd in the simplest manner as possible just to have a chat between friend, so nothing fancy, no password or anything. It's working fine for me with version 21.
I updated to 21.1 and it's a no go for me. I can't connect anymore, i have a "bad password" error. I guess it's coming from this change "Don't ignore but use the server password when PAM is compiled in but disabled.".
Did you check "ngircd --configtest"? Please make sure that you havn't set any "Password" in [Global], and that you either havn't compiled in support for PAM (if you compiled it from source yourself) or that you configured "PAM = No" in [Options] (if you are using a binary that supports PAM). Regards Alex
On 07/05/2014 14:53, Alexander Barton wrote:
Hi Greg!
Did you check "ngircd --configtest"?
Please make sure that you havn't set any "Password" in [Global], and that you either havn't compiled in support for PAM (if you compiled it from source yourself) or that you configured "PAM = No" in [Options] (if you are using a binary that supports PAM).
Regards Alex Hi,
Thank you very much, adding "PAM = No" did the trick. Thanks again :) Greg
Teilnehmer (3)
-
Alexander Barton -
EnderEOC -
Greg