Re: libpam related buildworld failures

1999-02-03 Thread Alex Zepeda
Speaking of pam, when will it be fixed to support all the various service
types?  Or is that a do it yourself project?

- alex


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: libpam related buildworld failures

1999-02-03 Thread John Polstra
Alex Zepeda wrote:
 Speaking of pam, when will it be fixed to support all the various service
 types?  Or is that a do it yourself project?

As you know, questions of the form when will X happen rarely get
useful answers around here.  So here's my useless answer: When it's
finished. :-) I'm working on it as fast as my available time permits.

John
---
  John Polstra   j...@polstra.com
  John D. Polstra  Co., Inc.Seattle, Washington USA
  Nobody ever went broke underestimating the taste of the American public.
-- H. L. Mencken

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: libpam related buildworld failures

1999-02-03 Thread Alex Zepeda
On Wed, 3 Feb 1999, John Polstra wrote:

 Alex Zepeda wrote:
  Speaking of pam, when will it be fixed to support all the various service
  types?  Or is that a do it yourself project?
 
 As you know, questions of the form when will X happen rarely get
 useful answers around here.  So here's my useless answer: When it's
 finished. :-) I'm working on it as fast as my available time permits.

Well I should have rephrased that.  I was curious if anyone knew about it
or was working on it.  What exactly needs to be done here (I know next to
nothing about pam)?

- alex


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: libpam related buildworld failures

1999-02-03 Thread John Polstra

Alex Zepeda wrote:
 
 Well I should have rephrased that.  I was curious if anyone knew about it
 or was working on it.  What exactly needs to be done here (I know next to
 nothing about pam)?

Well, if by service types you meant login, ftp, telnet, etc., then
what needs to be done is to convert ftpd, telnetd, etc. to use PAM
instead of doing their own authentication.  For ftpd that will require
a few relatively minor PAM module fixes having to do with the fact
that FTP as viewed from the server is sort of an event-driven machine
rather than an interactive conversation.

That's what my near-term focus is on.

If you instead meant things like support for RADIUS accounting, that's
just waiting for somebody to come along and implement the necessary
support in libradius and the corresponding PAM module.

John
---
  John Polstra   j...@polstra.com
  John D. Polstra  Co., Inc.Seattle, Washington USA
  Nobody ever went broke underestimating the taste of the American public.
-- H. L. Mencken

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: libpam related buildworld failures

1999-02-03 Thread Alex Zepeda
No I meant service as in authentication types or tasks whatever ya call
it.  From the man page:


   PAM separates the tasks of authentication into four  inde-
   pendent management groups: account management; authentica-
   tion management; password management; and session  manage-
   ment.   (We  highlight  the  abbreviations  used for these
   groups in the configuration file.)


authentication works.. but everything else gives unresolved (or defined)
symbols...  so kdm, xdm, and samba don't work with pam on FreeBSD (well
those are the ones I've tried).

- alex


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: libpam related buildworld failures

1999-02-03 Thread John Polstra

Alex Zepeda wrote:
 No I meant service as in authentication types or tasks whatever ya call
 it.  From the man page:

Well, service type is a specific term in PAM that refers to things
like login, ftp, ppp, and so forth.

PAM separates the tasks of authentication into four  inde-
pendent management groups: account management; authentica-
tion management; password management; and session  manage-
ment.   (We  highlight  the  abbreviations  used for these
groups in the configuration file.)
 
 
 authentication works.. but everything else gives unresolved (or defined)
 symbols...  so kdm, xdm, and samba don't work with pam on FreeBSD (well
 those are the ones I've tried).

That's what I meant by:

If you instead meant things like support for RADIUS accounting,
that's just waiting for somebody to come along and implement the
necessary support in libradius and the corresponding PAM module.

I'm going to work now.  Gotta keep food on the table.  Bye! :-)

John
---
  John Polstra   j...@polstra.com
  John D. Polstra  Co., Inc.Seattle, Washington USA
  Nobody ever went broke underestimating the taste of the American public.
-- H. L. Mencken

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: libpam related buildworld failures

1999-02-03 Thread Alex Zepeda
On Wed, 3 Feb 1999, John Polstra wrote:

 That's what I meant by:
 
 If you instead meant things like support for RADIUS accounting,
 that's just waiting for somebody to come along and implement the
 necessary support in libradius and the corresponding PAM module.

No.  I don't want/need radious support.  kdm and samba only do password
authentication AFAIK, why they don't use the auth method (or whatever) I
don't know.  They work without Radius and without Pam.. but that doesn't
fix the underlying problem

 I'm going to work now.  Gotta keep food on the table.  Bye! :-)

Have fun! ;)

- alex


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message