- WLUG - wlug.mailman3.com

ACM Installfest has been moved...

by Ryan Caron

Due to conflicting events on campus, we have moved the date of the Installfest. It is now scheduled for April 4th from 3 to 7PM. It will be in Higgins Lab 116. Please email acm(a)wpi.edu if you have any questions or are able to attend for even a portion of the event. Sincerely, Ryan Caron ACM Secretary

March 17, 2004

Re: [Wlug] Network configuration with OpenLDAP

by Matt Higgins

Here are some places to start, http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory?version=1 http://www.padl.com/Contents/OpenSourceSoftware.html -Matt Quoting Michael Long <mlong(a)datalong.com>: > Karl Hiramoto wrote: > > >What services do you need? > > > >linux shell logins? > > > > > > > Yes > > >samba logins? > > > > > Yes > > >imap/pop logins? > > > > > Yes, > > As Chuck pointed out earlier this is not a simple task. Since I have > never managed a multiuser *nix evironment I believe the best thing for > me to do is follow the KISS principle and attack the problem one piece > at a time. > > The first step is to setup a robust multiuser environment that allows > clients to authenticate onto the network via linux shells. These users > will initially login either at the console or remotely via SSH. Ideally > a VPN will be eventually be added to the mix. The next step will be to > setup samba to allow clients to authenticate onto the network via > windows. Finally setup ldap and migrate the authentication services to it. > > > > >I was also looking into this at my work. I setup a ldap server, I'm > >using it now for an address book, but i have not setup any logins yet. > > > >>From my reading, i understand you need to configure each server (samba, > >imap, etc) to auth to the ldap. > > > > > > > > > >>Hi, > >> > >>My goal is to set up a small business network that will have both linux > >>and windows > >>clients. I would like to use OpenLDAP for my authentication services. The > >>problem > >>is that I have never done anything like this and don't know where to > >>start. I have > >>read the docs at openldap.org, LDAP-HOWTO, LDAP-Implementation-HOWTO, > >>http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/pam.html and am > >>not sure > >>where to start. I would like to start by building the services that will > >>allow me > >>to authenticate users and configure file shares that they have access to. > >>Which > >>service(s) should I start with PAM, LDAP, other? > >> > >>Thanks, > >>Mike > >> > >>_______________________________________________ > >>Wlug mailing list > >>Wlug(a)mail.wlug.org > >>http://mail.wlug.org/mailman/listinfo/wlug > >> > >> > >> > > > > > > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > >

March 17, 2004

Re: [Wlug] Network configuration with OpenLDAP

by Michael Long

Karl Hiramoto wrote: >What services do you need? > >linux shell logins? > > > Yes >samba logins? > > Yes >imap/pop logins? > > Yes, As Chuck pointed out earlier this is not a simple task. Since I have never managed a multiuser *nix evironment I believe the best thing for me to do is follow the KISS principle and attack the problem one piece at a time. The first step is to setup a robust multiuser environment that allows clients to authenticate onto the network via linux shells. These users will initially login either at the console or remotely via SSH. Ideally a VPN will be eventually be added to the mix. The next step will be to setup samba to allow clients to authenticate onto the network via windows. Finally setup ldap and migrate the authentication services to it. >I was also looking into this at my work. I setup a ldap server, I'm >using it now for an address book, but i have not setup any logins yet. > >>From my reading, i understand you need to configure each server (samba, >imap, etc) to auth to the ldap. > > > > >>Hi, >> >>My goal is to set up a small business network that will have both linux >>and windows >>clients. I would like to use OpenLDAP for my authentication services. The >>problem >>is that I have never done anything like this and don't know where to >>start. I have >>read the docs at openldap.org, LDAP-HOWTO, LDAP-Implementation-HOWTO, >>http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/pam.html and am >>not sure >>where to start. I would like to start by building the services that will >>allow me >>to authenticate users and configure file shares that they have access to. >>Which >>service(s) should I start with PAM, LDAP, other? >> >>Thanks, >>Mike >> >>_______________________________________________ >>Wlug mailing list >>Wlug(a)mail.wlug.org >>http://mail.wlug.org/mailman/listinfo/wlug >> >> >> > > >

March 17, 2004

Re: [Wlug] Network configuration with OpenLDAP

by Charles R. Anderson

On Tue, Mar 16, 2004 at 05:46:06PM -0500, Michael Long wrote: > Hi, > > My goal is to set up a small business network that will have both linux and windows > clients. I would like to use OpenLDAP for my authentication services. The problem > is that I have never done anything like this and don't know where to start. I have > read the docs at openldap.org, LDAP-HOWTO, LDAP-Implementation-HOWTO, > http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/pam.html and am not sure > where to start. I would like to start by building the services that will allow me > to authenticate users and configure file shares that they have access to. Which > service(s) should I start with PAM, LDAP, other? This isn't going to be easy. Here are a few pointers I found on Google: http://www.bayour.com/LDAPv3-HOWTO.html http://lists.samba.org/archive/samba/2003-November/002398.html http://www.nyetwork.org/fvlug/Fvlug_Samba3.ppt

March 16, 2004

Network configuration with OpenLDAP

by Michael Long

Hi, My goal is to set up a small business network that will have both linux and windows clients. I would like to use OpenLDAP for my authentication services. The problem is that I have never done anything like this and don't know where to start. I have read the docs at openldap.org, LDAP-HOWTO, LDAP-Implementation-HOWTO, http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/pam.html and am not sure where to start. I would like to start by building the services that will allow me to authenticate users and configure file shares that they have access to. Which service(s) should I start with PAM, LDAP, other? Thanks, Mike

March 16, 2004

Fwd: consulting assistance

by Andy Stewart

If anybody has any interest in this opportunity, please contact Ralph Fasano directly at rfasano(a)risd.edu. -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

March 16, 2004

Re: [Wlug] Open source = security

by Michael Long

Thanks to everyone who replied. I am now able to explain the benefits of open source much more clearly. I have since had a very interesting followup conversation with the architect and I believe he may be starting to understand the benefit of open source. Mike

March 12, 2004

Re: [Wlug] Open source = security

by Theo Van Dinter

On Fri, Mar 12, 2004 at 11:09:37AM -0500, Michael Long wrote: > guess it is not. I was wondering how others would answer this question? I was working at RSA Security for a while, and my manager gave me the same sort of line: We make security products here, you definitely don't want that open source! <some other reference about open source being less secure> My response was along the lines of: Actually, that's _exactly_ the software I would want open source. Security through obscurity (which is what most non-open source relies on) doesn't work. He wasn't happy. <G> Anyway, yeah, "real" security people want as many people looking at their code/algorithm/etc as possible to make sure it's secure in and of itself. There's reasons that things like MD5, SHA1, AES, etc, all went through a rigorous review process before they're made a "standard". -- Randomly Generated Tagline: s Blind, Lingerie makes Great Braille!

March 12, 2004

Re: [Wlug] Open source = security

by orbitz＠ezabel.com

The security of an application is not hidden in a trick in the code but the algorithm it is using. Being able to see the code (assuming it were bug free) should never reveal a bug in the security framework. Obfuscation is not security. On Fri, 12 Mar 2004 11:09:37 -0500 (EST) "Michael Long" <mlong(a)datalong.com> wrote: > Hi, > > During a discussion with an application architect, while trouble shooting SQL > Servers "security" behavior, he asked how an application can be more secure > when anyone can view the security related code. I thought this was self > evident, but I guess it is not. I was wondering how others would answer this > question? > > Thanks, > Mike > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

March 12, 2004

Re: [Wlug] Open source = security

by Scott Venier

It's all about auditing. The more people who can look at the code can find AND FIX any bugs. And the bugs do get fixed. For historical evidence of that look at how quickly the Linux kernel was fixed when the "teardrop" bug was revealed. It took Windows much longer to release a patch. There are probably more recent examples, but that's the first one that comes to mind that effected both open and closed source software. This is the excat same reason that professional software developers have code reviews. Many eyes make all problems simple. Scott Michael Long said: > Hi, > > During a discussion with an application architect, while trouble shooting > SQL > Servers "security" behavior, he asked how an application can be more > secure when > anyone can view the security related code. I thought this was self > evident, but I > guess it is not. I was wondering how others would answer this question? > > Thanks, > Mike > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

March 12, 2004