NIS: Providing naming services to legacy clients.

Slides:

Advertisements

Similar presentations

Domain Name System. DNS is a client/server protocol which provides Name to IP Address Resolution.

Advertisements

Naming Computer Engineering Department Distributed Systems Course Asst. Prof. Dr. Ahmet Sayar Kocaeli University - Fall 2014.

1 DNS. 2 BIND DNS –Resolve names to IP address –Resolve IP address to names (reverse DNS) BIND –Berkeley Internet Name Domain system Version 4 is still.

NIS Consistent configuration across the network. Why NIS? Primary reason is to provide same user configuration across the network Users go any machine.

Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.

Directory & Naming Services CS-328 Dick Steflik. A Directory.

CS603 Directory Services January 30, Name Resolution: What would you like? Historical? –Mail –Telephone DNS? X.500 / LDAP? DCE? ActiveDirectory?

File System Variations and Software Caching May 19, 2000 Instructor: Gary Kimura.

NFS. The Sun Network File System (NFS) An implementation and a specification of a software system for accessing remote files across LANs. The implementation.

© 2005 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice Advanced Samba Administration Part.

DHCP. DHCP (Dynamic Host Configuration Protocol) is a network service that enables clients to obtain network settings (IP Address, Subnet Mask, Default.

Lecture – Single Login NIS and Winbind. NIS Network Information Service (NIS) is the traditional directory service on UNIX platforms Still widely used.

Linux Networking #2 Dr. Michael L. Collard 1.

Windows Server 2008 R2 Domain Name System Chapter 5.

Introduction To OpenLDAP Directory Services. What is a Directory Service? A specialized database optimized for reading, browsing, and searching. No complicated.

Chapter 17 Domain Name System

1 Application Layer Lecture 6 Imran Ahmed University of Management & Technology.

Setting up NIS and HTTP. Network Information Service Reading: 1. Linux NIS HOWTO: howto/HOWTOhttp://

Least-Privilege Isolation: The OKWS Web Server Brad Karp UCL Computer Science CS GZ03 / M th December, 2008.

ICN and DTN NetInf over BP using BPQ Elwyn Davies Folly Consulting Ltd/Trinity College Dublin or

Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.

Using RADIUS as a AAA backbone for Windows networks Kostas Kalevras NTUA Network Operations Centre.

1/14 Char 18 Sharing System Files Content –NIS(The Network Information Service) –NIS+

1 Network Information System (NIS). 2 Module – Network Information System (NIS) ♦ Overview This module focuses on configuring and managing Network Information.

GRID Centralized Management of the Globus grid-mapfile Carlo Rocca, INFN Catania.

Linux Operations and Administration

Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.

1 Security of NIS (YP) Gary Lam

Directory Services CS5493/7493. Directory Services Directory services represent a technological breakthrough by integrating into a single management tool:

Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.

Domain Name System: DNS To identify an entity, TCP/IP protocols use the IP address, which uniquely identifies the Connection of a host to the Internet.

The Web Web Design. 3.2 The Web Focus on Reading Main Ideas A URL is an address that identifies a specific Web page. Web browsers have varying capabilities.

Web Protocols and Practice

Indexing Goals: Store large files Support multiple search keys

CIT 470: Advanced Network and System Administration

Introduction to LDAP Frank A. Kuse.

Programming Assignment #1

Chapter 2: System Structures

BOOTP and DHCP Objectives

Net 323 D: Networks Protocols

Chapter 19 Domain Name System (DNS)

Chapter 3: Windows7 Part 4.

Name and Address Conversions Part I

Lecture 7: Name and Directory Servers

Things that are nice to know when you’re doing this project

Lecture 7: Name and Directory Servers

Multiple Processor Systems

Lecture 8: Name and Directory Servers

Distributed File Systems

CIT 470: Advanced Network and System Administration

Chapter 25 Domain Name System

Distributed File Systems

HTML5 and Local Storage.

Distributed File Systems

DNS: Domain Name System

Multiple Processor and Distributed Systems

Linux and TCP/IP Networking

Chapter 15: File System Internals

Chapter 25 Domain Name System

COMPUTER NETWORKS PRESENTATION

LO3 – Understand Business IT Systems

Traditional Internet Applications

Programming Assignment #1

Distributed File Systems

MapReduce: Simplified Data Processing on Large Clusters

Least-Privilege Isolation: The OKWS Web Server

Paging Andrew Whitaker CSE451.

Domain Name Server Presented By: Mahesh Venkat Adusumelli

Presentation transcript:

NIS: Providing naming services to legacy clients. -Or- NIS: The Shocking Truth

The Client POV Application asks the C library (libc) for passwd info. The library gets the domain name from the kernel and the RPC server address from ypbind's bindings file. The library issues an RPC request: yp_match(map=“passwd.byname”, key=“jimbo”) The library gets an answer “leeroy:*:1234:5678:Leeroy Jenkins:/home/leeroy:/bin/bash” The library parses the result and hands a structure back to the application.

What's Going On Here? The NIS protocol is about a dozen RPC calls. The NIS data model. Groups (maps) of key/value pairs. Key and data formats are opaque to the server. Map names and key/value formats determined by client convention. Data from maps is parsed by the client. Providing a NIS protocol server which uses a directory server as a data store shouldn't be that hard, right? Right?

Those RPCs in detail (1). YPPROC_XFR Pull fresh data from the master server. YPPROC_CLEAR Clear any caches, close/reopen on-disk databases. YPPROC_ORDER Return map generation. YPPROC_MASTER Return hostname of master for domain.

Those RPCs in detail (2). Do we service a given domain? YPPROC_DOMAIN/YPPROC_DOMAIN_NONACK Do we service a given domain? YPPROC_MATCH Look up one entry in a map using a key. YPPROC_FIRST/YPPROC_NEXT Retrieve first key/value pair, or the pair which follows this key. YPPROC_ALL Dump all key/value pairs for a map. YPPROC_MAPLIST Return list of known maps.

Strategies? New daemon which queries the directory server as needed? Alternate ypserv makefile? Authentication? Server reconnection (daemon)? Search limits, paging? Server as SLAPI module? Unusual lifecycle / privilege model. Potential for starving LDAP clients. Potential “ick” factor. Handling enumeration results consistently... hard?

Status Stuck in drawing-board phase. The “sn” SLAPI plugin... (no real “there” there!)

Wherein I Blow Your Mind The trick is hiding the complexity. This is not a new idea. Proprietary offerings abound. HP/UX SFU NIS is lighter than lightweight. The chicken may be the Tyrannosaurus Rex's closest living relative.