Date: Mon, 6 Oct 1997 22:08:20 +0100 From: Ian Vaudrey <i.vaudrey@cableinet.co.uk> To: "'ports@freebsd.org'" <ports@freebsd.org> Subject: RE: Cyrus port pwcheck daemon Message-ID: <01BCD2A4.5C6ABDA0@nemkoltd.nildram.co.uk>
next in thread | raw e-mail | index | archive | help
Many thanks, chmod g+w /var/pwcheck/pwcheck did the trick. I don't think I'd have found that without your help. Could you let me have a copy of your patch? I've been patching the port to use Tcl 8.0. The patched version - now that I can actually test Cyradm - seems to work as it should so I'm close to submitting a pr. If it's OK with you, I'll incorporate your umask patch so there won't be conflicting change requests for the port. - Ian On 06 October 1997 12:40, Tom wrote: > > On Mon, 6 Oct 1997, Ian Vaudrey wrote: > > > Does anyone know if something has changed in 2.2-STABLE (cvsup'ed > > and world made Oct 2nd) that would break the pwcheck daemon in > > the Cyrus port? I have it working on a 2.2.2-RELEASE box, but > > after building it on the STABLE machine it refuses to authenticate. > > I've even tried copying the daemon executable from the working > > unit with no luck. > > Yes, something has changed. UNIX domain sockets now apply the umask > permissions. You will find that /var/pwcheck/pwcheck can written to by > the Cyrus user. > > You can change the permissions (chmod o+rw /var/pwcheck/pwcheck will > work) after starting pwcheck. Do a "umask 0" before starting pwcheck > should also work. I placed a umask() call right in the pwcheck daemon. I > should probably submit my patch! > > > - Ian > > Tom > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01BCD2A4.5C6ABDA0>