DOCSLIB.ORG

CHAPTER 4 © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT Forsharing SALE OR DISTRIBUTION Files NOT for SALE OR DISTRIBUTION

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

© Jones & Bartlett Learning,© Jones LLC & Bartlett Learning LLC, an Ascend Learning© Jones Company. & NOT Bartlett FOR SALE Learning, OR DISTRIBUTION. LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC © Digital_Art/ShutterstockNOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION CHAPTER 4 © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FORSharing SALE OR DISTRIBUTION Files NOT FOR SALE OR DISTRIBUTION © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION ▸ About This Chapter In this chapter, we work with the mechanisms provided by operating systems like Unix and Windows to protect files and folders. We also take a technical look at the fifth phase© of Jones the security & Bartlettprocess: monitoring Learning, the system. LLC The chapter focuses on © Jones & Bartlett Learning, LLC these topics:NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION ■ Tailoring the security policy to grant special access to individuals or groups ■ Permission flags in Unix-like systems ■ Access control lists in Macintosh and Windows systems ■ © Jones &Monitoring Bartlett system Learning, events through LLC logging © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION ▸ 4.1 Controlled Sharing What happens if Bob needs to share files with one or two other users but not with the rest of the suite? © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTIONBob hired a clerk to do data entry for his newNOT client, FOR a big SALE surveying OR com- DISTRIBUTION pany. The new clerk, Tina, has her own login on Bob’s computer (“tina”). However, the isolation policy blocks Bob and Tina from sharing files, unless Bob logs in as administrator and bypasses the access restrictions. It is clear© Jones that we &can Bartlett create files Learning, and folders andLLC establish access rights for © Jones & Bartlett Learning, LLC them. We NOTcan share FOR files SALEwith some OR people DISTRIBUTION and hide them from others, simply by NOT FOR SALE OR DISTRIBUTION configuring the right permissions. In small cases we might get this correct through trial-and-error, but we might also leak data while implementing our solution. Instead, we begin with identifying our objectives, threats, risks, and requirements. We plan and implement our controls based on the requirements. © Jones &When Bartlett we write Learning, the requirements LLC and policy, we want to capture© Jones our general & Bartlett Learning, LLC NOT FORintent. SALE When we OR write DISTRIBUTION up implementation details, we get specific.NOT In this FOR case, SALEthe OR DISTRIBUTION © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION © Jones & Bartlett Learning,© Jones LLC & Bartlett Learning LLC, an Ascend Learning© Jones Company. & NOT Bartlett FOR SALE Learning, OR DISTRIBUTION. LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 136 Chapter 4 Sharing Files requirements talk about people and general types of information (Bob, Tina, and © Jonesshared & bookkeepingBartlett Learning, data). Implementation LLC controls talk about files,© Jones folders, users, & Bartlett Learning, LLC NOT FORand access SALE rights. OR Here DISTRIBUTION are the two requirements we add to our isolationNOT FOR policy: SALE OR DISTRIBUTION ■ Bob and Tina shall be able to read and modify the surveying company’s bookkeeping data. ■ No one shall have access to bookkeeping data, except Bob and Tina. © Jones & Bartlett Learning,Although globalLLC restrictions like “no one ©shall” Jones are sometimes & Bartlett hard toLearning, verify, LLC accurate policy statements may require them. NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION Tailored File Security Policies To share the project files, Bob needs to adjust his user isolation security policy. Practical problems like this often arise when using one-size-fits-all policies like © Jones & Bartlett Learning, LLC“isolate everyone” or “share© everything.” Jones & We Bartlett address Learning,such things with LLC tailored NOT FOR SALE OR DISTRIBUTIONaccess policies. Three examplesNOT of tailoredFOR SALEpolicies are:OR DISTRIBUTION 1. Privacy 2. Shared reading 3. Shared updating © Jones &We Bartlett can describe Learning, a tailored policy LLC in several ways. Here we ©take Jones a systematic & Bartlett Learning, LLC NOT FORapproach. SALE We implementOR DISTRIBUTION each tailored policy underneath a systemwideNOT FOR default SALE OR DISTRIBUTION policy of either isolation or sharing. The tailored policy specifies additional access rights. These new rights may add to or replace the default rights. For each new set of rights, the tailored policy needs to consider four things: © Jones & Bartlett 1.Learning, Which files LLC or other resources are involved© (e.g.,Jones files relating& Bartlett to “Surveyors” Learning, LLC NOT FOR SALE OR DISTRIBUTIONor perhaps “Tina’s personal files”)? NOT FOR SALE OR DISTRIBUTION 2. Which users are granted these new rights (e.g., users editing the books for “Surveyors”)? 3. Do we Deny by Default, or do we retain the default access rights for these files? © Jones & Bartlett Learning, LLC4. Which access rights do we© enforce:Jones full & access,Bartlett execute, Learning, read-only, orLLC no access? NOT FOR SALE OR DISTRIBUTIONTypically, the files in questionNOT willFOR reside SALE within OR a particular DISTRIBUTION directory and be used by a particular group of people. When we describe the policy, however, we must be careful to describe what we want, rather than how we’ll do it. © JonesBob’s & BartlettSharing Learning, Dilemma LLC © Jones & Bartlett Learning, LLC NOT FORBob needs SALE to implement OR DISTRIBUTION a tailored updating policy so that he canNOT share FOR files with SALE OR DISTRIBUTION Tina. But how should he do it? For each file, we can control access by the owner, administrators, and the rest of the users. If that’s all we have, there’s no way to grant access to two specific users while blocking access to the rest. © Jones & Bartlett Learning,Bob could LLCsolve this sharing dilemma if he© always Jones logs &in toBartlett a system adminisLearning,- LLC NOT FOR SALE ORtration DISTRIBUTION account. On some systems, these accountsNOT use FOR a specific SALE user identityOR DISTRIBUTION with a name like “system” or “root” that receives all system-related access rights. If Bob does this, the account will have full access to Tina’s files. If he wants to create files © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION © Jones & Bartlett Learning,© Jones LLC & Bartlett Learning LLC, an Ascend Learning© Jones Company. & NOT Bartlett FOR SALE Learning, OR DISTRIBUTION. LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 4.1 Controlled Sharing 137 to share with Tina, however, he must make Tina the owner of those files. Other- wise, he wouldn’t© Jones be able & toBartlett restrict access Learning, exclusively LLC to Tina and himself. © Jones & Bartlett Learning, LLC This NOTsolution FOR poses SALE a problem: OR Least DISTRIBUTION Privilege. It may seem convenient to NOT FOR SALE OR DISTRIBUTION log into a system routinely as “root” or some other administrative identity, but it poses a real risk to the system. If Bob unexpectedly exposes the system to a virus or malicious website while using administrative privileges, the system may quickly become compromised. © Jones &We Bartlett can solve Learning,Bob’s problem LLC if we can specify additional ©access Jones rights & for Bartlett Learning, LLC NOT FOReach file SALE and folder. OR DISTRIBUTIONThere are two choices, depending on whichNOT operating FOR sys SALE- OR DISTRIBUTION tem we use: 1. Keep a list of access rights for each file, called the access control list (ACL). Each entry in the ACL identifies a specific user and contains a list of access rights granted to that user. This is available on modern versions of Windows © Jones & Bartlett Learning,and on Apple’s LLC MacOS. © Jones & Bartlett Learning, LLC NOT FOR SALE OR2. DISTRIBUTIONKeep one additional set of access rights, andNOT associate FOR it SALEwith a user OR group DISTRIBUTION. Associate a group with each file, just as we associate a user, the owner, with each file. This is available on all Unix-based systems. Windows uses a simple version of ACLs to provide basic file sharing on “home” editions© Jones of Windows. & Bartlett All Unix-based Learning, systems LLC provide group-based access © Jones & Bartlett Learning, LLC controls. NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION Practical Tip: Always organize your files into separate folders according to their access rights. Bob and Tina need to share the bookkeeping files for the surveying company. They put the files they need to share into a specific folder. They set up the folder’s access rights to let them share the © Jones &files. Bartlett Neither BobLearning, nor Tina shouldLLC store files in that folder© unless Jones both & Bartlett Learning, LLC NOT FORof SALE them should OR DISTRIBUTIONbe sharing that file. If Bob hires another clerkNOT to FORwork SALE OR DISTRIBUTION on a different customer’s books, he should set up a separate folder for that clerk. © Jones & Bartlett 4.1.1Learning, Basic LLC File Sharing on Windows© Jones & Bartlett Learning, LLC NOT FOR SALE ORWindows DISTRIBUTION provides a very simple mechanism NOTfor sharing FOR files SALE among OR users DISTRIBUTION on a personal computer. The mechanism begins with an isolation policy; users have no access to other users’ personal files. Building on the isolation policy, we assign additional permissions to selected users. To implement tailored sharing, we put the files in a folder and enable file shar- ing for that© folder. Jones File &sharing Bartlett recognizes Learning, three sets LLC of access rights: © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 1.
Recommended publications
  • Reference Guide

    Reference Guide

    Reference Guide Scyld ClusterWare Release 5.10.1-5101g0000 December 18, 2013 Reference Guide: Scyld ClusterWare Release 5.10.1-5101g0000; December 18, 2013 Revised Edition Published December 18, 2013 Copyright © 1999 - 2013 Penguin Computing, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise) without the prior written permission of Penguin Computing, Inc.. The software described in this document is "commercial computer software" provided with restricted rights (except as to included open/free source). Use beyond license provisions is a violation of worldwide intellectual property laws, treaties, and conventions. Scyld ClusterWare, the Highly Scyld logo, and the Penguin Computing logo are trademarks of Penguin Computing, Inc.. Intel is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. Infiniband is a trademark of the InfiniBand Trade Association. Linux is a registered trademark of Linus Torvalds. Red Hat and all Red Hat-based trademarks are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries. All other trademarks and copyrights referred to are the property of their respective owners. Table of Contents Preface .....................................................................................................................................................................................v
  • Filedes = Open(Name, Mode) Opens an Existing File with the Given Name

    Filedes = Open(Name, Mode) Opens an Existing File with the Given Name

    Computer Science 425 Distributed Systems CS 425 / ECE 428 Fall 2013 Indranil Gupta (Indy) December 3, 2013 Lecture 27 Distributed File Systems Chapter 12 (relevant parts) 2013, I. Gupta, K. Nahrtstedt, S. Mitra, N. Vaidya, M. T. Harandi, J. Hou Lecture 27-1 File Attributes & System Modules File Attribute Block Block Block Record length creation timestamp File read timestamp Directory Module Access write timestamp Module attribute timestamp File Module Block reference count Module file type Access control ownership Device Module Module access control list File System Modules Lecture 27-2 UNIX File System Operations filedes = open(name, mode) Opens an existing file with the given name . filedes = creat(name, mode) Creates a new file with the given name . Both operations deliver a file descriptor referencing the open file. The mode is read, write or both. status = close(filedes) Closes the open file filedes. count = read(filedes, buffer, n) Transfers n bytes from the file referenced by filedes to buffer . count = write(filedes, buffer, n) Transfers n bytes to the file referenced by filedes from buffer. Both operations deliver the number of bytes actually transferred and advance the read-write pointer. pos = lseek(filedes, offset, Moves the read-write pointer to offset (relative or absolute, whence) depending on whence). status = unlink(name) Removes the file name from the directory structure. If the file has no other links to it, it is deleted from disk. status = link(name1, name2) Creates a new link (name2) for a file (name1 ). status = stat(name, buffer) Gets the file attributes for file name into buffer. Lecture 27-3 Distributed File System (DFS) Requirements Transparency : server-side changes should be invisible to the client-side.
  • Apple File System Reference

    Apple File System Reference

    Apple File System Reference Developer Contents About Apple File System 7 General-Purpose Types 9 paddr_t .................................................. 9 prange_t ................................................. 9 uuid_t ................................................... 9 Objects 10 obj_phys_t ................................................ 10 Supporting Data Types ........................................... 11 Object Identifier Constants ......................................... 12 Object Type Masks ............................................. 13 Object Types ................................................ 14 Object Type Flags .............................................. 20 EFI Jumpstart 22 Booting from an Apple File System Partition ................................. 22 nx_efi_jumpstart_t ........................................... 24 Partition UUIDs ............................................... 25 Container 26 Mounting an Apple File System Partition ................................... 26 nx_superblock_t ............................................. 27 Container Flags ............................................... 36 Optional Container Feature Flags ...................................... 37 Read-Only Compatible Container Feature Flags ............................... 38 Incompatible Container Feature Flags .................................... 38 Block and Container Sizes .......................................... 39 nx_counter_id_t ............................................. 39 checkpoint_mapping_t ........................................
  • AMS Designer Migration, Usability, and Performance Improvements

    AMS Designer Migration, Usability, and Performance Improvements

    AMS Designer Migration, Usability, and Performance Improvements Cadence Design Systems Indu Jain, Tina Najibi, Lei Song, Junwei Hou, Vijay Setia, Poonam Singhal Presented at AMS Designer from SpectreVerilog: Migration and Usability Improvements Indu Jain Tina Najibi Lei Song Junwei Hou Vijay Setia Poonam Singhal which is becoming critical as more and more ABSTRACT digital IP adheres to that standard. Furthermore, whereas in the 90s almost all mixed-signal design was created by Analog designers in the Virtuoso ® AMS Designer (AMSD) contains a Virtuoso ® Analog Design Environment (ADE), wide breadth of state of the art features today an increasing number of digital designers exceeding those of other solutions such as and verification engineers are required to run SpectreVerilog. In spite of this, many customers mixed-signal full chip simulations on the continue to use SpectreVerilog, as the migration command line. This is an area where path from SpectreVerilog to AMSD contains a SpectreVerilog is rarely, if ever, used and in fact number of barriers and ease of use issues. This was not created to meet this need. paper will discuss the solutions to barriers such as PDK conversion, design modifications and AMS Designer (AMSD), on the other hand, was verilog text usage. Additionally, this session will created to meet the demands of full chip present performance gains as well as usability simulations on the command line as well as the and debugability improvements. The demands of Analog designers in ADE. AMSD is introduction of a new netlister in the AMSD flow a feature and language rich simulator, built on (the OSS netlister) and a new simulator flow the NC technology using the latest language makes these solutions possible.
  • (Fall 2009) Lecture 19 Distributed File Systems Reading

    (Fall 2009) Lecture 19 Distributed File Systems Reading

    Computer Science 425/ECE 428/CSE 424 Distributed Systems (Fall 2009) Lecture 19 Distributed File Systems Reading: Chapter 8 Acknowledgement • The slides during this semester are based on ideas and material from the following sources: – Slides prepared by Professors M. Harandi, J. Hou, I. Gupta, N. Vaidya, Y-Ch. Hu, S. Mitra. – Slides from Professor S. Gosh’s course at University o Iowa. Administrative • MP2 posted October 5, 2009, on the course website, – Deadline November 6 (Friday) – Demonstration, 4-6pm, 11/6/2009 – Tutorial for MP2 planned for October 28 evening if students send questions to TA by October 25. Send requests what you would like to hear in the tutorial. Administrative • MP3 proposal instructions – Deadline for MP3 proposal: October 25, 2009, email proposal to TA – At least one representative of each group meets with instructor or TA during October 26-28 during their office hours ) watch for extended office hours during these days. – Wednesday, October 28, 8:30-10am – instructor’s office hours 3104 SC – No office hours, Thursday, 29, 9-10am Administrative • Homework 3 posted on Thursday, October 15 – Deadline: Thursday, October 29, 2009 at the beginning of class • Midterm Re-grading Period by Instructor – additional office hours: – October 27, 3:15-4pm – in 3104 SC – October 29, 3:15-4pm – in 3104 SC Plan for Today • File Systems – Review • Distributed File Systems – Requirements • File System Architecture • Network File System (NFS) • Andrew File System (AFS) File Systems A file is a collection of data with a user view (file structure) and a physical view (blocks). A directory is a file that provides a mapping from text names to internal file identifiers.
  • Database-Installation-Guide-Linux.Pdf

    Database-Installation-Guide-Linux.Pdf

    Oracle® Database Database Installation Guide 19c for Linux E96432-19 July 2021 Oracle Database Database Installation Guide, 19c for Linux E96432-19 Copyright © 2015, 2021, Oracle and/or its affiliates. Primary Authors: Prakash Jashnani, Subhash Chandra Contributing Authors: Douglas Williams Contributors: Jean-Francois Verrier, Richard Roddy, Neha Avasthy, Sampath Ravindhran, Prasad Bagal, Subhranshu Banerjee, Gerald Venzl, Tammy Bednar, Avi Miller, Gavin Bowe, Gia-Khanh Nguyen, Darcy Christensen, Kiran Chamala, Jonathan Creighton, Benoit Dageville, Logeshwaran Rajan, Rajesh Dasari, Angad Gokakkar , Anu Natarajan, Girdhari Ghantiyala, Bernard Clouse, Chandrasekharan Iyer, Anil Nair, Sivaram Soma, Lisa Vaz, Ranjit Noronha, Vasu Venkatasubramanian, Sumanta Chatterjee, Margaret Susairaj, Malai Stalin, Markus Michalewicz, Subrahmanyam Kodavaluru, Sudip Datta, Madhu Hunasigi, Jim Erickson, Marcus Fallen, Joseph Francis, Allan Graves, Barbara Glover, Asad Hasan, Thirumaleshwara Hasandka, Putta Ramesh, Sergio Leunissen, Aneesh Khandelwal, Joel Kallman, Eugene Karichkin, Jai Krishnani, Prasad K Kulkarni, Ranjith Kundapur, Balaji Pagadala, Christopher Jones, Tak Wang, Bryn Llewellyn, Saar Maoz, Chao Liang, Gopal Mulagund, Pushkar Punit, Sivaselvam Narayanasamy, Ankur Kemkar, Sue Lee, Rich Long, Ricardo Alonso Gonzalez Acuna, Barb Lundhild, Sangeeth Jose, Rudregowda Mallegowda, Prasad Kuruvadi Nagaraj, Mughees Minhas, Krishna Mohan, Matthew McKerley, John McHugh, Gurudas Pai, Satish Panchumarthy , Rajesh Prasad, Rajendra Pingte, Ramesh Chakravarthula,
  • SPICE2 – a Spatial Parallel Architecture for Accelerating the SPICE Circuit Simulator

    SPICE2 – a Spatial Parallel Architecture for Accelerating the SPICE Circuit Simulator

    SPICE2 { A Spatial Parallel Architecture for Accelerating the SPICE Circuit Simulator Thesis by Nachiket Kapre In Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy California Institute of Technology Pasadena, California 2010 (Submitted October 26, 2010) c 2010 Nachiket Kapre All Rights Reserved ii Abstract Spatial processing of sparse, irregular floating-point computation using a single FPGA enables up to an order of magnitude speedup (mean 2.8× speedup) over a conven- tional microprocessor for the SPICE circuit simulator. We deliver this speedup us- ing a hybrid parallel architecture that spatially implements the heterogeneous forms of parallelism available in SPICE. We decompose SPICE into its three constituent phases: Model-Evaluation, Sparse Matrix-Solve, and Iteration Control and parallelize each phase independently. We exploit data-parallel device evaluations in the Model- Evaluation phase, sparse dataflow parallelism in the Sparse Matrix-Solve phase and compose the complete design in streaming fashion. We name our parallel architec- ture SPICE2: Spatial Processors Interconnected for Concurrent Execution for ac- celerating the SPICE circuit simulator. We program the parallel architecture with a high-level, domain-specific framework that identifies, exposes and exploits parallelism available in the SPICE circuit simulator. Our design is optimized with an auto-tuner that can scale the design to use larger FPGA capacities without expert intervention and can even target other parallel architectures with the assistance of automated code-generation. This FPGA architecture is able to outperform conventional proces- sors due to a combination of factors including high utilization of statically-scheduled resources, low-overhead dataflow scheduling of fine-grained tasks, and overlapped processing of the control algorithms.
  • Client-To-Site VPN

    Client-To-Site VPN

    Barracuda CloudGen Firewall Client-to-Site VPN https://campus.barracuda.com/doc/41116193/ With client-to-site VPNs, mobile workers can remotely access corporate information resources. VPNs provide access without the bandwidth, scalability, and manageability limitations of RAS implementations. With the Barracuda NG Firewall, you can set up the following types of client-to-site VPNs: Barracuda TINA TINA is a Barracuda Networks proprietary VPN protocol. It offers a secure end-to-end solution that does not require additional third-party software or input. Every Barracuda NG Firewall includes a root- level Certificate Authority (CA), letting you create, delete, and renew X.509 certificates for strong authentication. TINA offers substantial improvement over the IPsec protocol. It provides the following: High level of security. For supported encryption standards, see Authentication, Encryption, and Transport. A full-featured Certificate Authority (CA) for TINA VPNs on every Barracuda NG Firewall, for use of self-signed certificates. X.509 certificate-based VPN authentication with password request. Immunity to NAT or proxy (HTTPS, SOCKS) traversal. Supported VPN Clients The following VPN clients are supported for use with Barracuda VPNs: Barracuda VPN Client (Windows) Barracuda VPN Client for macOS Barracuda VPN Client for Linux Setting Up a Barracuda Client-to-Site VPN For instructions on how to set up a Barracuda VPN, see the following articles: How to Configure a Client-to-Site Barracuda VPN (TINA) How to Configure a Client-to-Site TINA VPN with Client Certificate Authentication Getting Started with the Barracuda VPN and Network Access Client Client-to-Site VPN 1 / 5 Barracuda CloudGen Firewall IPsec IPsec is the most widely used secure cross-platform VPN protocol.
  • COMPATIBILITY GUIDE En Tina 4.6.6

    COMPATIBILITY GUIDE En Tina 4.6.6

    TIME NAVIGATOR Compatibility Guide for Tina 2020 October 2020 N ° 1 E U R O P E A N S O F T W A R E V E N D O R F O R D A T A P R O T E C T I O N A T E M P O . C O M TABLE OF CONTENTS General information about Tina 2020 Compatibility guide ................................... 2 Agent for Office 365 email & OneDrive ............................................................. 11 Co-residence with other Atempo products ............................................................. 2 HyperVision Agent for Microsoft Exchange .................................................... 12 Automated Library Management Please consult the Atempo-Hardware Time Navigator for Microsoft Exchange (classic agent) ................................. 12 Compatibility Guide for library & drive support. ..................................................... 2 Time Navigator for Microsoft SharePoint Server ............................................. 12 Support Lifecycle ........................................................................................................ 3 Time Navigator for Microsoft SQL Server ......................................................... 13 Time Navigator Operating System compatibility ................................................... 4 Time Navigator for SAP ERP (ECC) on Oracle (using BACKINT) ................ 13 HyperVision Agent for VMware ................................................................................ 6 Time Navigator for SAP HANA (using BACKINT) ........................................... 13 HSS & HVDS Compatibility
  • SGI NAS CIFS User Guide

    SGI NAS CIFS User Guide

    SGI NAS CIFS User Guide Release 3.1.x 007-5949-001 Copyright © 2013 SGI. All rights reserved; provided portions may be copyright in third parties, as indicated elsewhere herein. No permission is granted to copy, distribute, or create derivative works from the contents of this electronic documentation in any manner, in whole or in part, without the prior written permission of SGI. SGI reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. Refer to the latest product announcement or contact your local SGI representative for information on feature and product availability. This document includes the latest information available at the time of publication. TRADEMARKS AND ATTRIBUTIONS SGI, Silicon Graphics, Supportfolio and the SGI logo are trademarks or registered trademarks of Silicon Graphics International Corp. or its subsidiaries in the United States and other countries. Solaris and OpenSolaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Microsoft and Windows are registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks mentioned herein are the property of their respective owners. Document Number: 007-5949-001 SGI NAS CIFS User Guide Table of Contents 1 Overview .................................................................................................................................1 1.1 Purpose ............................................................................................................................1
  • Technical Overview

    Technical Overview

    9 Product Documentation Likewise Enterprise Technical Overview IN THIS DOCUMENT Abstract • Authenticating Users This overview describes how Likewise joins non-Windows computers to • Authorizing Users and Groups Active Directory, authenticates users, authorizes users and groups for Managing Users and Groups • access to resources, stores Unix and Linux user information in Active • Applying Group Policies Directory, and manages Linux and Unix computers with group policies. The • Software Components and overview also outlines Likewise's two operating modes, its use of cells, and Architecture its software components and processes. Copyright © 2008 Likewise Software. All rights reserved. 1 Product Documentation Likewise Enterprise: Technical Overview The information contained in this document represents the current view of Likewise Software on the issues discussed as of the date of publication. Because Likewise Software must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Likewise, and Likewise Software cannot guarantee the accuracy of any information presented after the date of publication. These documents are for informational purposes only. LIKEWISE SOFTWARE MAKES NO WARRANTIES, EXPRESS OR IMPLIED. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in, or introduced into a retrieval system, or transmitted in any form, by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Likewise Software. Likewise may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Likewise, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
  • Advanced Remote Access for Barracuda Cloudgen Firewall

    Advanced Remote Access for Barracuda Cloudgen Firewall

    SOLUTION BRIEF Advanced Remote Access for Barracuda CloudGen Firewall With today’s mobile and remote workforce, the focus is on employee productivity rather than location. Work is being done anytime and anywhere—at home, in the coffee shop, on a train. Giving workers the freedom to do their work outside the office, without fixed hours, from their BYOD is a growing trend. At the same time the IT department needs to roll out these connectivity options across multiple platforms, prevent unauthorized access, enforce access policies, provide multi-factor authentication and ensure always on availability with fewer resources, but on a global level. The Advanced Remote Access subscription for Barracuda CloudGen Firewall extends the basic VPN connectivity provided with every device to enable all the above—at a fraction of the price point of dedicated solutions - in the most flexible and convenient way, for the end user and the administrator. Every Barracuda CloudGen Firewall supports an unlimited The app is available for Windows, macOS, iOS, and Android number of VPN clients at no extra cost. Barracuda’s Network and is available for download from the respective app stores. Access VPN client provides a sophisticated VPN client for End users can install the app without elevated privileges on the Windows, macOS, and Linux that provides richer performance device. CudaLaunch looks and feels the same on every platform and functionality than standard IPsec client software. and provides fast, Java-independent access to commonly used applications in the company network – regardless if hosted on- Benefits include quick restoration of VPN tunnels, “Always On” premises or in the cloud.