Mac OS X File System Maintenance with Radmind
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Mac OS X Enterprise Application Management Best Practices Macosxlabs.Org
Mac OS X Enterprise Application Management Best Practices macosxlabs.org Richard Glaser, University of Utah Philip Rinehart, Yale University June 21, 2004 Contents 1 Abstract 1 1.1 Preface . 1 1.2 Audience . 2 1.3 Factors in the enterprise . 3 1.4 Comments and Questions . 4 2 Serialization of applications 4 2.0.1 Network Detection . 5 2.0.2 Server metering . 5 2.1 Hardware serialization . 7 2.1.1 Hardware Locks . 7 2.1.2 Media verification . 9 2.1.3 Challenge/Response . 9 3 Security 10 3.1 Permissions and File Modes . 11 3.1.1 SUID . 11 3.1.2 World writable directories . 13 3.2 Unnecessary open ports . 14 3.3 Startup items and root daemons . 14 3.4 Tripwire . 14 4 Installation 16 4.1 Log Files . 17 4.2 Administrative or root rights . 17 4.3 Non-standard location . 17 4.4 Broken links . 18 4.5 Path limitations . 19 4.5.1 File name limitation . 19 4.5.2 Directory location limitations . 19 ii 5 Missing Support and Features 19 5.1 Legacy application support . 20 5.2 Human Resources software . 20 5.3 Web-based instructional software . 21 5.4 Geographic Information Systems Support . 21 5.5 Backup software . 21 5.6 Lack of any Mac OS X alternative . 21 6 Distribution issues 22 6.1 Network Home Directories . 24 6.2 Resource forks . 25 6.3 Non-standard serialization . 25 6.4 Scratch space management . 26 6.5 ByHost preferences . 26 6.6 Auto launched application preferences . 26 6.7 File Attributes . -
Securing Mac OS X 10.4 Tiger V1.0.Doc
The natural choice for information security solutions AA CCoorrssaaiirree WWhhiittee PPaappeerr:: SSeeccuurriinngg MMaacc OOSS XX Author Stephen de Vries Document Reference Securing Mac OS X 10.4 Tiger v1.0.doc Document Revision 1.0 Released Date 19 August 2005 © Copyright 2000 – 2005 Corsaire Limited All Rights Reserved A Corsaire White Paper: Securing Mac OS X Table of Contents TABLE OF CONTENTS............................................................................................................ 2 1. INTRODUCTION................................................................................................................ 3 2. USING THIS GUIDE .......................................................................................................... 3 2.1 The Common Criteria..................................................................................................... 3 3. SUMMARY OF SECURITY HARDENING......................................................................... 4 4. SECURITY HARDENING GUIDELINES ........................................................................... 4 4.1 General Security Settings ............................................................................................. 4 4.2 Patching & Maintenance................................................................................................ 7 4.3 Physical Access Controls ............................................................................................. 8 4.4 Keychain ...................................................................................................................... -
CIS Mac OS X Leopard (10.5.X) Benchmark
Mac OS X 10.5 Leopard Level 1 & 2 Benchmark Version 1.0 May 2008 Copyright ©2008, The Center for Internet Security http://www.cisecurity.org Editor: Allan Marcus [email protected] CIS Mac OS X Leopard (10.5.x) Benchmark Table of Contents Terms of Use Agreement ........................................................................................................................... 3 1) Introduction ........................................................................................................................................ 6 1.1) Document Layout ....................................................................................................................... 6 1.2) Intended Audience ..................................................................................................................... 6 1.3) Practical Application .................................................................................................................. 7 1.4) Security Levels Explained ......................................................................................................... 7 1.5) Precursor Technical Information ............................................................................................... 7 1.6) Basic Security Principles: .......................................................................................................... 8 2) Benchmark Elements ......................................................................................................................... 9 2.1) Installation -
LCFG for Mac OS X
University of Edinburgh Division of Informatics LCFG For Mac OS X 4th Year Project Report Computer Science Angus W Hardie May 28, 2003 Abstract: LCFG is a large scale wide area configuration system. This project investigates the feasibility of implementing this system on the Mac OS X platform. The project involved the development of a working prototype of an LCFG client for Mac OS X. The results are discussed. Acknowledgements • Paul Anderson • Carwyn Edwards Lots of of other People who helped in various ways Document Information This document was made entirely with a Macintosh and Latex. The latest version of this document should be available at • http://homepages.inf.ed.ac.uk/s9812803/project/ • http://www.malcolmhardie.com/angus/project/ Contents 1 Introduction and Synopsis 1 1.1 Introduction . 1 1.2 Motivation . 1 1.3 Mac OS X - Discussion and Description . 2 1.4 LCFG - Description and Discussion . 2 1.4.1 How does LCFG work? . 3 1.5 Overview of Configuration Tools . 4 1.5.1 Imaging or Scripting? . 4 1.5.2 Declarative or Procedural? . 5 1.5.3 Comparison . 5 1.6 Similar Systems and Existing Solutions . 5 1.7 Apple Mac OS X Server . 5 1.8 Rsync/RsyncX . 6 1.9 Radmind . 6 1.10 MacAdministrator . 7 1.11 Summary of Results . 7 2 Proposed solution 9 2.1 Objectives . 9 2.2 Early Research and Prototypes . 9 2.3 Architectural Overview . 10 2.3.1 Selection of Scope . 10 2.3.2 Reuse . 11 2.4 Integration Overview . 11 2.5 Design Decisions . -
A Study of Configuration Management Systems Solutions for Deployment and Configuration of Software in a Cloud Environment
TVE 14 013 maj Examensarbete 15 hp Juni 2014 A Study of Configuration Management Systems Solutions for Deployment and Configuration of Software in a Cloud Environment Kim Torberntsson Ylva Rydin Abstract A Study of Configuration Management Systems Kim Torberntsson & Ylva Rydin Teknisk- naturvetenskaplig fakultet UTH-enheten The amount of servers needed in the world is constantly increasing along with the end users Besöksadress: constantly increasing demand for large scale network Ångströmlaboratoriet Lägerhyddsvägen 1 solutions and IT- services. With virtualisation and cloud Hus 4, Plan 0 computing it has become much easier to create and deploy large numbers of virtual servers, but the servers Postadress: still need configuration. This is precisely what Box 536 751 21 Uppsala configuration management systems (CMS) can help with. Cloud providers often want to include built in Telefon: support for these systems to simplify for their 018 – 471 30 03 customers. The purpose of the study was to compare Telefax: the different CMS available and to recommend the 018 – 471 30 00 ones that deserve to be supported by a cloud provider. A general study, based on parameters defined in the Hemsida: report, was made on twenty different CMS. The five top http://www.teknat.uu.se/student solutions were Puppet, Chef, CFEngine, Salt and Ansible, where Salt and Ansible are more lightweight solutions and Puppet, Chef and CFEngine are more advanced. They were included in a comparison study based on opinions and reviews from the Internet. The recommendation for a hypothetical cloud provider is to include support for several CMS if possible. If not, it is recommended to support one of the lightweight ones, preferably Salt, and one of the more advanced, preferably Puppet. -
About the Integration of Mac OS X Devices Into a Centrally Managed UNIX Environment Anton Schultschik – ETH, Zurich, Switzerland
About the Integration of Mac OS X Devices into a Centrally Managed UNIX Environment Anton Schultschik – ETH, Zurich, Switzerland ABSTRACT The UNIX flavors in use today have so much in common that centralized management of UNIX systems has become almost standard. Since Mac OS X is based on BSD-UNIX it is a promising candidate for integration into a centrally managed UNIX environment. Starting from generic administration concepts, this paper develops an integrated management concept that handles fully automated installation and configuration of hosts. The concept includes a centralized application management system for console and graphical Mac OS X applications. The management concept is then implemented based exclusively on standard UNIX tools. The necessary extensions of these tools to make Mac OS X conform to UNIX standards are presented, including a proxy tool to forward AppleEvents which facilitate the interprocess communication for centrally managed graphical Mac OS X applications. Introduction implementation and deployment of such a system will be layed out built on some basic principles. The result will The increasing diversity of hardware and soft- be a management system for UNIX systems that can be ware makes system management more difficult. Shorter life-cycles of computer systems require more used to manage network-based as well as stand-alone sys- frequent upgrades or replacement of hardware and as a tems. consequence, the installed computers on a large site In system management three basic principles rarely are uniform in hardware but rather split into sev- keep appearing in tools and methods [1], and these eral uniform clusters. Automated management of such shall be used as orientation for our integrated manage- an environment is challenging as complexity grows ment system: with each new configuration of hardware and software.