Re: debian packages for woody and sarge

2004-09-19 Thread Aime
OK. I did what you suggested but now I have problem
with OpenSSL. It cannot find Openssl. But it is ther ,
I know.
I just compiled Openssl on the machine.

How can I use dpkg-buildpackage -uc -us -b -rfakeroot
but forcing configure to use parameter 
--with-openssl-includes=/usr/local/openssl/include ?




--- Paul Hampson [EMAIL PROTECTED] wrote:

 On Sat, Sep 18, 2004 at 05:40:02AM -0700, Aime
 wrote:
  Hello Marcus, 
  
  Please can you layout here the steps you did to
 get
  freeradius compiled on Woody.
  
  I tried what you said in your mail (by commenting 
  dh_installpam --name=radiusd ), but still get
  dependency problems about libsasl2-dev and
 debhelper.
 
 After removing the dh_installpam line, you can take
 the versioning off the debhelper dependancy.
 
 And for woody, change libsasl2-dev to libsasl-dev.
 
 Then dpkg-buildpackage -us -uc -b -rfakeroot should
 work.
 
 I'd also recommend adding a new debian/changelog
 entry,
 so you can tell your package from anyone else's. ^_^
 
 -- 
 Paul TBBle Hampson, on an alternate email client.
 
 - 
 List info/subscribe/unsubscribe? See
 http://www.freeradius.org/list/users.html
 




___
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


Re: debian packages for woody and sarge

2004-09-19 Thread Paul Hampson
On Sun, Sep 19, 2004 at 08:24:13AM -0700, Aime wrote:
 OK. I did what you suggested but now I have problem
 with OpenSSL. It cannot find Openssl. But it is ther ,
 I know.
 I just compiled Openssl on the machine.

Do you also have the OpenSSL package? I'd suggest not
building a local copy, but using the 0.9.7 packaged in
Woody. That'll keep you in security fixes too. ^_^

 How can I use dpkg-buildpackage -uc -us -b -rfakeroot
 but forcing configure to use parameter 
 --with-openssl-includes=/usr/local/openssl/include ?

You add that configure option to debian/rules. Don't
forget the trailing backslash for the previous line. ^_^

-- 
Paul TBBle Hampson, on an alternate email client.

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


Re: lotus notes ldap

2004-09-19 Thread J.R. Cabanban

Check your recommendation...

radiusd.conf is per your comment...

To make it work I had to make users
per below...

#DEFAULTAuth-Type = System
#Fall-Through = 1

DEFAULT Auth-Type = LDAP
Fall-Through = 1

Q.Per My understanding
the Auth-Type = System should have been check then
move on to the
LDAP auth... At least per my results it is not... How does one
fix the fall-through
feature?







Dustin Doris [EMAIL PROTECTED]

Sent by: [EMAIL PROTECTED]
09/17/2004 07:15 AM



Please respond to
[EMAIL PROTECTED]





To
[EMAIL PROTECTED]


cc



Subject
Re: lotus notes ldap










On Thu, 16 Sep 2004, J.R. Cabanban wrote:

 command: radtest arookie  localhost 1 sharedsecret

 response: rad_recv: Access-Reject packet from host 127.0.0.1:1812,
id=61,
 length=20

 snapshot of radiusd -X -A

 rad_recv: Access-Request packet from host 127.0.0.1:32847, id=53,
 length=59
 User-Name = arookie
 User-Password = *
 NAS-IP-Address = 255.255.255.255
 NAS-Port = 1
  Processing the authorize section of radiusd.conf
 modcall: entering group authorize for request 1
  modcall[authorize]: module preprocess returns ok
for request 1
  modcall[authorize]: module chap returns noop for
request 1
  modcall[authorize]: module mschap returns noop
for request 1
   rlm_realm: No '@' in User-Name = arookie,
looking up realm NULL
   rlm_realm: No such realm NULL
  modcall[authorize]: module suffix returns noop
for request 1
  rlm_eap: No EAP-Message, not doing EAP
  modcall[authorize]: module eap returns noop for
request 1
   users: Matched DEFAULT at 152
   users: Matched DEFAULT at 155
  modcall[authorize]: module files returns ok for
request 1
 rlm_ldap: - authorize
 rlm_ldap: performing user authorization for arookie
 radius_xlat: '(uid=arookie)'
 radius_xlat: 'cn'
 rlm_ldap: ldap_get_conn: Checking Id: 0
 rlm_ldap: ldap_get_conn: Got Id: 0
 rlm_ldap: performing search in cn, with filter (uid=arookie)
 rlm_ldap: looking for check items in directory...
 rlm_ldap: looking for reply items in directory...
 rlm_ldap: user arookie authorized to use remote access
 rlm_ldap: ldap_release_conn: Release Id: 0
  modcall[authorize]: module ldap returns ok for
request 1
 modcall: group authorize returns ok for request 1
  rad_check_password: Found Auth-Type System
 auth: type System
  Processing the authenticate section of radiusd.conf
 modcall: entering group authenticate for request 1
  modcall[authenticate]: module unix returns notfound
for request 1
 modcall: group authenticate returns notfound for request 1
 auth: Failed to validate the user.
 Delaying request 1 for 1 seconds
 Finished request 1

 Q. did the ldap server properly authenticated the user 
allow access. if
 so why did the final result was Access-Reject?


Ldap authorized the user, but then you have it set to use System to
authenticate. These are two separate procedures. Check radiusd.conf
and
make sure you have ldap in the authorize section.

Uncomment this part, if you haven't already.
#Auth-Type LDAP {
#ldap
#}

-Dusty Doris


- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html