Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
When I was at Zuken, I set up Kerberos on several of the CentOS servers to authenticate against Active Directory. It took a few tries to work out the details, but once I figured it out, it worked well except when the clocks drifted too far apart. Of course I set it to also allow locally-defined logins, so I could still get admin access if AD was down. In practice the clock drift was only an issue for the two servers that ran under vmware-server. For those I set up an hourly cron job to force a sync using rdate. Ugly, but it got the job done. One thing I found disappointing was that Windows assigned all the uids and gids; I was unable to configure Windows to allow me to assign my own uids, in order to match what was already in use on the Linux servers. Alas, I kept all my notes on the procedure in the Zuken wiki, which I no longer have access to. So I'll have to figure it out all over again next time I need to authenticate against AD. On Sat, Nov 12, 2011 at 7:52 AM, Jerry Feldman <gaf at blu.org> wrote: > On 11/11/2011 04:06 PM, edwardp at linuxmail.org wrote: >> >> I bought a new Netgear router earlier this year, couldn't get the time >> zone out of -08:00 (Pacific), even after going through five "levels" >> of "technical support" at Netgear. ?It was returned for a Cisco. >> >> >> Jim Gasek wrote: >>> I love the $15 refurb netgear wireless routers. >>> Automatically download latest firmware. >>> Automatically enforce security/encryption. >>> >>> There were at least 3 choices under $20. >>> >> > I have never had a netgear router, but I have had many other Netgear > products including 3 24 port GS24TS switches and a ReadyNAS 3100 and > have had zero trouble. The ReadyNAS was somewhat complicated because I > wanted to use it primarily as an NFS server, but also as a CIFS server. > In the Boston office we use different user names/passwords than our > Windows systems. ?The complexity is that I had to maintain a separate > /etc/passwd for ReadyNAS because I needed to use the Windows user names > with the Linux UIDs, we have 3 different name/password combinations but > the tradeoff is that (1) we don't have to expire passwords, (2) I can > use gaf :-), and (3) we are not tied to the corporate network, so if > Internet is down or if Toronto is down, we are still 100% operational. > At one time I was thinking of wring a password coordination system > (probably in Python) because people don't change their Linux passwords > often, it is not necessary. But even a password coordination system > would work easily since you (1) create a map of different user names > (about 3 or 4), Locate the appropriate line in /etc/shadow on the > master, and simply locate the appropriate name on ReadyNAS, and plug the > line into /etc/shadow. > > I've also had Netgear NIC cards. I screwed one up, called Netgear and > easily RMA'd it. > > -- > Jerry Feldman <gaf at blu.org> > Boston Linux and Unix > PGP key id:3BC1EB90 > PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 ?C0AF 7CEA 30FC 3BC1 EB90 > > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://lists.blu.org/mailman/listinfo/discuss > -- John Abreau / Executive Director, Boston Linux & Unix OLD GnuPG KeyID: D5C7B5D9 / Email: abreauj at gmail.com OLD GnuPG FP: 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 2011 GnuPG KeyID: 32A492D8 / Email: abreauj at gmail.com 2011 GnuPG FP:
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |