DOCSLIB.ORG

Mail NYC*BUG Hosts Eric Allman and Marshall Kirk Mckusick Meeting In

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Daemon News: October 2004 http://ezine.daemonnews.org/200410/ Mirrors Primary (US) Issues November 2004 October 2004 Get BSD Contact Us Search BSD FAQ New to BSD? DN Print Magazine BSD News BSD Mall BSD Support Join Us T H I S M O N T H ' S F E A T U R E S From the Editor Fetching Yahoo! Mail by Mikel King Editorial by Chris Coleman I thought it might be nice to start off with a simple little article about a How can you help advocate simple app in the ports tree that I find perticularly useful. It is called BSD? fetchyahoo, basically what it does is fetch your email out of your mail.yahoo.com account via the http interface and download it into a mailbox. Of course that may not seem all that special or important, Get BSD Stuff but what is really cool about this app is where it can put the messages, and some of the advanced features, like dump the bulk messages, and automatic expunging of the deleted messages. Read More NYC*BUG Hosts Eric Allman and Marshall Kirk McKusick Meeting in Manhattan by George Rosamond NYC*BUG Hosts Eric Allman and Marshall Kirk McKusick Meeting in Manhattan The NYC *BSD User Group held a special meeting on Saturday, Search October 16th with Eric Allman and Marshall Kirk McKusick speaking at Columbia University. Monthly Ezine Eric Allman , the creator of Sendmail, has been a critical component in the open source community for decades. Kirk McKusick is an Search original BSD Unix developer from the 1970's, and continues to play a leading role in the FreeBSD project to this day. Both Eric and Kirk are also heavily involved in USENIX. Read More BSD News BSDCan Schedule Released Lowest Common Denominator NetBSD and Xen by David Bogen NYCBUG monthly meeting Michael Shalayeff: OpenBSD on In most contexts, titling something the "lowest common denominator" PA-RISC is faint praise, if not an outright insult. Most people consider the Theo de Raadt presented lowest common denominator in social groups to be those traits and with the 2004 Free Software urges most closely associated with our base instincts: food, shelter, Award warmth, safety, procreation, etc. Some examples that social and First look at Solaris 10 technology critics might offer: Read More SCALE 3x Presentations and Wrap Up Repors Now Online ZoneBSD.org Launched! R E G U L A R C O L U M N S Comparison of NetBSD and FreeBSD Why They use BSD: Netcraft by George Rosamond Recently, Daemon News asked Mike Prettejohn from well-known web server survey firm Netcraft.com about why they use BSD. Here's BSDMall what Mike wrote: Read More Office Applications for Mac OS X Panther Ver 2.0 $39.95 Unix Utilities for Mac OS X Daemon's Advocate Panther Ver 3.0 $39.95 by Poul-Henning Kamp 1 of 2 08.03.2005 14:00 Daemon News: October 2004 http://ezine.daemonnews.org/200410/ I met Peter Salus the other evening, he was in Copenhagen for a talk Sipura SPA SIP Telephone and he invited me out because he has started writing yet a computer Adapter Just $105 history book (If you have not yet read "A quarter century of UNIX" Sayson Telephone PT-390 and "Casting the NET" by all means do so). Now $95 Digium T1 Controllers $480 He told me that Kirk had told him to talk to me about FreeBSD, and OpenBSD 3.4 $37.50 his first question, while we waited for our "Galletes" to arive was Need Reseller Pricing? Go to "Why bother ?" Read More Cylogistics! Miscellaneous Credits The hard-working crew Tarball Download a tar.gz version of this issue PDF Download a PDF version of this issue 2 of 2 08.03.2005 14:00 Daemon News '200410' : '"Advocating BSD "' http://ezine.daemonnews.org/200410/editorial.html October 2004 Get BSD New to BSD? Search BSD Submit News FAQ Contact Us Join Us Advocating BSD Search Chris Coleman Monthly Ezine I've long been a fan of BSD. I began using BSD seriously in 1995, mostly FreeBSD, but dabbling with the other projects as needs arose. As I began to Search be more proficient in BSD and the Unix technologies I looked around for ways that I could contribute back to the project that was helping me out. I didn't know how to code very well, so I turned to my other hobby and began Get BSD Stuff to write. I found I really liked writing about BSD and quickly found that I liked explaining technical things. The first project I started out on was overly difficult. I tried writing a book about FreeBSD. At the time, only Greg Lehey's Complete FreeBSD book was around and I thought it would be a good idea to see another one. Linux books had started to pop up here and there. I ended up writing a great deal of text that I posted on the internet for everyone to read as I went. It wasn't the success I dreamed about, however, I did manage to get a book contract with a large publisher a short time later and began working on a BSD book with two other friends. However, the publisher dropped the book after some difficulties with us turning in our chapters in a non-Word format. Also, I think they couldn't see the market for the FreeBSD book yet. But I didn't give up. I did decide that a book wasn't really what I wanted to do anyway. I turned my time back to working on smaller technical articles that I could more easily wrap my brain around. It's much easier to make one point in an article than to stay on topic while trying to lead up to that point in a larger work. So, all of my current work goes into the Daemon News Ezine. It's a lot of work and it's all volunteer. I also think it's worth it. I find myself often referring to articles on Daemon News when working on BSD related tasks. Sometimes they are even my own articles. (Which I wrote just to document how I did something so I wouldn't forget it.) But there is a lot more to be done. I feel that quite a bit more advocacy work could be done. Recently I have had to work with a few Linux installations and every time it reminds me how much I like BSD. I'm probably just biased, but I find BSD to be extremely well suited to the kind of work I do. However, I'd like to do more than just talk about how much advocacy we need. So, I've helped put together http://advocacy.daemonnews.org as a place where we can share ideas about BSD advocacy. Recently I put a note up there for people to call Digium to let them know about interest from the BSD community in their products. So far, their response seems to be positive. With a little effort from the community, we can keep BSD on the radar scope of companies developing hardware and add it to a few company buzz words. -Chris Coleman Author maintains all copyrights on this article. Images and layout Copyright © 1998-2004 Dæmon News. All Rights Reserved. 1 of 1 08.03.2005 14:00 Daemon News '200410' : '"Fetching Yahoo! Mail "' http://ezine.daemonnews.org/200410/fetchyahoo.html October 2004 Get BSD New to BSD? Search BSD Submit News FAQ Contact Us Join Us Fetching Yahoo! Mail Search By Mikel King <[email protected]> Monthly Ezine I thought it might be nice to start off with a simple little article about a simple app in the ports tree that I find particularly useful. It is called fetchyahoo. Search Basically, what it does is fetch your email out of your mail.yahoo.com account via the http interface and download it into a mailbox. Of course, that may not seem all that special or important, but what is really cool about this app is where it can put the messages, and some of the advanced features, like Get BSD Stuff dumping the bulk messages and automatic expunging of the deleted messages. Now, one of the first things I usually do before I build anything from the ports tree is run a quick cvsup off my in house mirror to refresh the tree on the machine I am using. I find that this is generally a good thing to do. For instance, the version in the ports tree is 2.8.6 and mine is 2.8.0 which, of course, is not that great, but if you are going to take the time to build something, then why not do it right? OK, so building the port is easy once you complete the cvsup. I did have some trouble with the fetching of various dependencies but I suspect that was more or less bandwidth related. But, eventually, the make install clean will complete and you will be able to step into the .fetchyahoorc configuration file. A sample can be found in the build directory, and excerpts are included for explanation, as follows. This first section is rather self explanatory, just substitute your yahoo credentials here and then proceed to the next section. ###### SHOULD configure these ###### username = *yahoo-user-name* # this can be a password or an md5_hex hashed password password = *yahoo-password* # set this to 0 to turn off HTTPS and login insecurely via plaintext instead use-https = 1 ###### mail spool, mbox file and procmail configs ###### # set use-spool to 0 to disable outputting to a file/filter use-spool = 1 # if spoolName ends with a / we output in maildir format to that directory spool = /var/spool/mail/*local-user-name* # spool-mode must be either append, pipe or overwrite # use pipe for procmail or other filter and append for a normal spool # ignored if spoolName is a maildir directory spool-mode = append OK, at this point we could fire off a sync and download the email into a standard Unix type mailbox.
Recommended publications
  • Proceedings of the Bsdcon 2002 Conference

    Proceedings of the Bsdcon 2002 Conference

    USENIX Association Proceedings of the BSDCon 2002 Conference San Francisco, California, USA February 11-14, 2002 THE ADVANCED COMPUTING SYSTEMS ASSOCIATION © 2002 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. Rethinking /devand devices in the UNIX kernel Poul-Henning Kamp <[email protected]> The FreeBSD Project Abstract An outstanding novelty in UNIX at its introduction was the notion of ‘‘a file is a file is a file and evenadevice is a file.’’ Going from ‘‘hardware only changes when the DEC Field engineer is here’’to‘‘my toaster has USB’’has put serious strain on the rather crude implementation of the ‘‘devices as files’’concept, an implementation which has survivedpractically unchanged for 30 years in most UNIX variants. Starting from a high-levelviewofdevices and the semantics that have grown around them overthe years, this paper takes the audience on a grand tour of the redesigned FreeBSD device-I/O system, to convey anoverviewofhow itall fits together,and to explain whythings ended up as theydid, howtouse the newfeatures and in particular hownot to. 1. Introduction tax and meaning, so that a program expecting a file name as a parameter can be passed a device name; There are really only twofundamental ways to concep- finally,special files are subject to the same protec- tualise I/O devices in an operating system: The usual tion mechanism as regular files.
  • Advanced Openbsd Hardening

    Advanced Openbsd Hardening

    Advanced Hardening WrongunWrongun && DCDC JuneJune 20052005 ssh://root:[email protected] Lab Challenge JoinJoin thethe wifiwifi netnet andand sshssh intointo thethe boxbox usingusing thethe accountaccount specifiedspecified inin thethe footerfooter TryTry toto pwnpwn thethe boxbox byby addingadding anan accountaccount forfor yourselfyourself oror backdooringbackdooring sshdsshd ssh://root:[email protected] “Only one remote hole in the default install, in more than 8 years! “ ssh://root:[email protected] So OpenBSD is uber secure, right? Actually,Actually, nono …… TheThe defaultdefault installinstall hashas nothingnothing enabledenabled (except(except ssh)ssh) ““NoNo wonderwonder itit ’’ss secure,secure, itit ’’ss poweredpowered off!off! ”” SourceSource --onlyonly patchingpatching strategystrategy makesmakes itit difficultdifficult toto rollroll outout fixesfixes toto platformsplatforms w/ow/o compilerscompilers (i.e.(i.e. disklessdiskless firewalls,firewalls, etc.)etc.) ssh://root:[email protected] Brief History of OpenBSD Vulnerabilities 30 March 05: Bugs in the cp(4) stack can lead to memory exhaustion or processing of TCP segments with invalid SACK optio ns and cause a system crash. 14 Dec 04: On systems running sakmpd(8) it is possible for a local user to cause kernel memory corruption and system panic by setti ng psec(4) credentials on a socket 20 Sept 04: radius authentication, as implemented by ogin_radius(8) , was not checking the shared secret used for replies sent by the radius server. This could allow an attacker to spoof
  • THE FUTURE of IDEAS This Work Is Licensed Under a Creative Commons Attribution-Noncommercial License (US/V3.0)

    THE FUTURE of IDEAS This Work Is Licensed Under a Creative Commons Attribution-Noncommercial License (US/V3.0)

    less_0375505784_4p_fm_r1.qxd 9/21/01 13:49 Page i THE FUTURE OF IDEAS This work is licensed under a Creative Commons Attribution-Noncommercial License (US/v3.0). Noncommercial uses are thus permitted without any further permission from the copyright owner. Permissions beyond the scope of this license are administered by Random House. Information on how to request permission may be found at: http://www.randomhouse.com/about/ permissions.html The book maybe downloaded in electronic form (freely) at: http://the-future-of-ideas.com For more permission about Creative Commons licenses, go to: http://creativecommons.org less_0375505784_4p_fm_r1.qxd 9/21/01 13:49 Page iii the future of ideas THE FATE OF THE COMMONS IN A CONNECTED WORLD /// Lawrence Lessig f RANDOM HOUSE New York less_0375505784_4p_fm_r1.qxd 9/21/01 13:49 Page iv Copyright © 2001 Lawrence Lessig All rights reserved under International and Pan-American Copyright Conventions. Published in the United States by Random House, Inc., New York, and simultaneously in Canada by Random House of Canada Limited, Toronto. Random House and colophon are registered trademarks of Random House, Inc. library of congress cataloging-in-publication data Lessig, Lawrence. The future of ideas : the fate of the commons in a connected world / Lawrence Lessig. p. cm. Includes index. ISBN 0-375-50578-4 1. Intellectual property. 2. Copyright and electronic data processing. 3. Internet—Law and legislation. 4. Information society. I. Title. K1401 .L47 2001 346.04'8'0285—dc21 2001031968 Random House website address: www.atrandom.com Printed in the United States of America on acid-free paper 24689753 First Edition Book design by Jo Anne Metsch less_0375505784_4p_fm_r1.qxd 9/21/01 13:49 Page v To Bettina, my teacher of the most important lesson.
  • OPENBSD HARDWARE SENSORS FRAMEWORK a Unified and Ready-To-Use System for Hassle-�Ee Hardware Monitoring

    OPENBSD HARDWARE SENSORS FRAMEWORK a Unified and Ready-To-Use System for Hassle-Ee Hardware Monitoring

    OPENBSD HARDWARE SENSORS FRAMEWORK A unified and ready-to-use system for hassle-ee hardware monitoring. Constantine A. Murenin and Raouf Boutaba University of Waterloo AsiaBSDCon 2009 — 12–15 March 2009 — Tokyo, Japan Abstract In this paper, we will discuss the origin, history, design guidelines, API and the device drivers of the hardware sensors framework available in OpenBSD. The framework spans multiple utilities in the base system and the ports tree, is utilised by over 70 drivers, and is considered to be a distinctive and ready-to-use feature that sets OpenBSD apart from many other operating systems, and in its root is inseparable from the OpenBSD experience. 1. Introduction Another trend that has been particularly common in the recent years is the availability of defined inter- We will start by investigating into the matter of what faces for software-based temperature readout from hardware monitoring sensors represent, how common individual components of personal computers, such as is it for them to appear in the general-purpose com- the CPU, or the add-on cards, such as those imple- puter hardware that has been available on the market menting the 802.11 wireless functionality or 10 Giga- in the last decade or so, and what benefits can we gain bit Ethernet. Popular examples include recent Intel by having a unified, simple and straightforward inter- Xeon and Core series of processors (as well as budget face for getting the data out of these sensors. models that are marketed under different brands) Although it may come as a surprise to some users, the [admtemp.4] [cpu.4]; all AMD64 processors from majority of personal computers that have been avail- AMD (Families 0Fh, 10h, 11h) [kate.4] [km.4]; Intel able on the market in the last decade have an inte- WiFi Link 4965/5100/5300 wireless network devices grated hardware monitoring circuitry whose main [iwn.4].
  • The Complete Freebsd

    The Complete Freebsd

    The Complete FreeBSD® If you find errors in this book, please report them to Greg Lehey <grog@Free- BSD.org> for inclusion in the errata list. The Complete FreeBSD® Fourth Edition Tenth anniversary version, 24 February 2006 Greg Lehey The Complete FreeBSD® by Greg Lehey <[email protected]> Copyright © 1996, 1997, 1999, 2002, 2003, 2006 by Greg Lehey. This book is licensed under the Creative Commons “Attribution-NonCommercial-ShareAlike 2.5” license. The full text is located at http://creativecommons.org/licenses/by-nc-sa/2.5/legalcode. You are free: • to copy, distribute, display, and perform the work • to make derivative works under the following conditions: • Attribution. You must attribute the work in the manner specified by the author or licensor. • Noncommercial. You may not use this work for commercial purposes. This clause is modified from the original by the provision: You may use this book for commercial purposes if you pay me the sum of USD 20 per copy printed (whether sold or not). You must also agree to allow inspection of printing records and other material necessary to confirm the royalty sums. The purpose of this clause is to make it attractive to negotiate sensible royalties before printing. • Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. • For any reuse or distribution, you must make clear to others the license terms of this work. • Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above.
  • Cryptanalysis of the Random Number Generator of the Windows Operating System

    Cryptanalysis of the Random Number Generator of the Windows Operating System

    Cryptanalysis of the Random Number Generator of the Windows Operating System Leo Dorrendorf School of Engineering and Computer Science The Hebrew University of Jerusalem 91904 Jerusalem, Israel [email protected] Zvi Gutterman Benny Pinkas¤ School of Engineering and Computer Science Department of Computer Science The Hebrew University of Jerusalem University of Haifa 91904 Jerusalem, Israel 31905 Haifa, Israel [email protected] [email protected] November 4, 2007 Abstract The pseudo-random number generator (PRNG) used by the Windows operating system is the most commonly used PRNG. The pseudo-randomness of the output of this generator is crucial for the security of almost any application running in Windows. Nevertheless, its exact algorithm was never published. We examined the binary code of a distribution of Windows 2000, which is still the second most popular operating system after Windows XP. (This investigation was done without any help from Microsoft.) We reconstructed, for the ¯rst time, the algorithm used by the pseudo- random number generator (namely, the function CryptGenRandom). We analyzed the security of the algorithm and found a non-trivial attack: given the internal state of the generator, the previous state can be computed in O(223) work (this is an attack on the forward-security of the generator, an O(1) attack on backward security is trivial). The attack on forward-security demonstrates that the design of the generator is flawed, since it is well known how to prevent such attacks. We also analyzed the way in which the generator is run by the operating system, and found that it ampli¯es the e®ect of the attacks: The generator is run in user mode rather than in kernel mode, and therefore it is easy to access its state even without administrator privileges.
  • The Internet Is a Semicommons

    The Internet Is a Semicommons

    GRIMMELMANN_10_04_29_APPROVED_PAGINATED 4/29/2010 11:26 PM THE INTERNET IS A SEMICOMMONS James Grimmelmann* I. INTRODUCTION As my contribution to this Symposium on David Post’s In Search of Jefferson’s Moose1 and Jonathan Zittrain’s The Future of the Internet,2 I’d like to take up a question with which both books are obsessed: what makes the Internet work? Post’s answer is that the Internet is uniquely Jeffersonian; it embodies a civic ideal of bottom-up democracy3 and an intellectual ideal of generous curiosity.4 Zittrain’s answer is that the Internet is uniquely generative; it enables its users to experiment with new uses and then share their innovations with each other.5 Both books tell a story about how the combination of individual freedom and a cooperative ethos have driven the Internet’s astonishing growth. In that spirit, I’d like to suggest a third reason that the Internet works: it gets the property boundaries right. Specifically, I see the Internet as a particularly striking example of what property theorist Henry Smith has named a semicommons.6 It mixes private property in individual computers and network links with a commons in the communications that flow * Associate Professor, New York Law School. My thanks for their comments to Jack Balkin, Shyam Balganesh, Aislinn Black, Anne Chen, Matt Haughey, Amy Kapczynski, David Krinsky, Jonathon Penney, Chris Riley, Henry Smith, Jessamyn West, and Steven Wu. I presented earlier versions of this essay at the Commons Theory Workshop for Young Scholars (Max Planck Institute for the Study of Collective Goods), the 2007 IP Scholars conference, the 2007 Telecommunications Policy Research Conference, and the December 2009 Symposium at Fordham Law School on David Post’s and Jonathan Zittrain’s books.
  • Kratka Povijest Unixa Od Unicsa Do Freebsda I Linuxa

    Kratka Povijest Unixa Od Unicsa Do Freebsda I Linuxa

    Kratka povijest UNIXa Od UNICSa do FreeBSDa i Linuxa 1 Autor: Hrvoje Horvat Naslov: Kratka povijest UNIXa - Od UNICSa do FreeBSDa i Linuxa Licenca i prava korištenja: Svi imaju pravo koristiti, mijenjati, kopirati i štampati (printati) knjigu, prema pravilima GNU GPL licence. Mjesto i godina izdavanja: Osijek, 2017 ISBN: 978-953-59438-0-8 (PDF-online) URL publikacije (PDF): https://www.opensource-osijek.org/knjige/Kratka povijest UNIXa - Od UNICSa do FreeBSDa i Linuxa.pdf ISBN: 978-953- 59438-1- 5 (HTML-online) DokuWiki URL (HTML): https://www.opensource-osijek.org/dokuwiki/wiki:knjige:kratka-povijest- unixa Verzija publikacije : 1.0 Nakalada : Vlastita naklada Uz pravo svakoga na vlastito štampanje (printanje), prema pravilima GNU GPL licence. Ova knjiga je napisana unutar inicijative Open Source Osijek: https://www.opensource-osijek.org Inicijativa Open Source Osijek je član udruge Osijek Software City: http://softwarecity.hr/ UNIX je registrirano i zaštićeno ime od strane tvrtke X/Open (Open Group). FreeBSD i FreeBSD logo su registrirani i zaštićeni od strane FreeBSD Foundation. Imena i logo : Apple, Mac, Macintosh, iOS i Mac OS su registrirani i zaštićeni od strane tvrtke Apple Computer. Ime i logo IBM i AIX su registrirani i zaštićeni od strane tvrtke International Business Machines Corporation. IEEE, POSIX i 802 registrirani i zaštićeni od strane instituta Institute of Electrical and Electronics Engineers. Ime Linux je registrirano i zaštićeno od strane Linusa Torvaldsa u Sjedinjenim Američkim Državama. Ime i logo : Sun, Sun Microsystems, SunOS, Solaris i Java su registrirani i zaštićeni od strane tvrtke Sun Microsystems, sada u vlasništvu tvrtke Oracle. Ime i logo Oracle su u vlasništvu tvrtke Oracle.
  • BSD Projects IV – BSD Certification • Main Features • Community • Future Directions a (Very) Brief History of BSD

    BSD Projects IV – BSD Certification • Main Features • Community • Future Directions a (Very) Brief History of BSD

    BSD Overview Jim Brown May 24, 2012 BSD Overview - 5/24/2012 - Jim Brown, ISD BSD Overview I – A Brief History of BSD III – Cool Hot Stuff • ATT UCB Partnership • Batteries Included • ATT(USL) Lawsuit • ZFS , Hammer • BSD Family Tree • pf Firewall, pfSense • BSD License • Capsicum • Virtualization Topics • Jails, Xen, etc. • Desktop PC-BSD II – The Core BSD Projects IV – BSD Certification • Main Features • Community • Future Directions A (Very) Brief History of BSD 1971 – ATT cheaply licenses Unix source code to many organizations, including UCB as educational material 1975 – Ken Thompson takes a sabbatical from ATT, brings the latest Unix source on tape to UCB his alma mater to run on a PDP 11 which UCB provided. (Industry/academic partnerships were much more common back then.) Computer Science students (notably Bill Joy and Chuck Haley) at UCB begin to make numerous improvements to Unix and make them available on tape as the “Berkeley Software Distribution” - BSD A (Very) Brief History of BSD Some notable CSRG • 1980 – Computer Science Research Group members (CSRG) forms at UCB with DARPA funding to make many more improvements to Unix - job control, autoreboot, fast filesystem, gigabit address space, Lisp, IPC, sockets, TCP/IP stack + applications, r* utils, machine independence, rewriting almost all ATT code with UCB/CSRG code, including many ports • 1991 – The Networking Release 2 tape is released on the Internet via anon FTP. A 386 port quickly follows by Bill and Lynne Jolitz. The NetBSD group is formed- the first Open Source community entirely on the Internet • 1992 – A commercial version, BSDI (sold for $995, 1-800-ITS-UNIX) draws the ire of USL/ATT.
  • IOMMU-Resistant DMA Attacks

    IOMMU-Resistant DMA Attacks

    IOMMU-resistant DMA attacks Gil Kupfer Technion - Computer Science Department - M.Sc. Thesis MSC-2018-21 - 2018 Technion - Computer Science Department - M.Sc. Thesis MSC-2018-21 - 2018 IOMMU-resistant DMA attacks Research Thesis Submitted in partial fulfillment of the requirements for the degree of Master of Science in Computer Science Gil Kupfer Submitted to the Senate of the Technion | Israel Institute of Technology Sivan 5778 Haifa May 2018 Technion - Computer Science Department - M.Sc. Thesis MSC-2018-21 - 2018 Technion - Computer Science Department - M.Sc. Thesis MSC-2018-21 - 2018 This research was carried out under the supervision of Prof. Dan Tsafrir and Dr. Nadav Amit, in the Faculty of Computer Science. Acknowledgements who passed ,ז"ל This work is dedicated to my grandfather, Tuvia Kupfer away during the writing of this work. I would like to thank my wife, Odeya, for helping and supporting when needed. Also, I would like to thank all the friends who have been there. Finally, thanks to my advisors, Prof. Dan Tsafrir and Dr. Nadav Amit, for their help and guidance along the way. The generous financial help of the Technion is gratefully acknowledged. Technion - Computer Science Department - M.Sc. Thesis MSC-2018-21 - 2018 Technion - Computer Science Department - M.Sc. Thesis MSC-2018-21 - 2018 Contents List of Figures Abstract 1 Abbreviations and Notations3 1 Introduction5 2 Background9 2.1 DMA Attacks.................................9 2.1.1 Classic DMA Attacks........................9 2.1.2 IOMMU Protection......................... 10 2.1.3 Circumventing the IOMMU..................... 11 2.2 FireWire.................................... 12 3 Attack Mechanics 15 3.1 Sub-Page Granularity Vulnerability....................
  • Free As in Freedom (2.0): Richard Stallman and the Free Software Revolution

    Free As in Freedom (2.0): Richard Stallman and the Free Software Revolution

    Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution Sam Williams Second edition revisions by Richard M. Stallman i This is Free as in Freedom 2.0: Richard Stallman and the Free Soft- ware Revolution, a revision of Free as in Freedom: Richard Stallman's Crusade for Free Software. Copyright c 2002, 2010 Sam Williams Copyright c 2010 Richard M. Stallman Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License." Published by the Free Software Foundation 51 Franklin St., Fifth Floor Boston, MA 02110-1335 USA ISBN: 9780983159216 The cover photograph of Richard Stallman is by Peter Hinely. The PDP-10 photograph in Chapter 7 is by Rodney Brooks. The photo- graph of St. IGNUcius in Chapter 8 is by Stian Eikeland. Contents Foreword by Richard M. Stallmanv Preface by Sam Williams vii 1 For Want of a Printer1 2 2001: A Hacker's Odyssey 13 3 A Portrait of the Hacker as a Young Man 25 4 Impeach God 37 5 Puddle of Freedom 59 6 The Emacs Commune 77 7 A Stark Moral Choice 89 8 St. Ignucius 109 9 The GNU General Public License 123 10 GNU/Linux 145 iii iv CONTENTS 11 Open Source 159 12 A Brief Journey through Hacker Hell 175 13 Continuing the Fight 181 Epilogue from Sam Williams: Crushing Loneliness 193 Appendix A { Hack, Hackers, and Hacking 209 Appendix B { GNU Free Documentation License 217 Foreword by Richard M.
  • BSD Professional Certification Job Task Analysis Survey Results

    BSD Professional Certification Job Task Analysis Survey Results

    BSD Professional Certification Job Task Analysis Survey Results March 21, 2010 BSD Professional Job Task Analysis Survey Results 2 Copyright © 2010 BSD Certification Group All Rights Reserved All trademarks are owned by their respective companies. This work is protected by a Creative Commons License which requires attribution and prevents commercial and derivative works. The human friendly version of the license can be viewed at http://creativecommons.org/licenses/by-nc-nd/3.0/ which also provides a hyperlink to the legal code. These conditions can only be waived by written permission from the BSD Certification Group. See the website for contact details. BSD Daemon Copyright 1988 by Marshall Kirk McKusick. All Rights Reserved. Puffy Artwork Copyright© 2004 by OpenBSD. FreeBSD® is a registered trademark of The FreeBSD Foundation, Inc. NetBSD® is a registered trademark of The NetBSD Foundation, Inc. The NetBSD Logo Copyright© 2004 by The NetBSD Foundation, Inc. Fred Artwork Copyright© 2005 by DragonFly BSD. Use of the above names, trademarks, logos, and artwork does not imply endorsement of this certification program by their respective owners. www.bsdcertification.org BSD Professional Job Task Analysis Survey Results 3 Table of Contents Executive Summary ................................................................................................................................... 9 Introduction .............................................................................................................................................