Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[oth-Tech] Sharing Authentication between Windows and Linux

On Feb 26, 2004, at 4:12 PM, Dan Barrett wrote:
> Samba can become part of a domain:

Thats not exactly what we want... We would want Samba to BE the PDC 
(which I know it can do), while authenticating via NIS.

> ... and samba can authenticate via NIS:

Hum, that might be helpful.

> Couldn't you just make the filesystem available _both_ via NFS and 
> Samba?  So,
> if you're a UNIX client you'd go through NFS and authenticate via NIS,
> ignoring SMB.  If you're a Windows client, you'd go through Samba, 
> which
> would in turn authenticate against your PDC.

The trouble is that NFS file permissions are maintained by NIS, and SMB 
file permissions are maintained by the PDC. The Snapserver looks to NIS 
for NFS permissions, and to the PDC for SMB permissions, even for 
shares that are accessible via both protocols.

If you locked a user out of a directory via the PDC, they could use 
their Unix account via NFS, and still modify the files, since the 
authentication is done via NIS. The goal is so solve this by unifying 
the NIS and PDC into one database.

I noticed SuSe Server 8 can be a PDC. Can it also be an NIS server 
using the same database?

Bush/Cheney '04:
Compassionate Colonialism.

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /