DOCSLIB.ORG

Resolving Names in DNS the NAME GAME

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Resolving Names in DNS the NAME GAME SYSADMIN Admin Workshop: Resolvers Insider Tips: Resolving Names in DNS THE NAME GAME www.sxc.hu The resolver is the window from your computer to the global DNS system. Simply typing a URL awakens a link to computers all over the world. BY MARC ANDRÉ SELIG emory artists can memorize a the server to resolve a name to an IP grams actually use the library functions. list of over 300 numbers, but address. Some of them just do their own thing. Mothers might find it hard to The idea behind this roll-your-own remember even the four numbers that The Resolver approach is to avoid the kinds of block- make up an IP address. Most people The interface that provides a means for ages that can occur when using the glibc agree that a name is easier to remember an application to access name resolution functions. Many shell tools were than a number. The advantage of associ- services is commonly known as the designed as debugging tools and thus ating an object with an alphanumeric resolver. One popular approach for inte- provide direct network access. And for name is the real reason for the existence grating name resolution with a Linux another thing, many of these tools are of the huge, globally distributed Domain application is through the GNU C Library static builds, meaning that the resolver Naming System (DNS), a system that (glibc) functions. The most common routines use specific (and often obso- links computer names and addresses functions are gethostbyname(), which lete) library versions. around the world. translates a name into an IP address, and The DNS system has been the subject gethostbyaddr() for going the opposite Settings of countless articles and books, most of direction. This interface, and its auxil- The resolver can use various data them focused on the naming system iary functions, are increasingly being sources. The simplest data source is the itself or on DNS servers such as Berkeley replaced by a more flexible version, /etc/hosts file (Listing 1), which contains Internet Name Domain (BIND). But on which uses getaddrinfo() to translate a list of numerical addresses and corre- the other end of the connection is an hostnames into IP addresses and sponding names. Each address can be application on a simple desktop com- getnameinfo() for the opposite direction. mapped to one or more names. puter that needs a means of contacting Most scripting languages provide com- The records in the hosts file consist of parable functions; for example, Perl has an address and one or more names, as Marc André Selig gethostbyname() and gethostbyaddr(). well as blank lines and comments. The spends half of his The more recent variants are not avail- listing has various types of entries: the time working as a able – in Perl’s case, they are part of a localhost 127.0.0.1 entry is common to scientific assistant separate module that provides IPv6 all /etc/hosts files, as it is required for at the University of Trier and as an compatibility. local interprocess communications. The ongoing medical Additional resolver tools are available second address block contains important doctor in the Schramberg hospital. at shell level, such as the now obsolete IPv6 addresses. The third block shows If he happens to find time for it, his nslookup tool or the more recent host how addresses on the local network can THEAUTHOR current preoccupation is program- and dig tools. be added to the local database, offering a ing web based databases on various The tricky thing about handling names simple way of handling domain names Unix platforms. and addresses is the fact that not all pro- outside of the local domain. If the 68 ISSUE 59 OCTOBER 2005 WWW.LINUX - MAGAZINE.COM resolver fails to find a order in which the methods �������� requested hostname in /etc/ should be applied. hosts rep- hosts, it can contact a net- resents the local address list work based DNS service such in the /etc/hosts file, and bind ��������������� as BIND. The client can refer refers to network-based to its /etc/resolv.conf file access to the DNS system. (Listing 2) for the address of The multi on entry shown the name server; the file can here means that /etc/hosts either be created manually or can have multiple entries for by the DHCP client. the same name. Normally, up to three dif- The file tells the resolver to ferent name server entries are check /etc/hosts first, to see if permitted. The second and the required name or address third entries are only used if is listed there. If this search the name servers with higher- does not come up with the ranking entries do not re- goods, the DNS service is spond. The options rotate then used; in this case, the entry in Listing 2 changes resolver uses the configura- this behavior for a LAN, tion in /etc/resolv.conf. providing a simple means Host.conf predates glibc of distributing the load across 2.x; that is, it corresponds to multiple machines. libc.so.5 or earlier. Current versions of glibc now use the Sources name service switch from The resolver needs to know Solaris 2 and support a flexi- which of these databases are ble configuration of arbitrary ���������������������������������� available to which Linux sys- lookup services in a freely ���������������������������� tem and in which order they configurable order. ��������������������������������� should be used. This infor- Name service switching is mation is stored in various configured in /etc/nsswitch. ���������������������������������� configuration files. conf (Listing 3). The file con- �������� The original configuration tains a list of services and file for this purpose was /etc/ data sources, as well as a ������������������������������ host.conf. The file might look description of the desired ������������������������������������ like this: behavior. The hosts service is relevant to name resolution; ��������������������������������� order hosts,bind the strategy indicated here, ��������������������������������� multi on files dns, is the default and means that /etc/hosts should ������������������������������ The most important keyword be used first, followed by a ��������������� here is order, followed by the DNS request. �������������������������������� Listing 1: /etc/ hosts �������������������������������� 01 127.0.0.1 localhost.localdomain localhost ishi ������������������������� 02 ������������������ 03 # The following lines are desirable for IPv6 capable hosts ���������� 04 ::1 localhost.localdomain localhost ip6-localhost ip6-loopback 05 fe00::0 ip6-localnet 06 ff00::0 ip6-mcastprefix 07 ff02::1 ip6-allnodes 08 ff02::2 ip6-allrouters 09 ff02::3 ip6-allhosts 10 ���������������� 11 172.16.45.1 natrouter ������������������� 12 216.92.94.3 sedacon.pair.com ������������������������������������ SYSADMIN Admin Workshop: Resolvers Listing 2: /etc/ resolv.conf an hourly rate, avoiding DNS queries can suggest using firewall rules to prevent save you a lot of money. undesirable DNS queries. 01 nameserver 172.16.45.2 Admins can delete the bind from /etc/ 02 nameserver 172.16.45.3 host.conf and dns from /etc/nsswitch. Keeping in Line 03 options rotate conf to stop the glibc resolver from All of the mechanisms we have dis- accessing the network. However, this cussed are implementation specific. There are more configuration files. will also stop the client from talking to a Although each flavor of Unix has its own Sendmail is just one example of a pro- name server on the LAN. default resolver, the details of the gram that has its own resolver library. If you need to use a tunnel – such as a implementations will differ. For example, The configuration is similar to glibc’s VPN – for confidential work, you will BSD uses a different host.conf format, service switch but not identical. The either need to avoid DNS queries or and Solaris has /etc/netconfig, a method private configuration file for sendmail is direct them through the tunnel. In many that replaces the service switch with a titled /etc/mail/service.switch. It only cases, all you need to do is to configure private library. ■ supports the passwd, hosts, and aliases the system to dispatch email via IP services. Sendmail does not use colons addresses or add the domain name to / Listing 3: /etc/ nsswitch. to separate service names, but other etc/hosts. This leaves the browser as the conf Example than that, /etc/mail/service.switch is very most common instigator of DNS queries. 01 passwd: compat similar to /etc/nsswitch.conf. A Socks-4a proxy, such as privoxy for 02 group: compat example, will serve you well in this case 03 shadow: compat No Net because it allows you to reroute DNS 04 In some circumstances network requests lookups to the other end of the tunnel. may be undesirable. For example, if you Considering the variety of potential 05 hosts: files dns have a modem or DSL, and are charged resolvers, best security practices would 06 networks: files How DNS Came About and How it Still Works The future was looking bleak. With user recipe for success is decentralization. and the addresses they map to for a numbers booming, the procedures that Instead of a single authority for an domain. The name server may assign had served ARPANET, the Internet prede- unimaginably large number of net- responsibility for subdomains to other cessor, well in the seventies now were worked computers, the system calls for a name servers. collapsing. And one of these procedures kind of group leadership, where an entity If a client is interested in discovering the was the process for mapping names to is responsible for a group of computers address for a specific name, it contacts addresses. The network's admins had known as a domain, and domains them- the name server for its own domain. If simply maintained a large file for this selves can be subdivided into subdo- the name server does not have the purpose, and everyone on the network mains.
Load more

Recommended publications
  • Pluggable Authentication Modules
    Who this book is written for This book is for experienced system administrators and developers working with multiple Linux/UNIX servers or with both UNIX and Pluggable Authentication Windows servers. It assumes a good level of admin knowledge, and that developers are competent in C development on UNIX-based systems. Pluggable Authentication Modules PAM (Pluggable Authentication Modules) is a modular and flexible authentication management layer that sits between Linux applications and the native underlying authentication system. The PAM framework is widely used by most Linux distributions for authentication purposes. Modules Originating from Solaris 2.6 ten years ago, PAM is used today by most proprietary and free UNIX operating systems including GNU/Linux, FreeBSD, and Solaris, following both the design concept and the practical details. PAM is thus a unifying technology for authentication mechanisms in UNIX. This book provides a practical approach to UNIX/Linux authentication. The design principles are thoroughly explained, then illustrated through the examination of popular modules. It is intended as a one-stop introduction and reference to PAM. What you will learn from this book From Technologies to Solutions • Install, compile, and configure Linux-PAM on your system • Download and compile third-party modules • Understand the PAM framework and how it works • Learn to work with PAM’s management groups and control fl ags • Test and debug your PAM confi guration Pluggable Authentication Modules • Install and configure the pamtester utility
    [Show full text]
  • Strong Distributed Authentication Architecture for UNIX Ashwin Ganti
    University of Illinois at Chicago Strong Distributed Authentication Architecture for UNIX by Ashwin Ganti A PROJECT SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE MASTER OF SCIENCE in COMPUTER SCIENCE Approved, MASTERS PROJECT COMMITTEE Jon Solworth, Adviser Associate Professor of Computer Science V.N. Venkatakrishnan Assistant Professor of Computer Science Chicago, Illinois December, 2007 This project is dedicated to my family. Acknowledgments I would like to thank my adviser Jon Solworth for his invaluable guidance throughout the course of the research for this project and for having been most patient and supportive of me during the entire duration of my time in graduate school. Ashwin 2 Contents 1 Introduction 7 2 Overview of the Frameworks used 9 2.1 PAM........................................ 10 2.2 Name Service Module . 11 2.3 IPSec . 12 3 System Design 12 3.1 Statics . 12 3.1.1 Modules of the system . 12 3.1.2 Relation between the Modules . 13 3.1.3 SayAnything Certificates Used . 13 3.1.4 Relation between certificates . 15 3.2 Dynamics - Logical Flow . 17 4 System Internals 18 4.1 pam sayAnything . 18 4.2 nss sayAnything . 18 4.2.1 getpwuid (uid t uid) . 19 4.2.2 getpwnam (char* name) . 20 4.2.3 setpwent (void) . 20 4.2.4 getpwent (void) . 20 4.2.5 endpwent (void) . 21 4.3 sayAnything Agent . 21 4.3.1 Overview . 22 4.3.2 Logical Flow . 22 4.4 Certificate Server . 24 3 4.4.1 Add Certificate . 24 4.4.2 Get Certificate . 24 5 System Administration 25 5.1 pam sayAnything .
    [Show full text]
  • IT Acronyms.Docx
    List of computing and IT abbreviations /.—Slashdot 1GL—First-Generation Programming Language 1NF—First Normal Form 10B2—10BASE-2 10B5—10BASE-5 10B-F—10BASE-F 10B-FB—10BASE-FB 10B-FL—10BASE-FL 10B-FP—10BASE-FP 10B-T—10BASE-T 100B-FX—100BASE-FX 100B-T—100BASE-T 100B-TX—100BASE-TX 100BVG—100BASE-VG 286—Intel 80286 processor 2B1Q—2 Binary 1 Quaternary 2GL—Second-Generation Programming Language 2NF—Second Normal Form 3GL—Third-Generation Programming Language 3NF—Third Normal Form 386—Intel 80386 processor 1 486—Intel 80486 processor 4B5BLF—4 Byte 5 Byte Local Fiber 4GL—Fourth-Generation Programming Language 4NF—Fourth Normal Form 5GL—Fifth-Generation Programming Language 5NF—Fifth Normal Form 6NF—Sixth Normal Form 8B10BLF—8 Byte 10 Byte Local Fiber A AAT—Average Access Time AA—Anti-Aliasing AAA—Authentication Authorization, Accounting AABB—Axis Aligned Bounding Box AAC—Advanced Audio Coding AAL—ATM Adaptation Layer AALC—ATM Adaptation Layer Connection AARP—AppleTalk Address Resolution Protocol ABCL—Actor-Based Concurrent Language ABI—Application Binary Interface ABM—Asynchronous Balanced Mode ABR—Area Border Router ABR—Auto Baud-Rate detection ABR—Available Bitrate 2 ABR—Average Bitrate AC—Acoustic Coupler AC—Alternating Current ACD—Automatic Call Distributor ACE—Advanced Computing Environment ACF NCP—Advanced Communications Function—Network Control Program ACID—Atomicity Consistency Isolation Durability ACK—ACKnowledgement ACK—Amsterdam Compiler Kit ACL—Access Control List ACL—Active Current
    [Show full text]
  • Implementing Infiniband on IBM System P
    Front cover Implementing InfiniBand on IBM System p Understanding and exploiting InfiniBand HPC and commercial solution explored AIX 5L V5.3 and SLES 9 implementation Dino Quintero Norbert Conrad Rob Desjarlais Marc-Eric Kahle Jung-Hoon Kim Hoang-Nam Nguyen Tony Pirraglia Fernando Pizzano Robert Simon Shi Lei Yao Octavian Lascu ibm.com/redbooks International Technical Support Organization Implementing InfiniBand on IBM System p September 2007 SG24-7351-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (September 2007) This edition applies to Version 5, Release 3, Modification 4, APAR IY84006 of AIX 5L, of SUSE LINUX Enterprise Server 9 for POWER Service Pack 3, SLES 9 SP3 and Release 6, Version 1.0 and APAR MB01795 of the Hardware Management Console (HMC). © Copyright International Business Machines Corporation 2007. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . x Preface . xi The team that wrote this book . xi Become a published author . xiv Comments welcome. xv Part 1. InfiniBand architecture. 1 Chapter 1. Introduction. 3 1.1 Introduction to InfiniBand. 4 Chapter 2. Introduction to InfiniBand technology . 7 2.1 A technical introduction to InfiniBand . 9 2.2 Markets . 10 2.3 Application clustering . 11 2.4 I/O architectures: fabric versus bus. 12 2.4.1 Shared bus architecture . 13 2.4.2 New interconnects compliment InfiniBand . 13 2.4.3 Bandwidth out of the box. 14 2.5 InfiniBand technical overview .
    [Show full text]
  • Oracle Solaris Administration Naming and Directory Services
    Oracle® Solaris Administration: Naming and Directory Services Part No: 821–1455–11 December 2011 Copyright © 2002, 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract,and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
    [Show full text]
  • Computer System Administration. Topic 3. Active Directory Integration Mechanisms: PAM + NSS (Sssd)
    Computer System Design and Administration Topic 3. Active directory integration mechanisms: PAM + NSS (SSSd) José Ángel Herrero Velasco Department of Computer and Electrical Engineering This work is published under a License: Creative Commons BY-NC-SA 4.0 Computer System Design and Administration Topic 3. Active directory integration mechanisms: PAM + NSS (SSSd) Secure information service: Puzzle Information server LDAP clients Active Directory client Open OpenLDAP LDAP model LDAP DB SSL SSL service ” SSL Main SSH server sign-on ISC ISC ISC Third-party service DHCP DNS NTP client services Secondary Single Single Open “ LDAP DB service SSH client LDAP SSL SSL Replicated José Ángel Herrero Velasco Computer System Design and Administration Topic 3. Active directory integration mechanisms: PAM + NSS (SSSd) Target: The Single Sing-On mechanisms • Implementaon and development of a secure and centralized system for the management of account and computa*onal informaon in an enterprise (corporave) environment, using LDAP protocol. – Single Sing-On INTEGRATION mechanisms: • LDAP ac?ve directory Open DB LDAP LDAP • Centralized idenficaon and authencaon aware versions of C-library rou)nes – Identy NSS. SSSd (all in one). – Authen?cate PAM. José Ángel Herrero Velasco Computer System Design and Administration Topic 3. Active directory integration mechanisms: PAM + NSS (SSSd) PAM: Definition & features • P.A.M: Pluggable Authen+ca+on Modules: – Ini)ally developed by Sun Microsystems (Oracle) from 1995 (RFC 86.0). • Definion: – It’s a suite of shared libraries that: • Enables integrang mul+ple authen*caon schemas into an API which is used by applicaons: – PAM-aware applica?ons, through this API, are able to select the authencaon mechanism(s) that it uses: » Currently, by default.
    [Show full text]
  • IBM Security Directory Server: Troubleshooting Guide Operation Times out
    IBM Security Directory Server Version 6.3.1 Troubleshooting Guide GC27-2752-01 IBM Security Directory Server Version 6.3.1 Troubleshooting Guide GC27-2752-01 Note Before using this information and the product it supports, read the general information under “Notices” on page 147. Edition notice Note: This edition applies to version 6.3.1 of IBM Security Directory Server licensed program (product number 5724-J39 ) and to all subsequent releases and modifications until otherwise indicated in new editions. Contents Figures ..............vii Installation with the installation wizard ....28 Uninstallation with the installation wizard . 32 Tables ...............ix Chapter 5. Migration issues ......33 About this publication ........xi Migration log files ............33 Kerberos service name...........33 Access to publications and terminology .....xi Database instance or database in configuration file Accessibility ..............xii but no longer on system ..........33 Technical training ............xiii Format of backed-up schema files is incorrect . 34 Support information ...........xiii ibm-slapdPlugin entry in configuration file changed 34 Statement of Good Security Practices .....xiii Considerations for migration ........34 Chapter 1. Introduction to problem Chapter 6. Instance creation and determination and troubleshooting . 1 configuration issues .........37 Directory server overview ..........1 Instance creation overview and common errors . 37 Built-in troubleshooting features ........1 Instance creation overview ........37 Tools for troubleshooting a directory server instance 1 Cannot create another instance because of invalid Error Message Reference ..........2 IP address ..............38 Information about troubleshooting .......2 idssethost command does not recognize second IP address ..............38 Chapter 2. Utilities for logging .....5 Two directory instances use the same port number...............39 Chapter 3. Other diagnostic tools .
    [Show full text]
  • One Identity Authentication Services Administration Guide
    One Identity Authentication Services 4.2.2 Administration Guide Copyright 2019 One Identity LLC. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of One Identity LLC . The information in this document is provided in connection with One Identity products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of One Identity LLC products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, ONE IDENTITY ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON- INFRINGEMENT. IN NO EVENT SHALL ONE IDENTITY BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF ONE IDENTITY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. One Identity makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice.
    [Show full text]
  • Security with LDAP
    Security with LDAP Andrew Findlay Skills 1st Ltd www.skills-1st.co.uk February 2002 [email protected] Security with LDAP ● Applications of LDAP ● White Pages ● NIS (Network Information System) ● Authentication ● Lots of hype ● How much of it works? [email protected] Network Information Service ● Many in service: ● YP/NIS ● DNS / Hesiod ● WINS ● LDAP ● Maps: ● passwd, group ● automount, services, protocols ● Map from a key to a value ● Give reliable answers [email protected] Authentication Service ● Get password hash from NIS, check locally ● Authentication protocol ● RADIUS ● TACACS+ ● Kerberos ● POP ● LDAP ● Avoid exposing password in cleartext ● Protect authentication data from rogue clients [email protected] LDAP structure: the tree dc=org dc=example ou=People ou=Group ou=rpc ou=mounts [email protected] LDAP structure: person entry dn: uid=andrew,ou=People,dc=example,dc=org uid: andrew cn: Andrew Findlay objectClass: top objectClass: account objectClass: posixAccount objectClass: shadowAccount loginShell: /bin/bash uidNumber: 500 gidNumber: 500 homeDirectory: /home/andrew gecos: Andrew Findlay userPassword: {crypt}$1$HkYw.fgh$... [email protected] Test environment ● Red Hat 7.1 on laptop ● OpenLDAP 2.0.18 ● PADL migration tools ● Client OS mostly in VMware virtual machines ● Red Hat 7.2 ● FreeBSD 4.4 ● SuSE 7.0 ● Mandrake 8.1 ● Solaris 8 ● Aim to centralise all user management data [email protected] Name Service Switch ● NSS in Linux and
    [Show full text]
  • Installing and Administering NFS Services
    Installing and Administering NFS Services HP 9000 Networking Manufacturing Part Number: B1031-90048 E0601 U.S.A. © Copyright 2001 Hewlett-Packard Company. Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty. A copy of the specific warranty terms applicable to your Hewlett- Packard product and replacement parts can be obtained from your local Sales and Service Office. Restricted Rights Legend. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 for other agencies. Hewlett-Packard Co. 19420 Homestead Road Cupertino, CA 95014 USA Use of this manual and CD(s) supplied for this pack is restricted to this product only. Additional copies of the programs may be made for security and back-up purposes only. Resale of the programs in their present form or with alterations, is expressly prohibited. Copyright Notices ©copyright 1983-2000 Hewlett-Packard Company, all rights reserved. Reproduction, adaptation, or translation of this document without prior written permission is prohibited, except as allowed under the copyright laws.
    [Show full text]
  • System Operations IT-ST-FDO
    System Operations IT-ST-FDO Index: - Bash pag. 2 - Common Operations pag. 3 - EOS pag. 13 - Filesystem Operations pag. 16 - CASTOR pag. 23 - Interventions pag. 28 - How to implement the SSO on EOSCOCKPIT Machine pag. 34 - XrdFed pag. 38 - Rundeck pag. 40 - Gitlab pag. 41 - SAMBA pag. 45 Please remind that commands and procedures could be no longer updated. Please verify them before any use. Bash: Shell command line --> “command” “options” “arguments”. - scp [source] [dest] --> scp log.cron root@lxbst2277:/etc/file.conf --> Secure copy to other machines. - cp [options]... Source Dest --> Copy Source to Dest or Directory. - lp [options]...[file...] --> Send files to a printer. - cd [Options] [Directory] --> Change Directory - change the current working directory to a specific folder. - pwd [-LP] --> Print Working Directory. - ls [Options]... [File]... --> List information about files. - ll = ls -l [file] --> List directory contents using long list format. - cat [Options] [File]... --> Concatenate and print (display) the content of files. - grep [options] PATTERN [FILE...] --> Search file(s) for specific text. - sort [options] [file...] --> Sort text files. Sort, merge, or compare all lines from files given. - cut [OPTION]... [FILE]... --> Divide a file into several parts (columns). - tr [options]... SET1 [SET2] --> Translate, squeeze, and/or delete characters. - mv [options]... Source... Directory --> Move or rename files or directories. - source filename [arguments] --> Read and execute commands from the filename argument in the current shell context. - mkdir [Options] folder... --> Create new folder(s), if they do not already exist. - xrdcp [options] source destination --> Copies one or more files from one location to another. - df [option]... [file]... --> Disk Free - display free disk space.
    [Show full text]
  • Winbind Guide
    Unified Logons between Windows NT and UNIX using Winbind Tim Potter ([email protected]) Andrew Tridgell ([email protected]) October 16, 2000 Abstract Integration of UNIX and Microsoft Windows NT through a unified lo- gon has been considered a \holy grail" in heterogeneous computing envi- ronments for a long time. We present winbind, a component of the Samba suite of programs as a solution to the unified logon problem. Winbind uses a UNIX implementation of Microsoft RPC calls, Pluggable Authentication Modules, and the Name Service Switch to allow Windows NT domain users to appear and operate as UNIX users on a UNIX machine. This paper de- scribes the winbind system, explaining the functionality it provides, how it is configured and how it works internally. 1 Introduction It is well known that UNIX and Microsoft Windows NT have different models for representing user and group information and use different technologies for implementing them. This fact has made it difficult to integrate the two systems in a satisfactory manner. One common solution in use today has been to create identically named user accounts on both the UNIX and Windows systems and use the Samba suite of programs to provide file and print services between the two. This solution is far from perfect however, as adding and deleting users on both sets of machines becomes a chore and two sets of passwords are required both of which which can lead to synchronization problems between the UNIX and Windows systems and confusion for users. We divide the unified logon problem for UNIX machines into three smaller problems: Obtaining Windows NT user and group information • Authenticating Windows NT users • Password changing for Windows NT users • 1 Ideally, a prospective solution to the unified logon problem would satisfy all the above components without duplication of information on the UNIX machines and without creating additional tasks for the system administrator when maintaining users and groups on either system.
    [Show full text]