DOCSLIB.ORG

Solaris TCP/IP Network Security Features Previous Screen Carol Siegel Payoff Reviewing System Security for UNIX Is a Difficult Task

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Solaris TCP/IP Network Security Features Previous Screen Carol Siegel Payoff Reviewing System Security for UNIX Is a Difficult Task 84-10-11 Solaris TCP/IP Network Security Features Previous screen Carol Siegel Payoff Reviewing system security for UNIX is a difficult task. However, the new technologies have made this task simpler because of the development of new client/server technology and open systems. SUN Microsystems' Solaris (based on SUN-OS Release 5 and AT&T Corporation's AT&T System V Release IV) has become a dominant player in the UNIX arena. This article, addresses some of the Solaris Transmission Control/Internet Protocol (TCP/IP) networking security features. Introduction As the location of data and programs move from servers to clients(i.e., desktop workstations and microcomputers), security exposures increase exponentially. One of the biggest areas of concern is network security. Wide Area Network as well as local area network interconnectivity in conjunction with client/server technology translates into significant network traffic and services. This increased traffic along the wire places significant importance on creating an industrywide standard for secure transmissions. Cryptology and message authentication methodologies are tools that will help resolve this issue. In addition, TCP/IP network services that are offered in conjunction with UNIX operating systems need to be closely controlled. Some of these services send unencrypted ID and password information across the wire, others list them in plain text in files, while others permit user log-in by requiring password authentication. Clearly, the use of these services should be carefully considered. Networking Security Features Remote access through the TCP/IP protocol suite is regulated by the following local files: · /etc/hosts. This file correlates host names with IP addresses. · /etc/services. This file correlates service name with port number and protocol. · /etc/hosts.equiv. This file lists serverwide trusted hosts and users. If one host trusts another host, any user that has the same ID on both hosts can log in from the trusted host to the other computer without typing a password. A + sign means that all users are trusted. · $HOME/.rhosts. This file contains user-specified trusted hosts and users that may log in asuser without a password. These files are located in user's home directories and can be created by end-users. A + sign means that all users are trusted. As shown in Exhibit 1, /etc/hosts.equivfile is overridden by the use of the.rhosts. · /etc/inetd.conf. This file, as shown in Exhibit 2, matches service names with server programs to be executed. Telnet provides remote virtual terminal service. Telnet permits any user on any host on the network to access the local host if a valid user name and password is supplied. It permits users to act as if they are logged in locally with full-access privileges. $HOME/.rhosts and /etc/hosts.equiv Previous screen #Examples # denies access to all users on host #-@group denies access to all users on hosts in group #-@group1+@group2 allows access to users in group2 on hosts in group1 #host user allows acces to user on host #+user allows access to user on any host # host-user denies access to user on host #-host denies access to all users on host #-@group denies access to all users in hosts in group The /etc/inetd.conf Command #ident "@(#)inetd.conf 1.13 92/12/07 SMI/*SVr4.0 1.5/ #Configuration file for inedt (8). See inedt.conf(5). # #To reconfigure the runnint inetd process, edit this file, then #send the inetd proces a SIGNUP. # #Syntax for socket-based Internet services: #< service_name >< socket_type >< proto >< flags >< user > < server_pathname >< args > #Ftp and telnet are standard internet services # ftp stream tcp nowait root /usr/sbin/in.ftpd in.ftpd telnet stream tcp nowait root /usr/sbin/in.telnetd in.telnetd # #Tnamed serves the obsolete IEN-116 name server protocol. # # name dgram udp wait root /usr/sbin/in.tnamed in.tnamed # #Shell,log-in,exec,comsat,and talk are BSD protocols. # shell stream tcp nowait root /usr/sbin/in.rshd in.rshd log-in stream tcp nowait root /rsr/sbin/in.rlogind in.rlogind exec stream tcp nowait root /usr/sbin/in.execd in.rexecd comsat dgram udp wait root /usr/sbin/in.comsat in.comsat talk dgram udp wait root /usr/sbin/in.talkd in.talkd Certain commands called the r-commands permit remote access in some cases that do not require password authentication. These commands are: · rlogin permits a user to log in to a remote machine. · rsh permits a user to spawn a shell on a remote machine. · rcp permits remote copying. Exhibit 3 presents an example of the authentication process for rlogin, rsh, and rcp. Some of the access paths for user A do not require passwords: · Path 1. When executing rlogin, rsh, or rcp, if the user is not root, and if user A from Previous screen host * is listed in the local password file, and host * is listed in the localhosts.equiv file, access is allowed without a password. · Path 2. Similarly, if user A is listed in the local password file, but not in the local host.equiv file, but the user A and host * combination is listed in user A's local.rhosts file, no password is required. In search order, first the hosts.equiv file is searched and then the .rhosts file. Therefore, if end-users have created their own .rhosts files, they have control over certain remote access. Remote Network Authentication Remote Execution Security considerations for remote execution are: · Network services that are determined to be unsafe(depending on the security policy of the environment) should be disabled by removing or commenting out their entry in the/etc/inetd.conf or the/etc/services file. · $HOME/.rhosts files in general are considered to be unsafe, and should not be permitted. · A + sign in the/etc/host.equiv file or any$HOME/.rhosts file means all known hosts(those listed in /etc/hosts) are trusted. No+ signs should be found in these files. · $HOME/.rhosts files override entries in the /etc/host.equiv file and can be used as a backdoor. As they are controlled by end users, they are difficult to prevent. Daily system sweeps of end user's home directories are suggested. File Transfer Services The File Transfer Protocol (ftp) files to and from a remote network. It allows a remote user to log into a remote system with valid account and password information on the local system. After logging in, the user can get files, change directories, list directories, make directories, and remove files or directories. A file called /$HOME/.netrc can be created by any end user. The .netrc file contains valid host, user ID, and password information in clear text. This file permits those users specified to use ftp commands without manual password verification. The trivial ftp, used primarily for booting diskless workstations, permits the copying of world-readable files without logging in, thus not requiring adequate identification and authentication. Security Considerations for File Transfer The following is a list of security considerations for file transfer: · The /etc/ftpusers contains a list of users that cannot access the system using ftp.If this file is missing, any user may use ftp to access the system. · Because the $HOME/.netrcfile contains unencrypted password information, it is a serious Previous screen security exposure and should not be permitted. The system should be swept daily for the existence of these files. · If the need exists for a$HOME/.netrc file, it should be read and write for the owner of the file only. In addition, the remote target system should only allow ftp and no interactive session (e.g., telnet orrlogin). · The ftpusers file should contain all /etc/passwd users, except those authorized to use ftp; this file should be monitored regularly. · The ftp service should not be available unless expressly needed and should be commented out in theinetd.conf or /etc/servicesfile. X-Windowing Services X is a popular network-based window system that allows many programs to share a single graphical display. X-based programs display their output in windows, which can be either on the same computer on which the program is running or on any other computer on the network. Exhibit 4 shows the * server that controls a graphical screen allowing * clients to display windows on it. X-Windowing Access to xhost is controlled through the use of access control lists (ACLs) that display the remote hosts that have permission to display their windows on local workstations. The use of these Audit Command Language must be monitored. By issuing the command xhost+, an ACLs is created that permits any server to display on that client. If this command is not used, specific servers must be listed. A good X programmer can place a full screen window over the server's graphical device that is not detectable to the end-user. In this fashion, the programmer can potentially spoof production clients by displaying sign-on windows (or other data-gathering windows such as trade input). The xhost utility also has implications with respect to the physical and logical separation of product life-cycle environments. Development areas must be separated from User- Acceptance Test areas and from production areas. If access to a development or user- acceptance test (UAT) area is permitted from a production box by the use of thexhost utility, certain risks are present. For example, a trader who might be performing a test of a program or tool to analyze market data could display the resultant data on the production workstation screen. By doing this, the risk exists that any trader, for example, will mistake this data for true production data and base a decision on the erroneous data displayed.
Load more

Recommended publications
  • CIS IBM AIX 7.1 Benchmark V1.1.0 - 09-20-2013
    CIS IBM AIX 7.1 Benchmark v1.1.0 - 09-20-2013 http://benchmarks.cisecurity.org The CIS Security Benchmarks division provides consensus-oriented information security products, services, tools, metrics, suggestions, and recommendations (the “SB Products”) as a public service to Internet users worldwide. Downloading or using SB Products in any way signifies and confirms your acceptance of and your binding agreement to these CIS Security Benchmarks Terms of Use. CIS SECURITY BENCHMARKS TERMS OF USE BOTH CIS SECURITY BENCHMARKS DIVISION MEMBERS AND NON-MEMBERS MAY: Download, install, and use each of the SB Products on a single computer, and/or Print one or more copies of any SB Product that is in a .txt, .pdf, .doc, .mcw, or .rtf format, but only if each such copy is printed in its entirety and is kept intact, including without limitation the text of these CIS Security Benchmarks Terms of Use. UNDER THE FOLLOWING TERMS AND CONDITIONS: SB Products Provided As Is. CIS is providing the SB Products “as is” and “as available” without: (1) any representations, warranties, or covenants of any kind whatsoever (including the absence of any warranty regarding: (a) the effect or lack of effect of any SB Product on the operation or the security of any network, system, software, hardware, or any component of any of them, and (b) the accuracy, utility, reliability, timeliness, or completeness of any SB Product); or (2) the responsibility to make or notify you of any corrections, updates, upgrades, or fixes. Intellectual Property and Rights Reserved. You are not acquiring any title or ownership rights in or to any SB Product, and full title and all ownership rights to the SB Products remain the exclusive property of CIS.
    [Show full text]
  • Autoconf.Pdf
    Autoconf Creating Automatic Configuration Scripts for version 2.66, 2 July 2010 David MacKenzie Ben Elliston Akim Demaille This manual (2 July 2010) is for GNU Autoconf (version 2.66), a package for creating scripts to configure source code packages using templates and an M4 macro package. Copyright c 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with the Front-Cover texts being \A GNU Manual," and with the Back-Cover Texts as in (a) below. A copy of the license is included in the section entitled \GNU Free Documentation License." (a) The FSF's Back-Cover Text is: \You have the freedom to copy and modify this GNU manual. Buying copies from the FSF supports it in developing GNU and promoting software freedom." i Table of Contents 1 Introduction::::::::::::::::::::::::::::::::::::: 1 2 The GNU Build System:::::::::::::::::::::::: 3 2.1 Automake:::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2.2 Gnulib ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2.3 Libtool::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 2.4 Pointers:::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 3 Making configure Scripts :::::::::::::::::::::: 5 3.1 Writing `configure.ac' ::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Freebsd Command Reference
    FreeBSD command reference Command structure Each line you type at the Unix shell consists of a command optionally followed by some arguments , e.g. ls -l /etc/passwd | | | cmd arg1 arg2 Almost all commands are just programs in the filesystem, e.g. "ls" is actually /bin/ls. A few are built- in to the shell. All commands and filenames are case-sensitive. Unless told otherwise, the command will run in the "foreground" - that is, you won't be returned to the shell prompt until it has finished. You can press Ctrl + C to terminate it. Colour code command [args...] Command which shows information command [args...] Command which modifies your current session or system settings, but changes will be lost when you exit your shell or reboot command [args...] Command which permanently affects the state of your system Getting out of trouble ^C (Ctrl-C) Terminate the current command ^U (Ctrl-U) Clear to start of line reset Reset terminal settings. If in xterm, try Ctrl+Middle mouse button stty sane and select "Do Full Reset" exit Exit from the shell logout ESC :q! ENTER Quit from vi without saving Finding documentation man cmd Show manual page for command "cmd". If a page with the same man 5 cmd name exists in multiple sections, you can give the section number, man -a cmd or -a to show pages from all sections. man -k str Search for string"str" in the manual index man hier Description of directory structure cd /usr/share/doc; ls Browse system documentation and examples. Note especially cd /usr/share/examples; ls /usr/share/doc/en/books/handbook/index.html cd /usr/local/share/doc; ls Browse package documentation and examples cd /usr/local/share/examples On the web: www.freebsd.org Includes handbook, searchable mailing list archives System status Alt-F1 ..
    [Show full text]
  • Bootstrap Protocol, BOOTP, Is the Recommended Way to Establish Communications from the Host to the Printer in an Internet Protocol Environment
    BOOTP Bootstrap protocol, BOOTP, is the recommended way to establish communications from the host to the printer in an internet protocol environment. BOOTP obtains booting data from the bootptab file. With the proper information stored in the bootptab file, the printer can find its own name and IP address and boot from the network without any intervention, even for a first time boot. 1. Verify that the bootpd and bootptab files are in the correct directories: UNIX: /etc or /usr/etc directory OS/2: \TCPIP\ETC (for bootptab) and \TCPIP\BIN (for bootpd) LAN Server: MPTN\ETC (for bootptab) and \MPTN\BIN (for bootpd) Type: ls bootp* 2. Edit the hosts file to add the printer internet addresses and names: 128.07.60.30 P340-mktg 128.07.60.31 P340-sales For OS/2, use the TCP/IP Configuration Notebook under the Services tab to add the printer internet addresses and names. 3. Some UNIX hosts may require an explicit update to the arp table to add the new entries. This command is host-specific; check your host documentation for details. arp -s ether P340-mktg 08:00:11:01:00:45 arp -s ether P340-sales 08:00:11:01:00:46 The ether switch indicates that you are providing an Ethernet address. 4. Set up the bootptab file. 5. Start or restart the inetd or bootpd daemon. For OS/2 Warp, LAN Server 4.0, and UNIX, use the bootpd daemon. Here is a sample bootptab file; check your host system documentation to see which fields your implementation of BOOTP supports.
    [Show full text]
  • 1.113.1 Configure and Manage Inetd, Xinetd, and Related Services Weight
    1.113.1 Configure and manage inetd, xinetd, and related services Weight 4 1.113.1 Angus Lees Context Configure and manage inetd, xinetd, and Objective inetd, xinetd related services tcpwrappers Weight 4 xinetd License Of This Linux Professional Institute Certification — 102 Document Angus Lees [email protected] Geoffrey Robertson [email protected] Nick Urbanik [email protected] This document Licensed under GPL—see section 6 2005 July 1.113.1 Configure and manage Outline inetd, xinetd, and related services Weight 4 Angus Lees Context Objective inetd, xinetd tcpwrappers xinetd inetd.conf License Of This Context Document tcpwrappers Objective xinetd inetd, xinetd License Of This Document 1.113.1 Configure and manage Topic 113 Networking Services [24] inetd, xinetd, and Where we are up to related services Weight 4 Angus Lees Context Objective 1.113.1 Configure and manage inetd, xinetd, and inetd, xinetd related services [4] tcpwrappers xinetd 1.113.2 Operate and perform basic configuration of License Of This sendmail [4] Document 1.113.3 Operate and perform basic configuration of Apache [4] 1.113.4 Properly manage the NFS, smb, and nmb daemons [4] 1.113.5 Setup and configure basic DNS services [4] 1.113.7 Set up secure shell (OpenSSH) [4] 1.113.1 Configure and manage Description of Objective inetd, xinetd, and 1.113.1 Configure and manage inetd, xinetd, and related services related services Weight 4 Angus Lees Context Objective inetd, xinetd Candidates should be able to configure tcpwrappers which services are available through xinetd License Of This inetd, use tcpwrappers to allow or deny Document services on a host-by-host basis, manually start, stop, and restart internet services, configure basic network services including telnet and ftp.
    [Show full text]
  • Network Programming TDC 561 Lecture # 5: Multiservice and Multiprotocols Servers
    Network Programming TDC 561 Lecture # 5: Multiservice and Multiprotocols Servers Dr. Ehab S. Al-Shaer School of Computer Science & Telecommunication DePaul University Chicago, IL 1 select() Review int select( int maxfd, fd_set *readset, fd_set *writeset, fd_set *excepset, const struct timeval *timeout); maxfd : highest number assigned to a descriptor. readset: set of descriptors we want to read from. writeset: set of descriptors we want to write to. excepset: descriptors to watch for exceptions. timeout: maximum time select should wait 2 Dr. Ehab Al-Shaer/Network Programming select() Review ❂ select() components (e.g., p. 143) • passive (original) mailbox, afds: FD_SET and FD_CLR • active (operational) mailbox, rfds:FD_ISSET ❂ When to use it • I/O Multiplexing • Non-blocking • High-precision timer 3 Dr. Ehab Al-Shaer/Network Programming 1 Multiprotocol Servers ❂ Provides a single service using TCP or UDP ❂ Motivation • less overhead • No need for replication control • maintainability • extendibility for more protocols 4 Dr. Ehab Al-Shaer/Network Programming Multiprotocol Servers ❂ Algorithm 1. Create a passive UDP socket (usock) and passive TCP socket (tsock), Bind to a port 2. Use select() to monitor usock and tsock 3. 3. If tsock is READY 3.1. Accept connections 3.2. Read and Write 3.3. Close if finish 4. If usock is READY 4.1. Receive and Send 5. Go to 2 ❂ Example (daytimed.c, P. 150) • Is it truly concurrent? 5 •No read in tsock,Dr. Ehab and Al-Shaer/Network no close Programmingin usock, WHY? Multiservice Servers ❂ A single server that provides multiple services ❂ Motivation • less execution overhead • less code ❂ Algorithm for connectionless servers 1.
    [Show full text]
  • UNIX System Servicesplanning
    z/OS Version 2 Release 3 UNIX System Services Planning IBM GA32-0884-30 Note Before using this information and the product it supports, read the information in “Notices” on page 409. This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2019-03-26 © Copyright International Business Machines Corporation 1996, 2018. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents List of Figures...................................................................................................... xv List of Tables......................................................................................................xvii About this document...........................................................................................xix Using this document..................................................................................................................................xix z/OS information........................................................................................................................................xix Discussion list.......................................................................................................................................xix How to send your comments to IBM.....................................................................xxi If you have a technical problem................................................................................................................xxi
    [Show full text]
  • IBM I: TCP/IP Troubleshooting • a Default Route (*DFTROUTE) Allows Packets to Travel to Hosts That Are Not Directly Connected to Your Network
    IBM i Version 7.2 Networking TCP/IP troubleshooting IBM Note Before using this information and the product it supports, read the information in “Notices” on page 71. This document may contain references to Licensed Internal Code. Licensed Internal Code is Machine Code and is licensed to you under the terms of the IBM License Agreement for Machine Code. © Copyright International Business Machines Corporation 1997, 2013. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents TCP/IP troubleshooting......................................................................................... 1 PDF file for TCP/IP troubleshooting............................................................................................................ 1 Troubleshooting tools and techniques........................................................................................................1 Tools to verify your network structure...................................................................................................1 Tools for tracing data and jobs.............................................................................................................15 Troubleshooting tips............................................................................................................................ 31 Advanced troubleshooting tools..........................................................................................................66 Troubleshooting problems related
    [Show full text]
  • Administration Guide Administration Guide SUSE Linux Enterprise Server 15 SP1
    SUSE Linux Enterprise Server 15 SP1 Administration Guide Administration Guide SUSE Linux Enterprise Server 15 SP1 Covers system administration tasks like maintaining, monitoring and customizing an initially installed system. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xxii 1 Available Documentation xxiii 2 Giving Feedback xxv 3 Documentation Conventions xxv 4 Product Life Cycle and Support xxvii Support Statement for SUSE Linux Enterprise Server xxviii • Technology Previews xxix I COMMON TASKS 1 1 Bash and Bash
    [Show full text]
  • Configuration Management with Newfig William Lefebvre and David Snyder – CNN Internet Technologies
    Auto-configuration by File Construction: Configuration Management with Newfig William LeFebvre and David Snyder – CNN Internet Technologies ABSTRACT A tool is described that provides for the automatic configuration of systems from a single description. The tool, newfig, uses two simple concepts to provide its functionality: boolean logic for making decisions and file construction for generating the files. Newfig relies heavily on external scripts for anything beyond the construction of files. This simple yet powerful design provides a mechanism that can easily build on other tools rather than a single monolithic stand- alone program. This provides for a great deal of flexibility while maintaining simplicity. The language is a combination of boolean logic and output statements, and also provides for macros and other essential elements. All output is written to channels: an abstraction which provides for extensive configurability. Examples are provided that show the tool’s power and flexibility. A description is also provided of the efforts undergone at CNN to integrate this tool in to a sizable infrastructure. The paper concludes with a discussion of future improvements. Introduction When we sought out a tool for automated sys- tems configuration, we were looking for certain prop- As the number of systems in an infrastructure grows, the administration problem grows with it. erties that we believe would be beneficial in our envi- Unless the engineering staff grows accordingly, at some ronment. We wanted the system to be idempotent, point the management of the systems will need to be congruent, deterministic, transportable, extensible, and automated. This realization is nothing new, and several fail-safe.
    [Show full text]
  • Solaris Benchmark V1.3.0 (For Solaris 2.5.1 and Later Releases)
    Solaris Benchmark v1.3.0 (for Solaris 2.5.1 and later releases) Copyright 2001-2004, The Center for Internet Security http://www.CISecurity.org/ ii Solaris Benchmark v1.3.0 June 17, 2004 Copyright 2001-2004, The Center for Internet Security (CIS) TERMS OF USE AGREEMENT Background. The Center for Internet Security ("CIS") provides benchmarks, scoring tools, software, data, information, suggestions, ideas, and other services and materials from the CIS website or elsewhere (“Products”) as a public service to Internet users worldwide. Recommendations contained in the Products (“Recommendations”) result from a consensus-building process that involves many security experts and are generally generic in nature. The Recommendations are intended to provide helpful information to organizations attempting to evaluate or improve the security of their networks, systems, and devices. Proper use of the Recommendations requires careful analysis and adaptation to specific user requirements. The Recommendations are not in any way intended to be a “quick fix” for anyone’s information security needs. No Representations, Warranties, or Covenants. CIS makes no representations, warranties, or covenants whatsoever as to (i) the positive or negative effect of the Products or the Recommendations on the operation or the security of any particular network, computer system, network device, software, hardware, or any component of any of the foregoing or (ii) the accuracy, reliability, timeliness, or completeness of the Products or the Recommendations. CIS is providing the Products and the Recommendations “as is” and “as available” without representations, warranties, or covenants of any kind. User Agreements. By using the Products and/or the Recommendations, I and/or my organization (“We”) agree and acknowledge that: 1.
    [Show full text]
  • Cx Odbc Driver Installation Guide
    CX ODBC Driver Installation Guide Copyright 2001 Jenazabar, Inc. You may print any part or the whole of this documentation to support installations of Jenzabar software. Where the documentation is available in an electronic format such as PDF or online help, you may store copies with your Jenzabar software. You may also modify the documentation to reflect your institution's usage and standards. Permission to print, store, or modify copies in no way affects ownership of the documentation; however, Jenzabar, Inc. assumes no responsibility for any changes you make. Filename: inodbc Distribution date: 08/30/2001 Contact us at www.jenzabar.com Jenzabar CX, and QuickMate are trademarks of Jenzabar, Inc. INFORMIX, PERFORM, and ACE are registered trademarks of the IBM Corporation Impromptu, PowerPlay, Scenario, and Cognos are registered trademarks of the Cognos Corporation UNIX is a registered trademark in the USA and other countries, licensed exclusively through X/Open Company Limited Windows is a registered trademark of the Microsoft Corporation All other brand and product names are trademarks of their respective companies JENZABAR, INC. CX ODBC DRIVER INSTALLATION GUIDE TABLE OF CONTENTS INTRODUCTION........................................................................................................................................... 1 Overview................................................................................................................................................. 1 Operation of the ODBC Link..................................................................................................................
    [Show full text]