DOCSLIB.ORG

Principles of System Administration

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Principles of System Administration Principles of System Administration Jan Schaumann [email protected] April 14, 2021 Contents Preface to the preface i Preface ii I Introduction and General Concepts 1 1 Introduction 2 1.1 What exactly does a System Administrator do? . .3 1.2 The Profession of System Administration . .6 1.3 System Administration Education . .9 1.3.1 Challenges in System Administration Education . 11 1.4 The Three Pillars of Exceptional System Design . 13 1.4.1 Scalability . 14 1.4.2 Security . 16 1.4.3 Simplicity . 19 1.5 The Future of System Administration . 20 Problems and Exercises 23 Problems . 23 Exercises . 24 2 Unix 28 2.1 Unix History . 28 2.1.1 The Operating System . 28 2.1.2 Networking . 35 2.1.3 Open Source . 37 2.2 Basic Unix Concepts and Features . 38 1 CONTENTS 2 2.2.1 The shell . 39 2.2.2 Manual pages and documentation . 42 2.2.3 A portable, multitasking, multiuser system . 44 2.2.4 The Unix Philosophy . 46 Problems and Exercises 50 Exercises . 51 3 Documentation Techniques 55 3.1 System Documentation Writing 101 . 56 3.1.1 Know Your Audience . 56 3.2 Online Documentation . 58 3.3 Different Document Types . 59 3.3.1 Processes and Procedures . 60 3.3.2 Policies . 61 3.3.3 Online Help and Reference . 62 3.3.4 Infrastructure Architecture and Design . 63 3.3.5 Program Specification and Software Documentation . 64 3.4 Collaboration . 65 3.5 Formats . 66 Problems and Exercises 68 II Fundamental Technologies and Concepts 70 4 Of File Systems and Storage Models 74 4.1 Introduction . 74 4.2 Storage Models . 76 4.2.1 Direct Attached Storage . 76 4.2.2 Network Attached Storage . 78 4.2.3 Storage Area Networks . 80 4.2.4 Cloud Storage . 83 4.2.5 Storage Model Considerations . 86 4.3 Disk Devices and Interfaces . 87 4.3.1 Physical Disk Structure . 90 4.4 Dividing and Combining Disks . 92 4.4.1 Partitions . 93 CONTENTS 3 4.4.2 Logical Volumes . 97 4.4.3 RAID . 99 4.5 File Systems . 106 4.5.1 File System Types . 106 4.6 File System Layout . 110 4.7 The Unix File System . 112 4.8 Conclusions . 118 Problems and Exercises 122 Problems . 122 5 Software Installation and Package Management 126 5.1 Introduction . 126 5.2 Types of Software . 128 5.2.1 Up and down the software stack . 128 5.2.2 Operating System vs. System Software vs. Third Party Software . 135 5.3 File System Layout . 137 5.4 OS Installation . 141 5.4.1 Identifying server requirements . 142 5.4.2 OS Installation Overview . 143 5.4.3 OS Installation Details . 147 5.5 Package Management Systems . 151 5.5.1 \Manual" Software Installation . 151 5.5.2 Software Installation by Package Manager . 153 5.5.3 Inherent Security Risks . 158 5.6 Managing Software Updates and Patches . 160 5.7 Conclusions . 163 Problems and Exercises 166 Problems . 166 6 Of Users and Groups 170 6.1 Introduction . 170 6.2 Types of Users . 171 6.3 Groups of Users . 175 6.4 User Authentication . 177 6.4.1 Authentication Examples . 179 CONTENTS 4 6.4.2 The Problem with Passwords . 181 6.4.3 Sharing root ....................... 183 6.5 Summary . 184 Problems and Exercises 188 Problems . 188 7 Configuration Management 191 7.1 Introduction . 191 7.2 Services, not Single Points of Failure . 194 7.3 Defining Services and Requirements . 195 7.3.1 Example Service: Syslog . 196 7.3.2 Example Requirements: LDAP Client Configuration . 197 7.3.3 CM Requirements . 199 7.4 Of States and Sets . 204 7.4.1 States . 204 7.4.2 Sets . 207 7.5 Fighting entropy . 210 7.5.1 Deployment roles . 210 7.5.2 Idempotence and Convergence . 214 7.5.3 Quis custodiet ipsos custodes? . 217 7.6 Even more formal process definitions . 217 7.7 Summary . 218 Problems and Exercises 222 Problems . 222 8 Automation 226 8.1 Introduction . 226 8.2 Of Laziness And Other Virtues . 227 8.3 Benefits of Automation . 229 8.3.1 Repeatability . 229 8.3.2 Reliability . 230 8.3.3 Flexibility . 232 8.4 Who benefits from automation? . 233 8.4.1 Ourselves . 234 8.4.2 Our Peers . 234 8.4.3 All Users . 235 CONTENTS 5 8.5 Levels of Automation . 236 8.6 Automation Pitfalls . 238 8.6.1 Increased Complexity and Impact . 238 8.6.2 Loss of Audit Trail . 240 8.6.3 Loss of Accountability . 240 8.6.4 Safeguards . 241 8.7 Summary . 243 Problems and Exercises 246 Problems . 246 9 Building Scalable Tools 249 9.1 Introduction . 249 9.2 How Software evolves . 251 9.2.1 Scripts . 252 9.2.2 Programs . 253 9.2.3 Software Products . 254 9.3 Principles of Developing Robust System Tools . 256 9.3.1 Unix Philosophy and User Interface . 257 9.3.2 Principle of Least Astonishment . 263 9.3.3 Explicit and predictable failure . 264 9.3.4 There's no such thing as a temporary solution. 265 9.3.5 Readability counts . 266 9.3.6 Of Buses and Windows . 268 9.3.7 Code Reviews . 270 9.4 Additional Guidelines . 270 9.5 Summary . 272 Problems and Exercises 274 Problems . 274 10 Networking 278 11 Security 279 11.1 Authentication and Authorization . 279 CONTENTS 6 III Managing Complex Services 280 12 Managing System Services 282 13 Backup, Failover, and Disaster Recovery 283 13.1 File System Backups and Snapshots . 283 14 Monitoring and Visibility 284 IV Meta Matter 285 15 Everything We Haven't Covered 287 15.1 Containers . 287 15.2 Service Orchestration . 287 16 Ethics and Legal Issues 288 17 Future Direction of System Administration 289 Glossary of Terms 290 A Image Attributions 291 Index 294 Listings 1 Sample command-line invocations . vi 2.1 Simple I/O redirection in the shell . 39 2.2 Simple job control in the shell . 42 2.3 2-clause BSD license . 49 4.1 fdisk(8) sample invocation and output on a Linux system . 94 4.2 disklabel(8) invocation and output on a NetBSD system . ..
Load more

Recommended publications
  • Administrator's Guide for SAP Simple Finance, On-Premise Edition 2 PUBLIC Content Document History
    Administrator's Guide PUBLIC Document Version: 1503 SP 7 – 17.07.17 Administrator's Guide for SAP Simple Finance, On- Premise Edition Content 1 SAP Simple Finance, On-Premise Edition............................................ 4 2 Getting Started................................................................5 3 System Landscape.............................................................11 3.1 Introduction...................................................................11 Technical System Landscape....................................................12 Central Finance..............................................................19 Deployment Options for SAP Cash Management powered by SAP HANA.....................21 4 Installation and Migration Process................................................ 22 4.1 Introduction..................................................................22 Installation and Upgrade of SAP Simple Finance, On-Premise Edition....................... 22 Technical Installation of SAP Simple Finance, On-Premise Edition..........................39 Technical Installation of SAP HANA Live 2.0, Virtual Data Model for SAP Simple Finance, On- Premise Edition.............................................................44 5 Operation Information......................................................... 46 5.1 Introduction..................................................................46 Support Packages and Patch Implementation........................................48 Data Aging.................................................................48
    [Show full text]
  • Experience and Lessons from Software Configuration Management for PMAS
    Transactions of the Korean Nuclear Society Spring Meeting Jeju, Korea, May 22, 2009 Experience and Lessons from Software Configuration Management for PMAS Joo Hyun Cho a∗, Seung Min Baek a, Hang Bae Kim a a KOPEC, I&C System Engineering Department,150 Deokjin-Dong, Yuseong-Gu, Daejon, 305-353 *Corresponding author: [email protected] 1. Introduction for performing ongoing backup of work in progress for the system periodically, and the engineers are Plant Monitoring and Annunciator System (PMAS) responsible to develop source code and prepare the for Shin-kori and Shin-wolsong nuclear power plants 1 related document. and 2 is the first localization of a large scale I&C The configuration control plan for the PCS is based system in nuclear power plant construction project. The on the principle of a single, controlled source archive. PMAS is composed of Plant Computer System (PCS), Each engineer is responsible for developing the single Plant Data Acquisition System (PDAS) and Plant source of archive and the system administrator Annunciator System (PAS). The function of the PCS is maintains the single controlled archive. Configuration to perform plant status monitoring and application control of externally developed software begins upon programs running. The PDAS performs I/O signal receipt of the software from the external supplier. acquisition, processing and data communication for the PCS, and the PAS performs the annunciation of plant 2.1.2. SCM Activities alarm through annunciator window. The PCS and the PDAS/PAS are developed by different organizations, Configuration identification is applied to all software, and they are integrated at the staging area.
    [Show full text]
  • REQUEST for INFORMATION for Enterprise Resource Planning (ERP) Software, and Implementation and Integration Services
    City of Rockville RFI 08-18 RFI for ERP Software and Services City of Rockville Rockville, Maryland REQUEST FOR INFORMATION For Enterprise Resource Planning (ERP) Software, and Implementation and Integration Services Responses Due by 2:00 P.M. Eastern Time, Friday, September 8, 2017 ISSUED BY: Jessie J. Woods, Senior Buyer Procurement Division City of Rockville, City Hall 111 Maryland Avenue Rockville, Maryland 20850 Phone: (240) 314‐8430 Fax: (240) 314‐8439 Any individual with a disability who would like to receive the information in this publication in another form may contact the ADA Coordinator at 240‐314‐8100, TDD 240‐314‐8137 MFD Outreach Program It is the intent of the City of Rockville to increase opportunities for minority, female and disabled (MFD) owned businesses to compete effectively at supplying goods, equipment, and services to the City, within the constraints of statutory purchasing requirements, departmental needs, availability, and sound economical considerations. Suggested changes and MFD enhancements to this solicitation’s requirements for possible consideration and/or inclusion in future solicitations are encouraged. Page i City of Rockville RFI 08-18 RFI for ERP Software and Services Table of Contents 1.0 INTRODUCTION ............................................................................................................................................. 3 1.1 Intent of RFI ................................................................................................................................... 3 1.2
    [Show full text]
  • System Administrator Description
    GASCOSAGE ELECTRIC COOPERATIVE SYSTEM ADMINISTRATOR GENERAL SUMMARY: The System Administrator is responsible for managing the day-to-day operation of Gascosage Electric Cooperative and GTech Fiber networks. This position provides internal technical support to users, performs technology installations and software installations, employee training, participates in technology solution selections, and ensures network reliability and security. ROLES & RESPONSIBILITIES: 1. Implement, monitor and maintain servers and network devices. 2. Responsible for ensuring the availability of servers and the network to support operational needs. 3. Troubleshoot system failures and execute procedures to restore operations. 4. Monitor server and network performance and anticipate needed changes to optimize performance. 5. Analyze hardware and software for acquisition. 6. Design and test configurations necessary for new applications, new technologies and enhanced performance. ESSENTIAL DUTIES: Provide the administration of the following systems: Windows and Linux servers, SAN storage, virtualization infrastructure, local area networks, fiber optic wide area network, telephone system, Microsoft Office 365 applications, NISC’s iVUE enterprise hardware and software, Aclara’s TWACS automated meter reading hardware and software, electronic devices including desktop computers, laptop computers, tablets, copiers, printers and cell phones. 1. Install and maintain current release level for all desktop/server operating systems, network storage and network equipment. 2. Manage internal and external telecommunication services, cellular service and equipment including setup and maintenance. System Administrator, Page 2 3. Consult with the Management and staff personnel to identify long-term computer and telecommunication needs. 4. Answer and track internal technical and application support calls and submit monthly status report updates to Management. 5. Troubleshoot equipment problems and place service calls with the appropriate maintenance vendors when necessary.
    [Show full text]
  • TIBCO Activematrix Businessworks™ Smartmapper EPS Business UI User’S Guide
    TIBCO ActiveMatrix BusinessWorks™ SmartMapper EPS Business UI User’s Guide Version 6.0.1 August 2021 Copyright © 1999-2021. TIBCO Software Inc. All Rights Reserved. | ii Contents Figures . iv Tables . vi Chapter 1 SmartMapper EPS Business UI Overview . .1 Product Overview. 2 Chapter 2 Starting SmartMapper EPS Business UI . .3 Prerequisites . 4 Setting Up the Configuration File . 4 Starting Server. 6 Logging in to SmartMapper EPS Business UI. 7 Forgot Your Password. 8 Logging out SmartMapper EPS Business UI . 8 Stopping Server . 10 Chapter 3 User Interface Overview. .11 Home Page . 12 Main Menu . 13 Product and User Information. 13 Quick Tips Panel. 14 Recent Activity Panel . 14 Favorites Panel . 15 Relationship and Entity Management Page. 16 Left Panel Overview . 16 Right Panel Overview . 19 Chapter 4 Managing Identity Relationships . .21 Identity Relationship Management Page Overview . 22 Left Panel of the Identity Relationship Management Page . 22 Right Panel of the Identity Relationship Management Page. 23 Creating an Identity Relationship Instance . 25 Editing an Identity Relationship Instance. 29 Setting Up Favorite Relationships . 30 TIBCO ActiveMatrix BusinessWorks™ SmartMapper Enterprise Server Business UI User’s Guide iii | Contents Chapter 5 Managing Association Relationships . 31 Association Relationship Management Page Overview . 32 Left Panel of the Association Relationship Management Page . 32 Right Panel of the Association Relationship Management Page . 33 Creating an Association Relationship Instance. 34 Editing an Association Relationship Instance . 36 Setting Up Favorite Relationships . 37 Chapter 6 Managing Participants . 39 Adding a Participant Instance . 40 Changing Display Field and Setting Up Anchor Participant . 43 Chapter 7 Managing Entities . 47 Entity Management Page Overview .
    [Show full text]
  • Systems Administrator
    SYSTEMS ADMINISTRATOR SUMMARY The System Administrator’s role is to manage in-house computer software systems, servers, storage devices and network connections to ensure high availability and security of the supported business applications. This individual also participates in the planning and implementation of policies and procedures to ensure system provisioning and maintenance that is consistent with company goals, industry best practices, and regulatory requirements. ESSENTIAL DUTIES AND RESPONSIBILITIES: The Authority’s Senior Systems Manager may designate various other activities. The following statements are intended to describe the general nature and level of work being performed. They are not intended to be construed, as an exhaustive list of all responsibilities, duties and skills required of personnel so classified. Nothing in this job description restricts management's right to assign or reassign duties and responsibilities to this job at any time for any reason, including reasonable accommodation. Operational Management Manage virtual and physical servers with Windows Server 2003 – 2012 R2 and RHEL operating systems Manage Active Directory, Microsoft Office 365, and server and workstation patching with SCCM Manage the physical and virtual environment (VMware) of 300 plus servers Have familiarity with MS SQL server, windows clustering, domain controller setup, and group policy Ensure the security of the server infrastructure by implementing industry best-practices regarding privacy, security, and regulatory compliance. Develop and maintain documentation about current environment setup, standard operating procedures, and best practices. Manage end user accounts, permissions, access rights, and storage allocations in accordance with best- practices Perform and test routine system backups and restores. Anticipate, mitigate, identify, troubleshoot, and correct hardware and software issues on servers, and workstations.
    [Show full text]
  • Oracle Partner Relationship Management
    Oracle Partners Online Concepts and Procedures Release 11i June 2001 Part No. A87571-03 Oracle Partners Online Concepts and Procedures, Release 11i Part No. A87571-03 Copyright © 2001, Oracle Corporation. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation. If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on behalf of the U.S. Government, the following notice is applicable: Restricted Rights Notice Programs delivered subject to the DOD FAR Supplement are “commercial computer software” and use, duplication, and disclosure of the Programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, Programs delivered subject to the Federal Acquisition Regulations are “restricted computer software” and use, duplication, and disclosure of the Programs shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software - Restricted Rights (June, 1987).
    [Show full text]
  • Operating RISC: UNIX Standards in the 1990S
    Operating RISC: UNIX Standards in the 1990s This case was written by Will Mitchell and Paul Kritikos at the University of Michigan. The case is based on public sources. Some figures are based on case-writers' estimates. We appreciate comments from David Girouard, Robert E. Thomas and Michael Wolff. The note "Product Standards and Competitive Advantage" (Mitchell 1992) supplements this case. The latest International Computerquest Corporation analysis of the market for UNIX- based computers landed on three desks on the same morning. Noel Sharp, founder, chief executive officer, chief engineer and chief bottle washer for the Superbly Quick Architecture Workstation Company (SQAWC) in Mountain View, California hoped to see strong growth predicted for the market for systems designed to help architects improve their designs. In New York, Bo Thomas, senior strategist for the UNIX systems division of A Big Computer Company (ABCC), hoped that general commercial markets for UNIX-based computer systems would show strong growth, but feared that the company's traditional mainframe and mini-computer sales would suffer as a result. Airborne in the middle of the Atlantic, Jean-Helmut Morini-Stokes, senior engineer for the UNIX division of European Electronic National Industry (EENI), immediately looked to see if European companies would finally have an impact on the American market for UNIX-based systems. After looking for analysis concerning their own companies, all three managers checked the outlook for the alliances competing to establish a UNIX operating system standard. Although their companies were alike only in being fictional, the three managers faced the same product standards issues. How could they hasten the adoption of a UNIX standard? The market simply would not grow until computer buyers and application software developers could count on operating system stability.
    [Show full text]
  • Position Description
    Position Description Job Title: Business Systems Administrator Classification: AS06 Position No: CI12 Branch: Corporate Services Project Management Reports to: Lead Project Manager / Permit Reform Manager Date: March 2018 Primary Objectives The Business System Administrator will manage the technical and functional operation, maintenance and support of NLC business systems. The position will support internal users of NLC business systems to resolve incidents and change requests. Current NLC projects include the Land Use Management and Royalties (LUMAR) Project and Permit Reform Project (PRP): • The LUMAR Project will deliver a contemporary and consolidated system across all aspects of land use management and royalty distribution. • The PRP will deliver a modern and intuitive system that streamlines stakeholder permit applications and enables visitor management on Aboriginal land and waters. Business System Administration is a key priority for both projects and this position will be engaged in the development phase to build expertise in the proposed business solutions. As part of business system commissioning, the position will transition into NLC’s ICT Section. The Aboriginal Land Rights (Northern Territory) Act 1976 (ALRA), Native Title Act 1993 (NTA) and the Northern Territory Aboriginal Land Act 2013 (ALA) provide the framework within which the projects are being delivered. Duties: Business Analysis 1. Develop an understanding of what the NLC does and how it does it and evaluate and determine improvements to existing business systems and processes. 2. Design features of the business solution and develop functional and technical specifications to meet the NLC’s requirements. 3. Manage requirements traceability, options analysis and the solution decision register. 4. Work with external service providers to ensure that the solution meets the NLC’s business requirements.
    [Show full text]
  • The Rise & Development of Illumos
    Fork Yeah! The Rise & Development of illumos Bryan Cantrill VP, Engineering [email protected] @bcantrill WTF is illumos? • An open source descendant of OpenSolaris • ...which itself was a branch of Solaris Nevada • ...which was the name of the release after Solaris 10 • ...and was open but is now closed • ...and is itself a descendant of Solaris 2.x • ...but it can all be called “SunOS 5.x” • ...but not “SunOS 4.x” — thatʼs different • Letʼs start at (or rather, near) the beginning... SunOS: A peopleʼs history • In the early 1990s, after a painful transition to Solaris, much of the SunOS 4.x engineering talent had left • Problems compounded by the adoption of an immature SCM, the Network Software Environment (NSE) • The engineers revolted: Larry McVoy developed a much simpler variant of NSE called NSElite (ancestor to git) • Using NSElite (and later, TeamWare), Roger Faulkner, Tim Marsland, Joe Kowalski and Jeff Bonwick led a sufficiently parallelized development effort to produce Solaris 2.3, “the first version that worked” • ...but with Solaris 2.4, management took over day-to- day operations of the release, and quality slipped again Solaris 2.5: Do or die • Solaris 2.5 absolutely had to get it right — Sun had new hardware, the UltraSPARC-I, that depended on it • To assure quality, the engineers “took over,” with Bonwick installed as the gatekeeper • Bonwick granted authority to “rip it out if itʼs broken" — an early BDFL model, and a template for later generations of engineering leadership • Solaris 2.5 shipped on schedule and at quality
    [Show full text]
  • Job Description
    JOB DESCRIPTION Title: Accela System Administrator Reports To: Technology Manager Division/Bureau: Executive / MetCom & Technical Services Bureau FLSA Classification: Exempt I. GENERAL STATEMENT OF DUTIES Incumbent is responsible for the administration, maintenance and customization of SMFR’s Accela software solution. Responsibilities include: oversee management of Accela functionality including user interfaces; install, configure and implement Accela application and upgrades; maintain application scripts; customize Accela product to meet the needs of the Life Safety Bureau; provide technical support and end-user training to participating Accela users and administrators within SMFR and contracted agencies; develop routine and special reports; establish and document processes. II. SUPERVISION RECEIVED Work is performed under general supervision and guidance from the Technology Manager and the Fire Marshal. III. SUPERVISION EXERCISED This position has no supervisory responsibilities. IV. ESSENTIAL DUTIES AND RESPONSIBILITIES Administers, maintains and evaluates business applications/requests, software maintenance and interfaces. Confers with stakeholders and management to understand system flow, data usage and work processes. Develops software solutions through needs analysis and study of business requirements; creates, tests and implements custom scripts and forms; configures screens and workflows to meet organizational specifications. Enhances current application through the development of new code; designs and implements new modules to increase efficiency and meet business needs. Prepares technical system and user documentation, including flowcharts, layouts, diagrams, code comments, clear code, policies and procedures. Produces ad-hoc queries and reports. Communicates with end-users to provide support; identifies and analyzes application performance issues; designs solutions to meet end-user needs. Develops and delivers user training and presentations on new systems, application changes and upgrades.
    [Show full text]
  • IBM System Storage Open Systems Tape Encryption Solutions
    Front cover IBM System Storage Open Systems Tape Encryption Solutions Understanding tape encryption and Tivoli Key Lifecycle Manager Version 2 Planning for and installing hardware and software Configuring and managing the tape encryption solution Alex Osuna Luciano Cecchetti Edgar Vinson ibm.com/redbooks International Technical Support Organization IBM System Storage Open Systems Tape Encryption Solutions December 2010 SG24-7907-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (December 2010) This edition applies to Tivoli Key Lifecycle Manager (TKLM) Version 2. © Copyright International Business Machines Corporation 2010. 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 . vii Trademarks . viii Preface . ix The team who wrote this book . .x Become a published author . xi Comments welcome. xi Stay connected to IBM Redbooks . xii Chapter 1. Introduction to tape encryption. 1 1.1 IBM System Storage tape drives. 2 1.2 How tape data encryption works . 4 1.3 What to encrypt . 6 1.4 Why use tape data encryption. 7 1.4.1 Why encrypt data in the drive . 7 1.4.2 Fundamental to encryption: Policy and key management . 7 1.4.3 Summary. 8 1.5 Concepts of tape data encryption . 8 1.5.1 Symmetric key encryption. 9 1.5.2 Asymmetric key encryption . 11 1.5.3 Hybrid encryption . 14 1.5.4 Digital certificates . 15 1.6 Simplifying key management with TKLM . 20 1.6.1 Encryption as a critical business process .
    [Show full text]