DOCSLIB.ORG

Contributeurs Au Projet Freebsd Version: 43184 2013-11-13 Par Hrs

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Contributeurs Au Projet Freebsd Version: 43184 2013-11-13 Par Hrs Contributeurs au projet FreeBSD Version: 43184 2013-11-13 par hrs. Résumé Cet article liste les organisations et les personnes ayant contribué à FreeBSD. Table des matières 1. Gallerie des dons ..................................................................................................................... 1 2. Le bureau dirigeant .................................................................................................................. 3 3. Les développeurs FreeBSD .......................................................................................................... 3 4. Le projet de documentation de FreeBSD ...................................................................................... 14 5. Qui est reponsable de quoi ....................................................................................................... 15 6. Liste des anciens de la "Core Team" ........................................................................................... 16 7. Liste des anciens développeurs .................................................................................................. 17 8. Liste des logiciels contribués ..................................................................................................... 18 9. Contributeurs additionnels à FreeBSD ......................................................................................... 18 10. Contributeurs du kit de patch 386BSD ....................................................................................... 58 Index ...................................................................................................................................... 61 1. Gallerie des dons Le projet FreeBSD Project est redevable à ces donneurs et veut les remercier publiquement ici! • Contributeurs au serveur central du projet: Les personnes et sociétés suivantes ont fait qu'il a été possible au projet FreeBSD de mettre en place un nouveau serveur central, qui a remplacé freefall.FreeBSD.org, grace aux dons suivants: • Ade Barkah et son employeur, Hemisphere Online, ont fournis un Pentium Pro (P6) 200MHz CPU • ASA Computers a fourni un carte mere Tyan 1662 . • Joe McGuckin <[email protected] > de ViaNet Communications a fourni une carte Ethernet Kingston. • Jack O'Neill <[email protected]> a fourni une carte NCR 53C875 SCSI. • Ulf Zimmermann <[email protected]> de Alameda Networks a fourni 128MB de mémoire, et un disque de 4 Gb. • Dons en numéraires: Les personnes et entreprises suivantes ont directement donnés des fonds au projet: • Annelise Anderson <[email protected]> • Matthew Dillon • Blue Mountain Arts • Epilogue Technology Corporation • Sean Eric Fagan Gallerie des dons • Global Technology Associates, Inc • Don Scott Wilde • Gianmarco Giovannelli <[email protected]> • Josef C. Grosch <[email protected]> • Robert T. Morris • Chuck Robey • Kenneth P. Stox <[email protected]> de Imaginary Landscape, LLC. • Dmitry S. Kohmanyuk <[email protected] > • Laser5 du Japon (une partie des bénéfices de leur ventes des CDROMs de FreeBSD). • Fuki Shuppan Publishing Co. a donné une partie des bénéfices du livre Hajimete no FreeBSD (FreeBSD, Getting started) à FreeBSD et au projet XFree86. • ASCII Corp. a donné une partie des bénéfices de la vente de certains livres en rapport avec FreeBSD. • Yokogawa Electric Corp a généreusement donné une somme significative au projet FreeBSD. • BuffNET • Pacific Solutions • Siemens AG via Andre Albsmeier <[email protected]> • Chris Silva <[email protected]> • Contributeurs matériels Les personnes et sociétés suivantes ont généreusement contribués en fournissant du matériel pour les tests et le développement des gestionnaires de périphériques: • BSDi a fourni les systèmes Pentium P5-90 et 486/DX2-66 EISA/VL qui sont utilisés pour notre développement. • Compaq a fourni 3 AlphaStation DS10s au projet FreeBSD. Parmi ces dons, il y a 4 AlphaStations DS10s, un AlphaServer DS20, un AlphaServer 2100s, un AlphaServer 4100, 8 stations personnelles 500Mhz, 4 stations personnelles 433Mhz ! Ces machines sont actuellement utilisés pour la gestion de la chaine de version et les développements de la plateforme FreeBSD/Alpha. • TRW Financial Systems, Inc. a fourni 130 PCs, trois serveurs de fichiers de 68 GB, douze Ethernets, deux rou- teurs et un switch ATM pour débogguer le code ddiskless. • Dermot McDonnell a fourni le CDROM Toshiba XM3401B utilisé actuellement sur freefall. • Chuck Robey <[email protected]> a fourni son lecteur de bande pour les tests. • Larry Altneu <[email protected]>, et Wilko Bulte, ont fournis les lecteurs de bandes Wangtek et Archive QIC-02 pour améliorer les gestionnaires de périphériques wt. • Ernst Winter <[email protected]> a fourni le lecteur de disquette de 2.88 MB. Cela permettra de ré-écrire le gestionnaire de disquette pour le supporter. • Tekram Technologies a fourni les cartes DC-390, DC-390U ,DC-390F FAST et ULTRA SCSI pour les tests de non- régression des gestionnaires de périphérique NCR et AMD. Nous les remercions aussi pour la mise à disposi- 2 Contributeurs au projet FreeBSD tion des sources des gestionnaires pour les systèmes d'exploitations libres sur leur serveur FTP ftp://ftp.te- kram.com/scsi/FreeBSD/. • Larry M. Augustin a fourni en plus de la carte Symbios Sym8751S SCSI, un ensemble de livres dont, un livre sur le support des composants Sym53c895, Ultra-2 et LVD, ainsi qu'un livre sur la programmation des fonctions avancées des composants SCSI Symbios. • Christoph Kukulies <[email protected]> a fourni un CDROM 12x, FX120 Mitsumi, pour le développement du gestionnaire de périphériques des CDROM IDE. • Mike Tancsa <[email protected]> a fourni quatre différentes cartes PCI ATM, pour nous aider a améliorer le support de ces cartes et de la pile ATM netatm. • Contributeurs spéciaux: • BSDi (encore connu sous Walnut Creek CDROM) a fourni plus que ce que nous pourrions dire (voyez l'his- torique dans le Manuel FreeBSD pour plus de détails). En particulier, nous aimerions les remercier pour le matériel originel utilisé surfreefall.FreeBSD.org, notre machine de développement principal et pour thud.FreeBSD.org , la machine de test et de compilation. Nous voulons aussi les remercier pour l'ensemble de leurs dons et contributions depuis des années et la fourniture de la connection T1 à l'Internet. • La société Interface business GmbH, Dresden a patiemment supporté Jörg Wunsch qui a préfére son travail sur FreeBSD, et utilisé la connexion (tres chère) internet EUnet lorsque sa connexion privé devint trop lente pour travailler avec... • Berkeley Software Design, Inc. a fourni le code d'émulation DOS au monde BSD, qui est utilisé dans la com- mande doscmd. 2. Le bureau dirigeant Le bureau dirigeant de FreeBSD (core team) constitue le « Comité dirigeant » du projet, responsable des décisions sur le projet, telles que les buts à atteindre tout comme la gestion de certaines portions du projet FreeBSD (par ordre alphabétique et trié par nom de famille): • John Baldwin • Jun Kuriyama • Greg Lehey • Warner Losh • Mark Murray • Wes Peters • Murray Stokely • Robert Watson • Peter Wemm 3. Les développeurs FreeBSD Ce sont des personnes disposant du privilège d'écriture dans l'arboresence des sources. Tous les membres du bu- reau dirigeant sont aussi développeurs. 3 Les développeurs FreeBSD (par ordre alphabétique et trié par nom de famille): • Shunsuke Akiyama • Jose M. Alcaide • Doug Ambrisko • Will Andrews • Eric Anholt • Ugen J.S. Antsilevich • Toshihiko Arai • Sergey Babkin • Daniel Baker • John Baldwin • Duncan Barclay • Mike Barcroft • Ade Barkah • Robert V. Baron • Doug Barton • Anton Berezin • Stefan Bethke • Pierre Beyssac • Andrzej Bialecki • John Birrell • Neil Blakey-Milner • Martin Blapp • Torsten Blum • Maxim Bolotin • Oliver Braun • Jonathan M. Bresler • Wilko Bulte • Jake Burkholder • Donald Burr • Adrian Chadd 4 Contributeurs au projet FreeBSD • Hye-Shik Chang • David W. Chapman Jr. • Philippe Charnier • Jonathan Chen • Luoqi Chen • Andrey A. Chernov • Eric J. Chet • Sean Chittenden • Kenjiro Cho • Junho CHOI • Crist J. Clark • Joe Marcus Clarke • Nik Clayton • Archie Cobbs • Chris Costello • Alan L. Cox • Martin Cracauer • David E. Cross • Peter da Silva • Adam David • Chad David • Ceri Davies • Brooks Davis • Brian S. Dean • John W. DeBoskey • Prafulla S. Deuskar • Matthew Dillon • Matthew N. Dodd • Dima Dorfman • Ian Dowse • Robert Drehmel 5 Les développeurs FreeBSD • Garance A Drosehn • Peter Dufault • Frank Durda IV • Tor Egge • Daniel Eischen • Eivind Eklund • Alan Eldridge • Julian Elischer • Ralf S. Engelschall • Udo Erdelhoff • Ruslan Ermilov • Stefan Eßer • Bruce Evans • Jason Evans • Sean Eric Fagan • Chris D. Faulhaber • Brian F. Feldman • Bill Fenner • Mário Sérgio Fujikawa Ferreira • John Fieber • Tony Finch • James FitzGibbon • Marc Fonvieille • Marc G. Fournier • Lars Fredriksen • Pete Fritchman • Dirk Frömberg • Satsuki FUJISHIMA • Shigeyuki Fukushima • Bill Fumerola • Atsushi Furuta 6 Contributeurs au projet FreeBSD • Andrew Gallatin • Patrick S. Gardella • Thomas Gellekum • Justin T. Gibbs • Brandon Gillespie • Sebastien Gioria • Daichi GOTO • Cameron Grant • Rodney Grimes • Edwin Groothuis • John-Mark Gurney • Ernst de Haan • Hiroyuki HANAI • Roger Hardiman • Michael Haro • Daniel Harris • Peter Hawkins • John Hay • Sheldon Hearn • Mike Heffner • Martin Heinen • Wolfgang Helbig • Guy Helmer • Maxime Henrion • Eric L. Hernes • Christopher Shumway • Christoph Herrmann • Nick Hibma • Seiichirou Hiraoka • Orion Hodson • Peter Holm 7 Les développeurs
Load more

Recommended publications
  • BSD – Alternativen Zu Linux
    ∗BSD { Alternativen zu Linux Karl Lockhoff March 19, 2015 Inhaltsverzeichnis I Woher kommt BSD? I Was ist BSD? I Was ist sind die Unterschiede zwischen FreeBSD, NetBSD und OpenBSD? I Warum soll ich *BSD statt Linux einsetzen? I Chuck Haley und Bill Joy entwickeln den vi in Berkeley I Bill Joy erstellt eine Sammlung von Tools, 1BSD I Unix Version 7 erscheint I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I 1978 I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I Bill Joy erstellt eine Sammlung von Tools, 1BSD I Unix Version 7 erscheint I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 1978 I Chuck Haley und Bill Joy entwickeln den vi in Berkeley I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I Unix Version 7 erscheint I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 1978 I Chuck Haley und Bill Joy entwickeln den
    [Show full text]
  • 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
    [Show full text]
  • Ebook - Informations About Operating Systems Version: August 15, 2006 | Download
    eBook - Informations about Operating Systems Version: August 15, 2006 | Download: www.operating-system.org AIX Internet: AIX AmigaOS Internet: AmigaOS AtheOS Internet: AtheOS BeIA Internet: BeIA BeOS Internet: BeOS BSDi Internet: BSDi CP/M Internet: CP/M Darwin Internet: Darwin EPOC Internet: EPOC FreeBSD Internet: FreeBSD HP-UX Internet: HP-UX Hurd Internet: Hurd Inferno Internet: Inferno IRIX Internet: IRIX JavaOS Internet: JavaOS LFS Internet: LFS Linspire Internet: Linspire Linux Internet: Linux MacOS Internet: MacOS Minix Internet: Minix MorphOS Internet: MorphOS MS-DOS Internet: MS-DOS MVS Internet: MVS NetBSD Internet: NetBSD NetWare Internet: NetWare Newdeal Internet: Newdeal NEXTSTEP Internet: NEXTSTEP OpenBSD Internet: OpenBSD OS/2 Internet: OS/2 Further operating systems Internet: Further operating systems PalmOS Internet: PalmOS Plan9 Internet: Plan9 QNX Internet: QNX RiscOS Internet: RiscOS Solaris Internet: Solaris SuSE Linux Internet: SuSE Linux Unicos Internet: Unicos Unix Internet: Unix Unixware Internet: Unixware Windows 2000 Internet: Windows 2000 Windows 3.11 Internet: Windows 3.11 Windows 95 Internet: Windows 95 Windows 98 Internet: Windows 98 Windows CE Internet: Windows CE Windows Family Internet: Windows Family Windows ME Internet: Windows ME Seite 1 von 138 eBook - Informations about Operating Systems Version: August 15, 2006 | Download: www.operating-system.org Windows NT 3.1 Internet: Windows NT 3.1 Windows NT 4.0 Internet: Windows NT 4.0 Windows Server 2003 Internet: Windows Server 2003 Windows Vista Internet: Windows Vista Windows XP Internet: Windows XP Apple - Company Internet: Apple - Company AT&T - Company Internet: AT&T - Company Be Inc. - Company Internet: Be Inc. - Company BSD Family Internet: BSD Family Cray Inc.
    [Show full text]
  • Twenty Years of Berkeley Unix : from AT&T-Owned to Freely
    Twenty Years of Berkeley Unix : From AT&T-Owned to Freely Redistributable Marshall Kirk McKusick Early History Ken Thompson and Dennis Ritchie presented the first Unix paper at the Symposium on Operating Systems Principles at Purdue University in November 1973. Professor Bob Fabry, of the University of California at Berkeley, was in attendance and immediately became interested in obtaining a copy of the system to experiment with at Berkeley. At the time, Berkeley had only large mainframe computer systems doing batch processing, so the first order of business was to get a PDP-11/45 suitable for running with the then-current Version 4 of Unix. The Computer Science Department at Berkeley, together with the Mathematics Department and the Statistics Department, were able to jointly purchase a PDP-11/45. In January 1974, a Version 4 tape was delivered and Unix was installed by graduate student Keith Standiford. Although Ken Thompson at Purdue was not involved in the installation at Berkeley as he had been for most systems up to that time, his expertise was soon needed to determine the cause of several strange system crashes. Because Berkeley had only a 300-baud acoustic-coupled modem without auto answer capability, Thompson would call Standiford in the machine room and have him insert the phone into the modem; in this way Thompson was able to remotely debug crash dumps from New Jersey. Many of the crashes were caused by the disk controller's inability to reliably do overlapped seeks, contrary to the documentation. Berkeley's 11/45 was among the first systems that Thompson had encountered that had two disks on the same controller! Thompson's remote debugging was the first example of the cooperation that sprang up between Berkeley and Bell Labs.
    [Show full text]
  • Advanced Integration
    ZFS: Advanced Integration Allan Jude -- [email protected] @allanjude Introduction: Allan Jude • 16 Years as FreeBSD Server Admin • FreeBSD src/doc committer (ZFS, installer, boot loader, GELI, bhyve, libucl, libxo) • FreeBSD Core Team (July 2016 - 2018) • Co-Author of “FreeBSD Mastery: ZFS” and “FreeBSD Mastery: Advanced ZFS” with Michael W. Lucas • Architect of the ScaleEngine CDN (HTTP and Video) • Host of weekly BSDNow.tv Podcast • Personally Responsible for 1000 TB of ZFS Storage ZFS: What Is It? • ZFS is a filesystem with a built in volume manager (combine multiple disks into a pool) • Space from the pool is thin-provisioned to multiple filesystems or block volumes (zvols) • All data and metadata is checksummed • Optional transparent compression • Copy-on-Write with snapshots and clones • Each filesystem is tunable with properties Snapshots and Clones • Copy-on-Write means snapshots are instant • Blocks referenced by a snapshot kept when they are removed from the live filesystem • Snapshots allows you to access the file- system as it was when snapshot was taken • No performance impact on reads/writes • Take no additional space until blocks change • Clones allow you to “fork” a filesystem Boot Environments • If the root filesystem is on ZFS, you can snapshot before an upgrade, then clone it • You now have 2 filesystems, one before the upgrade, and one after. Only takes the space of blocks that changed • FreeBSD boot loader allows you to select which one to use from a menu • Upgrade without fear, can always rollback Boot Environment Tooling • Existing tool: sysadmin/beadm • GSoC 2017: be(8) and libbe(3) • New tool supports better management of filesystem properties for boot integration • New tool will support “deep” boot environments.
    [Show full text]
  • The Release Engineering of Freebsd 4.4
    The Release Engineering of FreeBSD 4.4 Murray Stokely [email protected] Wind River Systems Abstract different pace, and with the general assumption that they This paper describes the approach used by the FreeBSD re- have first gone into FreeBSD-CURRENT and have been lease engineering team to make production-quality releases thoroughly tested by our user community. of the FreeBSD operating system. It details the methodol- In the interim period between releases, nightly snap- ogy used for the release of FreeBSD 4.4 and describes the shots are built automatically by the FreeBSD Project build tools available for those interested in producing customized machines and made available for download from ftp: FreeBSD releases for corporate rollouts or commercial pro- //stable.FreeBSD.org. The widespread availabil- ductization. ity of binary release snapshots, and the tendency of our user community to keep up with -STABLE development with CVSup and “make world”[8] helps to keep FreeBSD- 1 Introduction STABLE in a very reliable condition even before the qual- ity assurance activities ramp up pending a major release. The development of FreeBSD is a very open process. Bug reports and feature requests are continuously sub- FreeBSD is comprised of contributions from thousands of mitted by users throughout the release cycle. Problem people around the world. The FreeBSD Project provides reports are entered into our GNATS[9] database through anonymous CVS[1] access to the general public so that email, the send-pr(1) application, or via a web-based form. others can have access to log messages, diffs between de- In addition to the multitude of different technical mailing velopment branches, and other productivity enhancements lists about FreeBSD, the FreeBSD quality-assurance mail- that formal source code management provides.
    [Show full text]
  • 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].
    [Show full text]
  • Sun Storagetek 5320 NAS Appliance and Gateway Administration Guide
    Sun StorageTek™ 5320 NAS Appliance and Gateway Administration Guide NAS Software Version 4.12 Sun Microsystems, Inc. www.sun.com Part No. 819-6388-10 May 2006, Revision A Submit comments about this document at: http://www.sun.com/hwdocs/feedback Copyright 2006 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries. This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, Java, AnswerBook2, docs.sun.com, Sun StorEdge, Sun StorageTek, Java, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and in other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • Freebsd Handbook
    FreeBSD Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/han... FreeBSD Handbook The FreeBSD Documentation Project Copyright © 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013 The FreeBSD Documentation Project Welcome to FreeBSD! This handbook covers the installation and day to day use of FreeBSD 8.3-RELEASE and FreeBSD 9.1-RELEASE. This manual is a work in progress and is the work of many individuals. As such, some sections may become dated and require updating. If you are interested in helping out with this project, send email to the FreeBSD documentation project mailing list. The latest version of this document is always available from the FreeBSD web site (previous versions of this handbook can be obtained from http://docs.FreeBSD.org/doc/). It may also be downloaded in a variety of formats and compression options from the FreeBSD FTP server or one of the numerous mirror sites. If you would prefer to have a hard copy of the handbook, you can purchase one at the FreeBSD Mall. You may also want to search the handbook. REDISTRIBUTION AND USE IN SOURCE (XML DOCBOOK) AND 'COMPILED' FORMS (XML, HTML, PDF, POSTSCRIPT, RTF AND SO FORTH) WITH OR WITHOUT MODIFICATION, ARE PERMITTED PROVIDED THAT THE FOLLOWING CONDITIONS ARE MET: 1. REDISTRIBUTIONS OF SOURCE CODE (XML DOCBOOK) MUST RETAIN THE ABOVE COPYRIGHT NOTICE, THIS LIST OF CONDITIONS AND THE FOLLOWING DISCLAIMER AS THE FIRST LINES OF THIS FILE UNMODIFIED. 2. REDISTRIBUTIONS IN COMPILED FORM (TRANSFORMED TO OTHER DTDS, CONVERTED TO PDF, POSTSCRIPT, RTF AND OTHER FORMATS) MUST REPRODUCE THE ABOVE COPYRIGHT NOTICE, THIS LIST OF CONDITIONS AND THE FOLLOWING DISCLAIMER IN THE DOCUMENTATION AND/OR OTHER MATERIALS PROVIDED WITH THE DISTRIBUTION.
    [Show full text]
  • Tuesday October 20: a Guide to Event-Driven SRE-Inspired Devops 16:55 GMT-3 / 15:55 GMT -4 / 14:55 GMT -5 / 12:55 GMT -7
    Buenos Aires, Arg.: GMT -3, ART New York, USA., Toronto and Montreal, Ca.: EDT, GMT -4 Texas, USA., Winnipeg, Ca.: CDT, GMT -5 California, USA., Vancouver, Ca: PDT, GMT -7 Twitter: @nerdearla Website: https://nerdear.la/en/ ​ Schedule (in spanish with Argentine GMT -3 timezone): https://nerdear.la/agenda/ ​ How to register? See at the end of this document for a step by step guide. Tuesday October 20: A Guide to Event-driven SRE-inspired DevOps 16:55 GMT-3 / 15:55 GMT -4 / 14:55 GMT -5 / 12:55 GMT -7 We have broken our monoliths into event-driven microservice architectures! Yet, many of us are still using old monolithic pipeline approaches to delivery & operations. Let me show you a modern open source event-driven approach to delivery & operations with the safety net of SRE! By Andreas Grabner — DevOps Activist FreeBSD: Code, Community and Collaboration 17:55 GMT-3 / 16:55 GMT -4 / 15:55 GMT -5 / 13:55 GMT -7 The FreeBSD Open Source Operating System is one of the oldest, largest, and most successful open source projects, with a long history of innovation. FreeBSD descended from Berkeley Unix back in the early ’90s, with its lineage dating back 50 years to the original UNIX. It’s known for its reliability, stability, and advanced networking and performance. Deb will take you through its long history and highlight some of the features that set FreeBSD apart from other operating systems. She’ll describe how the FreeBSD Project works and how you can contribute to the Project. She will point out some of the differences between FreeBSD and Linux, and share why individuals and companies use FreeBSD.
    [Show full text]