> On Sun, 6 Jan 2002 20:42:16 -0500,
> Ken Murchison <[EMAIL PROTECTED]> (km) writes:
km> Yeah. We're trying not to have generated files in CVS (just source files). So
km> mdoc would be considered one of the "tools" that you need if you want to use
km> the code from CVS.
Thanks to y
Quoting Amos Gouaux <[EMAIL PROTECTED]>:
> > On Sat, 08 Dec 2001 10:43:17 -0500,
> > Ken Murchison <[EMAIL PROTECTED]> (km) writes:
>
> km> I think that this is because the preformatted saslauthd.8 in the
> km> distribution hasn't been updated from the saslauthd.mdoc source. If
> you
>
On Sat, 5 Jan 2002, Amos Gouaux wrote:
> km> nroff -mdoc saslauthd.mdoc > saslauthd.8
> km> make install
>
> And if you don't? Looks like cyrus-sasl from CVS runs this by
> default in the 'install' target, and on a Solaris system without
> mdoc macros it blows up. So this means, unless I'm mist
> On Sat, 08 Dec 2001 10:43:17 -0500,
> Ken Murchison <[EMAIL PROTECTED]> (km) writes:
km> I think that this is because the preformatted saslauthd.8 in the
km> distribution hasn't been updated from the saslauthd.mdoc source. If you
km> have the mdoc macros, just run:
km> nroff -mdoc sas
On Sat, 8 Dec 2001, Ken Murchison wrote:
> nroff -mdoc saslauthd.mdoc > saslauthd.8
> make install
Sadly it looks like saslauthd.mdoc didn't make it into the release. I've
attached an updated version to this message.
-Rob
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
R
[EMAIL PROTECTED] wrote:
>
> Rob Siemborski schrieb am Fri, Dec 07, 2001 at 09:53:33PM -0500:
> * saslauthd links the pam libraries just like libsasl used to in SASLv1.
> *
> * libsasl2 now connects to a unix domain socket, which saslauthd is
> * listening to, presents the username and password
Rob Siemborski schrieb am Fri, Dec 07, 2001 at 09:53:33PM -0500:
* saslauthd links the pam libraries just like libsasl used to in SASLv1.
*
* libsasl2 now connects to a unix domain socket, which saslauthd is
* listening to, presents the username and password, and saslauthd consults
* pam, and rep
> On Sat, 08 Dec 2001 01:42:17 -0500,
> Vincent Stoessel <[EMAIL PROTECTED]> (vs) writes:
vs> It sound like a very well designed change I will defintely be playing with this
vs> one, I am tired of creating users on the system for mail accts.
This saslauthd also has much better logging th
Rob Siemborski wrote:
> saslauthd links the pam libraries just like libsasl used to in SASLv1.
>
> libsasl2 now connects to a unix domain socket, which saslauthd is
> listening to, presents the username and password, and saslauthd consults
> pam, and replies either yes or now. This is similar t
How then does pam interface with the new saslauthd?
Rob Siemborski wrote:
> On Fri, 7 Dec 2001, Robert Scussel wrote:
>
>
>>My imapd.conf file looks like so:
>> configdirectory: /var/spool/imapdb
>> partition-default: /var/spool/imap
>> sasl_pwcheck_method: PAM
>> reject
saslauthd links the pam libraries just like libsasl used to in SASLv1.
libsasl2 now connects to a unix domain socket, which saslauthd is
listening to, presents the username and password, and saslauthd consults
pam, and replies either yes or now. This is similar to how pwcheck works.
To start sa
On Fri, 7 Dec 2001, Robert Scussel wrote:
> My imapd.conf file looks like so:
> configdirectory: /var/spool/imapdb
> partition-default: /var/spool/imap
> sasl_pwcheck_method: PAM
> reject8bit: no
SASLv2 no longer makes use of the many internal pwcheck methods that it
used
12 matches
Mail list logo
