Description of problem:
In looking at the configuration file, there appears to be PAM support, however it needs to be compiled. In discussing with Kevin its currently not compiled with those options.
Feature does not work
ngircd-21.1-2.fc20 has been submitted as an update for Fedora 20.
ngircd-21.1-2.fc19 has been submitted as an update for Fedora 19.
ngircd-21.1-2.el6 has been submitted as an update for Fedora EPEL 6.
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing ngircd-21.1-2.el6'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Breaks my existing ngircd config. Not sure why yet.
So, it appears that the added PAM support is on by default and requires all users to authenticate with it. I was also completely unable to de-activate PAM with:
PAM = no
PAMIsOptional = yes
So I was completely unable to make this version work for me.
I should state that this is on EL6.
My reading of the docs was that it was disabled by default... sorry about that.
Would you be willing to file upstream on this?
Or would you prefer I do so?
Well, if you already have an ngircd bugzilla account, I'd prefer if you would. Happy to help test things out though.
"How does your ngircd.conf look like?
"ngircd --configtest" validates the configuration without errors?
"PAM=no" in an "[options]" section should disable PAM altogether … and at least
it seems to work for me.
Apparently I have let my ngircd.conf file stagnate while ngircd has moved on (understandable on EL I believe) as I didn't even have an [Options] section. In fact the Fedora package's provided /etc/ngircd.conf file doesn't have it either, seems like it has stagnated as well.
Moving PAM=no there works for me. However, I don't think that fixes the EPEL (and other) update issue - anyone without PAM=no in ngircd.conf file (which I think is likely everyone) will have their behavior change dramatically.
Yeah, we can (and should) update the config file we ship by default from the template, however the file is config/noreplace, so I agree we definitely don't want to push this to stable releases. ;(
Should we just push this in rawhide and add a release note for f21 for folks to sync their config then? Or should we just drop the idea entirely?
Oh no! Could we ask to have it disabled by default upstream and only explicitly enable it if PAM=yes? Is that even a valid request to do?
I was doing a new install and i happen to use the upstream example, so i never noticed the problem mentioned.
I've reopened the upstream bug to ask if there could be a way to default to no when pam is build in and there's no PAM= directive. Will see what they say.
I've also unpushed all these updates (but not yet reverted anything in git).
ok, I've come up with a new plan thanks to upstream. ;)
We enable pam.
We ship a /etc/pam.d/ngircd that calls pam_permit.so
That way folks that want to use pam, can simply change the /etc/pam.d/ngircd, and everyone else can ignore it.
Can you test these scratch builds:
I'm afraid I didn't test before the builds were cleaned up, but it seems reasonable.
ok. I have pushed this fix to f22/f21.
Was el6 also wanted?
whoah! I've totally forgot about this.
it would think putting it on el6 would be a good idea. I can't see a negative in doing it.
ngircd-21.1-5.el6 has been submitted as an update for Fedora EPEL 6.
ngircd-21.1-5.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.