Date: Mon, 31 Jan 2011 10:19:53 +1100 From: Lawrence Stewart <lstewart@freebsd.org> To: Ashish SHUKLA <ashish@freebsd.org> Cc: freebsd-ports@freebsd.org Subject: Re: Adding a PAM config option to net-im/ejabberd Message-ID: <4D45F219.6070207@freebsd.org> In-Reply-To: <86r5buec8e.fsf@chateau.d.if> References: <4D44FD91.7070607@freebsd.org> <86r5buec8e.fsf@chateau.d.if>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/31/11 00:45, Ashish SHUKLA wrote: > Hi Lawrence, > > Lawrence Stewart writes: >> Hi Ashish, > >> What do you think about applying the attached patch to the ejabberd >> port? It installs some parts required to allow ejabberd to auth against >> PAM and is working great for me. > > Sure, I can apply it, once ports freeze is over. I also need to update > ejabberd. I'll do both together. Sounds good, thanks. One question: in order to get PAM auth working, you have to set uid root on the epam bits and chown them appropriately in order to allow things to work. Should the port installation process do these steps as well or should we leave them to the user? I would be inclined to have the port do them so that upgrading the port doesn't break PAM auth after the upgrade. We would want to print a big warning at the end of the port install about the set uid security aspects though. Cheers, Lawrence
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D45F219.6070207>