DOCSLIB.ORG

File Systems and Sysadmin

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

;login FEBRUARY 2014 VOL. 39, NO. 1 : File Systems and Sysadmin & An Overview of Object Storage Matthew W. Benjamin, Casey Bodley, Adam C. Emerson, and Marcus Watts & Hadoop 2 Sanjay Radia and Suresh Srinivas & Loser Buys, Two Tales of Debugging Mark Bainter and David Josephsen & Improving Performance of Logging Reports and Dashboards David Lang & Change Management Jason Paree and Andy Seely Columns Practical Perl Tools: Redis Meets Perl David N. Blank-Edelman Python: The Wheels Keep on Spinning David Beazley iVoyeur: Counters Dave Josephsen For Good Measure: Measuring Security Book Value Dan Geer and Gunnar Peterson /dev/random: Cybertizing the World Robert Ferrell Conference Reports LISA ’13: 27th Large Installation System Administration Conference Advanced Topics Workshop at LISA ’13 UPCOMING EVENTS FAST ’14: 12th USENIX Conference on File and 23rd USENIX Security Symposium Storage Technologies August 20–22, 2014, San Diego, CA, USA February 17–20, 2014, Santa Clara, CA, USA www.usenix.org/sec14 www.usenix.org/fast14 Submissions due: February 27, 2014 2014 USENIX Research in Linux File and Storage Workshops Co-located with USENIX Security ’14 Technologies Summit EVT/WOTE ’14: 2014 Electronic Voting Technology In conjunction with FAST ’14 Workshop/Workshop on Trustworthy Elections February 20, 2014, Mountain View, CA, USA USENIX Journal of Election Technology and Systems (JETS) NSDI ’14: 11th USENIX Symposium on Networked Published in conjunction with EVT/WOTE Systems Design and Implementation www.usenix.org/jets April 2–4, 2014, Seattle, WA, USA Submissions for Volume 2, Issue 3, due: April 8, 2014 www.usenix.org/nsdi14 HotSec ’14: 2014 USENIX Summit on Hot Topics 2014 USENIX Federated Conferences Week in Security June 17–20, 2014, Philadelphia, PA, USA FOCI ’14: 4th USENIX Workshop on Free and Open HotCloud ’14: 6th USENIX Workshop on Communications on the Internet Hot Topics in Cloud Computing HealthTech ’14: 2014 USENIX Workshop on Health June 17–18, 2014 Information Technologies www.usenix.org/hotcloud14 Safety, Security, Privacy, and Interoperability Submissions due: March 6, 2014 of Health Information Technologies HotStorage ’14: 6th USENIX Workshop CSET ’14: 7th Workshop on Cyber Security on Hot Topics in Storage and File Systems Experimentation and Test June 17–18, 2014 www.usenix.org/hotstorage14 WOOT ’14: 8th USENIX Workshop on Offensive Submissions due: March 13, 2014 Technologies WiAC ’14: 2014 USENIX Women in Advanced OSDI ’14: 11th USENIX Symposium on Operating Computing Summit Systems Design and Implementation June 18, 2014 October 6–8, 2014, Broomfield, CO, USA www.usenix.org/wiac14 www.usenix.org/osdi14 ICAC ’14: 11th International Conference on Abstract registration due: April 24, 2014 Autonomic Computing Co-located with OSDI ’14: June 18–20, 2014 www.usenix.org/icac14 Diversity ’14: 2014 Workshop on Diversity Paper titles and abstracts due: February 26, 2014 in Systems Research USENIX ATC ’14: 2014 USENIX Annual Technical LISA ’14: 28th Large Installation System Conference Administration Conference June 19–20, 2014 November 9–14, 2014, Seattle, WA, USA www.usenix.org/atc14 www.usenix.org/lisa14 UCMS ’14: 2014: USENIX Configuration Management Submissions due: April 14, 2014 Summit June 19, 2014 www.usenix.org/ucms14 URES ’14: 2014 USENIX Release Engineering Summit June 20, 2014 www.usenix.org/ures14 twitter.com/usenix www.usenix.org/youtube www.usenix.org/gplus Stay Connected... www.usenix.org/facebook www.usenix.org/linkedin www.usenix.org/blog FEBRUARY 2014 VOL. 39, NO. 1 EDITORIAL EDITOR Rik Farrow 3 Musings Rik Farrow [email protected] MANAGING EDITOR FILE SYSTemS Rikki Endsley 6 A Saga of Smart Storage Devices: An Overview of Object Storage [email protected] Matthew W. Benjamin, Casey Bodley, Adam C. Emerson, and Marcus Watts COPY EDITOR 12 HADOOP 2: What’s New Steve Gilmartin Sanjay Radia and Suresh Srinivas [email protected] PRODUCTION MANAGER SYSADMIN Michele Nelson 16 The Evolution of Managed Change in a Complex IT Enterprise PRODUCTION Jason Paree and Andy Seely Arnold Gatilao Casey Henderson 20 Logging Reports and Dashboards TYPESETTER David Lang Star Type 26 Loser Buys: A Troublesome Retrospective [email protected] Mark Bainter and Dave Josephsen USENIX ASSOCIATION 2560 Ninth Street, Suite 215, 30 When Data Is a Risk: Data Loss Prevention Tools and Their Role Berkeley, California 94710 within IT Departments Phone: (510) 528-8649 Klaus Haller FAX: (510) 548-5738 35 Using a Database to Store Data Captured with tcpdump www.usenix.org Mihalis Tsoukalos ;login: is the official magazine of the USENIX Association. ;login: (ISSN 1044-6397) COLUMNS is published bi-monthly by the USENIX Association, 2560 Ninth Street, Suite 215, 38 Practical Perl Tools: Redis Meet Perl David N. Blank-Edelman Berkeley, CA 94710. 42 The Wheels Keep on Spinning David Beazley $90 of each member’s annual dues is for a subscription to ;login:. Subscriptions for non- 46 iVoyeur: Counters Dave Josephsen members are $90 per year. Periodicals postage 49 Margin of Safety or Speculation? Measuring Security Book Value paid at Berkeley, CA, and additional offices. Dan Geer and Gunnar Peterson POSTMASTER: Send address changes to ;login:, USENIX Association, 2560 Ninth Street, 52 /dev/random Robert Ferrell Suite 215, Berkeley, CA 94710. ©2014 USENIX Association BOOKS USENIX is a registered trademark of the 54 Book Reviews Elizabeth Zwicky, with Mark Lamourine USENIX Association. Many of the designations used by manufacturers and sellers to USENIX NOTES distinguish their products are claimed as trademarks. USENIX acknowledges all 59 Transition of USENIX Leadership trademarks herein. Where those designations Anne Dickison and Casey Henderson appear in this publication and USENIX is aware of a trademark claim, the designations have 60 2014 Election for USENIX Board of Directors been printed in caps or initial caps. Margo Seltzer and Niels Provos, 2014 USENIX Board Nominating Committee 60 Thanks, Rikki Endsley Casey Henderson CONFERENce RePORTS 61 LISA ’13: 27th Large Installation System Administration Conference 90 Advanced Topics Workshop at LISA ’13 Musings RIK FEDITORIALARROW Rik is the editor of ;login:. like to attend the SNIA Storage Developer Conference [1], looking for [email protected] ideas and authors for the February issue of ;login:. Although the main I focus of SDC continues to be Microsoft SMB, I get to learn about other network/distributed file systems while there. Not that SMB 3 is not amazing. If you are still using older versions of Microsoft’s networked file system, you are living in the dark ages. But I was after other prey, topics of greater inter- est to file system and storage researchers. I’ve long been interested in Parallel NFS (pNFS), the long-awaited set of standards that allow the venerable NFS to work over a collection of storage servers. So I attended the pNFS BoF one evening at SDC, only to find that I was one of only five people there. I did say this was mainly an SMB conference. Fortunately for me, the people there, Brent Welch (Google), Matt Benjamin, Adam Emerson, and Marcus Watts (all with CohortFS) were willing to talk about distributed file systems. When I asked the CohortFS people what they were working on, the talk turned to object storage systems. File Systems I have a confession to make: I had no idea what a file system was by the end of the operating systems class I took in 1978. The class textbook covered IBM only, and years later, the class’ professor heavily criticized my chapter on file systems for my system administration book. That was certainly ironic, as he had totally failed to cover the topic. Then again, perhaps that was why he had commented that the material was “unnecessary.” In the 1970s, file systems were a bit alien. Really. People in the operating system course labs carried cases of punch cards. These weren’t their backups: they were the storage system. The ability to store files online was just beginning at the University of Maryland. So when I was tasked with writing a file system, I was stumped. I knew I had to build data structures that held lists of blocks, but beyond that, I had no idea what to do. I had never knowingly interacted with a file system. Three years later, I had my own, home-built, microcomputer system, which ran CP/M on 1 floppy disks, using a flat file system. My computer had built-in 5 /4-inch drives, but most of my customers used 8-inch floppies (with a capacity of more than 200 kilobytes!). I had both an external 8-inch drive and a Morrow DJIO card, and because I had written the manual for the DJIO, I thought I could patch in access to the 8-inch drive. What I did was build a device driver and CP/M file system, all in two pages of C code. Things were a lot simpler then. And, fortunately for me, there were other sources of knowledge about file systems (magazine articles in Byte!) than the professor who had ignored this topic. Object Stores As you will learn when you read the object storage article in this issue, object stores have been around since work done by Garth Gibson in 1990. His initial research into network attached storage devices (NASD) grew into Panasas, and later into object storage standards. Gibson and 2 FEBRUARY 2014 VOL. 39, NO. 1 www.usenix.org EDITORIAL Musings his cohorts had built a POSIX-compatible interface that allowed Kinetic drive fails? Not that the long-favored scheme of RAID for access to distributed object storage as if they were a more tradi- reliability works with drives as large as four terabytes. And repli- tional file system. The interface hid the behind-the-scenes work cation is expensive in terms of space for reliability. of distributing data among different devices to produce fast, reli- You can read about other peoples’ opinions about Seagate’s able, and scalable storage systems for super computers.
Recommended publications
  • Elastic Storage for Linux on System Z IBM Research & Development Germany

    Elastic Storage for Linux on System Z IBM Research & Development Germany

    Peter Münch T/L Test and Development – Elastic Storage for Linux on System z IBM Research & Development Germany Elastic Storage for Linux on IBM System z © Copyright IBM Corporation 2014 9.0 Elastic Storage for Linux on System z Session objectives • This presentation introduces the Elastic Storage, based on General Parallel File System technology that will be available for Linux on IBM System z. Understand the concepts of Elastic Storage and which functions will be available for Linux on System z. Learn how you can integrate and benefit from the Elastic Storage in a Linux on System z environment. Finally, get your first impression in a live demo of Elastic Storage. 2 © Copyright IBM Corporation 2014 Elastic Storage for Linux on System z Trademarks The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. AIX* FlashSystem Storwize* Tivoli* DB2* IBM* System p* WebSphere* DS8000* IBM (logo)* System x* XIV* ECKD MQSeries* System z* z/VM* * Registered trademarks of IBM Corporation The following are trademarks or registered trademarks of other companies. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
  • Security in Cloud Computing a Security Assessment of Cloud Computing Providers for an Online Receipt Storage

    Security in Cloud Computing a Security Assessment of Cloud Computing Providers for an Online Receipt Storage

    Security in Cloud Computing A Security Assessment of Cloud Computing Providers for an Online Receipt Storage Mats Andreassen Kåre Marius Blakstad Master of Science in Computer Science Submission date: June 2010 Supervisor: Lillian Røstad, IDI Norwegian University of Science and Technology Department of Computer and Information Science Problem Description We will survey some current cloud computing vendors and compare them to find patterns in how their feature sets are evolving. The start-up firm dSafe intends to exploit the promises of cloud computing in order to launch their business idea with only marginal hardware and licensing costs. We must define the criteria for how dSafe's application can be sufficiently secure in the cloud as well as how dSafe can get there. Assignment given: 14. January 2010 Supervisor: Lillian Røstad, IDI Abstract Considerations with regards to security issues and demands must be addressed before migrating an application into a cloud computing environment. Different vendors, Microsoft Azure, Amazon Web Services and Google AppEngine, provide different capabilities and solutions to the individual areas of concern presented by each application. Through a case study of an online receipt storage application from the company dSafe, a basis is formed for the evaluation. The three cloud computing vendors are assessed with regards to a security assessment framework provided by the Cloud Security Alliance and the application of this on the case study. Finally, the study is concluded with a set of general recommendations and the recommendation of a cloud vendor. This is based on a number of security as- pects related to the case study’s existence in the cloud.
  • Educational Directory, 1

    Educational Directory, 1

    DEPARTMENT OF THEINTERIOR BUREAU OF EDUCATION BULLETIN, 1922, No.50, EDUCATIONALDIRECTORY 1922-1923 WASHINGTON GOVERNMENT PRINTING OFFICE 1923 A u ADDITIONAL COPIES OP THIS PUBLICATION MAY BE PROCURED rams THE SUPERINTENDENT OF DOCUMENTS GOVERNMENT PRINTING OFFICE WASHINGTON, AT 115 CENTS PER COPY PURCHASER AGREES NOT TO RESELL 1SR DISTRIBUTE THIS COPT TOR PROT1T.-P1111. RES. S7, APPROVED MAY 11, 1923 IL CONTENTS. I. The United StatesBureau of Education Page: II. Principal State school officers 1 III. County and other local 3 superintendents of schools.- 13 IV. Superintendents of prIblic schools in cities and towns. 46 V. Presidents of universities andcolleges VI. Presidents of junior 67 77 VII. Heads 9f departm nts ofeducation 78 N111 I. Presidentsor deans of schools of theology 87 IX. Presidents or deans of schools of law 90 X. Presidents or deans of schools of tiielicine 92 XI. Presidents or deans of schools of dentistry 94 Presidents or deans of schools of pharmacy.. XII I. Presidents of schools of 94' osteopathy 96 X IV. Presidents or deans of srliools of veterinary medicine 96 XV. Presidents, etc.. of institutionsfor the training of teachers: 1. Presidents of teachers' colleges. 96 II. Principals of normal training schools: 1. Public normal sclu 99 2. Private normal selfols 104 'III. Directors of kindergarten training incolleges, normal schools, and kindergarten training 84110eild 105 XVI. Directors of.summer schools 109 XVII. Librarians of Public and society Librai 126 XVIII. Executive officers of State library 151 X IX. Directors of librafy schools 152 X X. Educational boards and foundations X X I. Church. educational boards and 152 societies.
  • Protocols: 0-9, A

    Protocols: 0-9, A

    Protocols: 0-9, A • 3COM-AMP3, on page 4 • 3COM-TSMUX, on page 5 • 3PC, on page 6 • 4CHAN, on page 7 • 58-CITY, on page 8 • 914C G, on page 9 • 9PFS, on page 10 • ABC-NEWS, on page 11 • ACAP, on page 12 • ACAS, on page 13 • ACCESSBUILDER, on page 14 • ACCESSNETWORK, on page 15 • ACCUWEATHER, on page 16 • ACP, on page 17 • ACR-NEMA, on page 18 • ACTIVE-DIRECTORY, on page 19 • ACTIVESYNC, on page 20 • ADCASH, on page 21 • ADDTHIS, on page 22 • ADOBE-CONNECT, on page 23 • ADWEEK, on page 24 • AED-512, on page 25 • AFPOVERTCP, on page 26 • AGENTX, on page 27 • AIRBNB, on page 28 • AIRPLAY, on page 29 • ALIWANGWANG, on page 30 • ALLRECIPES, on page 31 • ALPES, on page 32 • AMANDA, on page 33 • AMAZON, on page 34 • AMEBA, on page 35 • AMAZON-INSTANT-VIDEO, on page 36 Protocols: 0-9, A 1 Protocols: 0-9, A • AMAZON-WEB-SERVICES, on page 37 • AMERICAN-EXPRESS, on page 38 • AMINET, on page 39 • AN, on page 40 • ANCESTRY-COM, on page 41 • ANDROID-UPDATES, on page 42 • ANET, on page 43 • ANSANOTIFY, on page 44 • ANSATRADER, on page 45 • ANY-HOST-INTERNAL, on page 46 • AODV, on page 47 • AOL-MESSENGER, on page 48 • AOL-MESSENGER-AUDIO, on page 49 • AOL-MESSENGER-FT, on page 50 • AOL-MESSENGER-VIDEO, on page 51 • AOL-PROTOCOL, on page 52 • APC-POWERCHUTE, on page 53 • APERTUS-LDP, on page 54 • APPLEJUICE, on page 55 • APPLE-APP-STORE, on page 56 • APPLE-IOS-UPDATES, on page 57 • APPLE-REMOTE-DESKTOP, on page 58 • APPLE-SERVICES, on page 59 • APPLE-TV-UPDATES, on page 60 • APPLEQTC, on page 61 • APPLEQTCSRVR, on page 62 • APPLIX, on page 63 • ARCISDMS,
  • Ispconfig 3 Manual]

    Ispconfig 3 Manual]

    [ISPConfig 3 Manual] ISPConfig 3 Manual Version 1.0 for ISPConfig 3.0.3 Author: Falko Timme <[email protected]> Last edited 09/30/2010 1 The ISPConfig 3 manual is protected by copyright. No part of the manual may be reproduced, adapted, translated, or made available to a third party in any form by any process (electronic or otherwise) without the written specific consent of projektfarm GmbH. You may keep backup copies of the manual in digital or printed form for your personal use. All rights reserved. This copy was issued to: Thomas CARTER - [email protected] - Date: 2010-11-20 [ISPConfig 3 Manual] ISPConfig 3 is an open source hosting control panel for Linux and is capable of managing multiple servers from one control panel. ISPConfig 3 is licensed under BSD license. Managed Services and Features • Manage one or more servers from one control panel (multiserver management) • Different permission levels (administrators, resellers and clients) + email user level provided by a roundcube plugin for ISPConfig • Httpd (virtual hosts, domain- and IP-based) • FTP, SFTP, SCP • WebDAV • DNS (A, AAAA, ALIAS, CNAME, HINFO, MX, NS, PTR, RP, SRV, TXT records) • POP3, IMAP • Email autoresponder • Server-based mail filtering • Advanced email spamfilter and antivirus filter • MySQL client-databases • Webalizer and/or AWStats statistics • Harddisk quota • Mail quota • Traffic limits and statistics • IP addresses 2 The ISPConfig 3 manual is protected by copyright. No part of the manual may be reproduced, adapted, translated, or made available to a third party in any form by any process (electronic or otherwise) without the written specific consent of projektfarm GmbH.
  • BESIII Physical Analysis on Hadoop Platform

    BESIII Physical Analysis on Hadoop Platform

    20th International Conference on Computing in High Energy and Nuclear Physics (CHEP2013) IOP Publishing Journal of Physics: Conference Series 513 (2014) 032044 doi:10.1088/1742-6596/513/3/032044 BESIII Physical Analysis on Hadoop Platform Jing HUO12, Dongsong ZANG12, Xiaofeng LEI12, Qiang LI12, Gongxing SUN1 1Institute of High Energy Physics, Beijing, China 2University of Chinese Academy of Sciences, Beijing, China E-mail: [email protected] Abstract. In the past 20 years, computing cluster has been widely used for High Energy Physics data processing. The jobs running on the traditional cluster with a Data-to-Computing structure, have to read large volumes of data via the network to the computing nodes for analysis, thereby making the I/O latency become a bottleneck of the whole system. The new distributed computing technology based on the MapReduce programming model has many advantages, such as high concurrency, high scalability and high fault tolerance, and it can benefit us in dealing with Big Data. This paper brings the idea of using MapReduce model to do BESIII physical analysis, and presents a new data analysis system structure based on Hadoop platform, which not only greatly improve the efficiency of data analysis, but also reduces the cost of system building. Moreover, this paper establishes an event pre-selection system based on the event level metadata(TAGs) database to optimize the data analyzing procedure. 1. Introduction 1.1 The current BESIII computing architecture High Energy Physics experiment is a typical data-intensive application. The BESIII computing system now consist of 3PB+ data, 6500 CPU cores, and it is estimated that there will be more than 10PB data produced in the future 5 years.
  • Persistent 9P Sessions for Plan 9

    Persistent 9P Sessions for Plan 9

    Persistent 9P Sessions for Plan 9 Gorka Guardiola, [email protected] Russ Cox, [email protected] Eric Van Hensbergen, [email protected] ABSTRACT Traditionally, Plan 9 [5] runs mainly on local networks, where lost connections are rare. As a result, most programs, including the kernel, do not bother to plan for their file server connections to fail. These programs must be restarted when a connection does fail. If the kernel’s connection to the root file server fails, the machine must be rebooted. This approach suffices only because lost connections are rare. Across long distance networks, where connection failures are more common, it becomes woefully inadequate. To address this problem, we wrote a program called recover, which proxies a 9P session on behalf of a client and takes care of redialing the remote server and reestablishing con- nection state as necessary, hiding network failures from the client. This paper presents the design and implementation of recover, along with performance benchmarks on Plan 9 and on Linux. 1. Introduction Plan 9 is a distributed system developed at Bell Labs [5]. Resources in Plan 9 are presented as synthetic file systems served to clients via 9P, a simple file protocol. Unlike file protocols such as NFS, 9P is stateful: per-connection state such as which files are opened by which clients is maintained by servers. Maintaining per-connection state allows 9P to be used for resources with sophisticated access control poli- cies, such as exclusive-use lock files and chat session multiplexers. It also makes servers easier to imple- ment, since they can forget about file ids once a connection is lost.
  • Globalfs: a Strongly Consistent Multi-Site File System

    Globalfs: a Strongly Consistent Multi-Site File System

    GlobalFS: A Strongly Consistent Multi-Site File System Leandro Pacheco Raluca Halalai Valerio Schiavoni University of Lugano University of Neuchatelˆ University of Neuchatelˆ Fernando Pedone Etienne Riviere` Pascal Felber University of Lugano University of Neuchatelˆ University of Neuchatelˆ Abstract consistency, availability, and tolerance to partitions. Our goal is to ensure strongly consistent file system operations This paper introduces GlobalFS, a POSIX-compliant despite node failures, at the price of possibly reduced geographically distributed file system. GlobalFS builds availability in the event of a network partition. Weak on two fundamental building blocks, an atomic multicast consistency is suitable for domain-specific applications group communication abstraction and multiple instances of where programmers can anticipate and provide resolution a single-site data store. We define four execution modes and methods for conflicts, or work with last-writer-wins show how all file system operations can be implemented resolution methods. Our rationale is that for general-purpose with these modes while ensuring strong consistency and services such as a file system, strong consistency is more tolerating failures. We describe the GlobalFS prototype in appropriate as it is both more intuitive for the users and detail and report on an extensive performance assessment. does not require human intervention in case of conflicts. We have deployed GlobalFS across all EC2 regions and Strong consistency requires ordering commands across show that the system scales geographically, providing replicas, which needs coordination among nodes at performance comparable to other state-of-the-art distributed geographically distributed sites (i.e., regions). Designing file systems for local commands and allowing for strongly strongly consistent distributed systems that provide good consistent operations over the whole system.
  • Designing a Free Data Loss Prevention System

    Designing a Free Data Loss Prevention System

    University of Piraeus Department of Digital Systems MSc in Security of Digital Systems Master Thesis Designing a free Data Loss Prevention system Dimitrios Koutsourelis March 2014 Data Loss Prevention Systems Supervisors Sokratis Katsikas, Professor University of Piraeus Spyros Papageorgiou, Captain (OF-5) Hellenic National Defense General Staff/ Directorate of Cyber Defense Dimitrios Koutsourelis 2 Data Loss Prevention Systems Abstract Data Loss is an everyday threat within all organizations. The leaking of confidential data ultimately results in a loss of revenue. A quarter of all Data Loss is widely attributed to the use of applications such as Voice, Email, Instant Messaging, Social Networks, Blogs, P2P and Videos. A common approach, adopted to prevent Data Loss is the use of sophisticated data detection algorithms and the deployment of systems to control applications, attempting to access the outside world [1]. Many vendors currently offer data loss prevention products for no small amount of money. This thesis focuses on providing all the necessary information needed to fully comprehend the terms that wrap around data loss prevention and illustrating some of the most common mechanisms and techniques used by the available software. Also, two publicly available, free, data loss prevention software tools, MyDLP and OpenDLP, are presented and analyzed. In the third part of this project, a system architecture is presented, designed to combine the two previously mentioned software in a way such that they co-exist inside an information system, complementing each other, providing solid data loss prevention services. Dimitrios Koutsourelis 3 Data Loss Prevention Systems Table of Contents 1 Introduction .......................................................................................................... 6 1.1 Background ....................................................................................................
  • To the Members of the Senate Judiciary Committee: We, The

    To the Members of the Senate Judiciary Committee: We, The

    To the members of the Senate Judiciary Committee: We, the undersigned, have played various parts in building a network called the Internet. We wrote and debugged the software; we defined the standards and protocols that talk over that network. Many of us invented parts of it. We're just a little proud of the social and economic benefits that our project, the Internet, has brought with it. We are writing to oppose the Committee's proposed new Internet censorship and copyright bill. If enacted, this legislation will risk fragmenting the Internet's global domain name system (DNS ), create an environment of tremendous fear and uncertainty for technological innovation, and seriously harm the credibility of the United States in its role as a steward of key Internet infrastructure. In exchange for this, the bill will introduce censorship that will simultaneously be circumvented by deliberate infringers while hampering innocent parties' ability to communicate. All censorship schemes impact speech beyond the category they were intended to restrict, but this bill will be particularly egregious in that regard because it causes entire domains to vanish from the Web, not just infringing pages or files. Worse, an incredible range of useful, law-abiding sites can be blacklisted under this bill. These problems will be enough to ensure that alternative name-lookup infrastructures will come into widespread use, outside the control of US service providers but easily used by American citizens. Errors and divergences will appear between these new services and the current global DNS, and contradictory addresses will confuse browsers and frustrate the people using them.
  • Absolute BSD—The Ultimate Guide to Freebsd Table of Contents Absolute BSD—The Ultimate Guide to Freebsd

    Absolute BSD—The Ultimate Guide to Freebsd Table of Contents Absolute BSD—The Ultimate Guide to Freebsd

    Absolute BSD—The Ultimate Guide to FreeBSD Table of Contents Absolute BSD—The Ultimate Guide to FreeBSD............................................................................1 Dedication..........................................................................................................................................3 Foreword............................................................................................................................................4 Introduction........................................................................................................................................5 What Is FreeBSD?...................................................................................................................5 How Did FreeBSD Get Here?..................................................................................................5 The BSD License: BSD Goes Public.......................................................................................6 The Birth of Modern FreeBSD.................................................................................................6 FreeBSD Development............................................................................................................7 Committers.........................................................................................................................7 Contributors........................................................................................................................8 Users..................................................................................................................................8
  • Using the Andrew File System on *BSD Hugo@Meiland.Nl, Bsdcan, 2006 Why Another Network Filesystem

    Using the Andrew File System on *BSD [email protected], Bsdcan, 2006 Why Another Network Filesystem

    Using the Andrew File System on *BSD [email protected], BSDCan, 2006 why another network filesystem 1-slide history of Andrew File System user view admin view OpenAFS Arla AFS on OpenBSD, FreeBSD and NetBSD Filesharing on the Internet use FTP or link to HTTP file interface through WebDAV use insecure protocol over vpn History of AFS 1984: developed at Carnegie Mellon 1989: TransArc Corperation 1994: over to IBM 1997: Arla, aimed at Linux and BSD 2000: IBM releases source 2000: foundation of OpenAFS User view <1> global filesystem rooted at /afs /afs/cern.ch/... /afs/cmu.edu/... /afs/gorlaeus.net/users/h/hugo/... User view <2> authentication through Kerberos #>kinit <username> obtain krbtgt/<realm>@<realm> #>afslog obtain afs@<realm> #>cd /afs/<cell>/users/<username> User view <3> ACL (dir based) & Quota usage runs on Windows, OS X, Linux, Solaris ... and *BSD Admin view <1> <cell> <partition> <server> <volume> <volume> <server> <partition> Admin view <2> /afs/gorlaeus.net/users/h/hugo/presos/afs_slides.graffle gorlaeus.net /vicepa fwncafs1 users hugo h bram <server> /vicepb Admin view <2a> /afs/gorlaeus.net/users/h/hugo/presos/afs_slides.graffle gorlaeus.net /vicepa fwncafs1 users hugo /vicepa fwncafs2 h bram Admin view <3> servers require KeyFile ~= keytab procedure differs for Heimdal: ktutil copy MIT: asetkey add Admin view <4> entry in CellServDB >gorlaeus.net #my cell name 10.0.0.1 <dbserver host name> required on servers required on clients without DynRoot Admin view <5> File locking no databases on AFS (requires byte range locking)