La Promotion Du Web Ouvert a Bien Changé Mais Mozilla Est Toujours Là
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Communications Cacm.Acm.Org of Theacm 06/2009 Vol.52 No.06
COMMUNICATIONS CACM.ACM.ORG OF THEACM 06/2009 VOL.52 NO.06 One Laptop Per Child: Vision vs. Reality Hard-Disk Drives: The Good, The Bad, and the Ugly How CS Serves The Developing World Network Front-End Processors The Claremont Report On Database Research Autonomous Helicopters Association for Computing Machinery Think Parallel..... It’s not just what we make. It’s what we make possible. Advancing Technology Curriculum Driving Software Evolution Fostering Tomorrow’s Innovators Learn more at: www.intel.com/thinkparallel ACM Ad.indd 1 4/17/2009 11:20:03 AM ABCD springer.com Noteworthy Computer Science Journals Autonomous Biological Personal and Robots Cybernetics Ubiquitous G. Sukhatme, University W. Senn, Universität Bern, Computing of Southern California, Physiologisches Institut; ACM Viterbi School of Engi- J. Rinzel, National neering, Dept. Computer Institutes of Health (NIH), P. Thomas, Univ. Coll. Science Dept. Health Education & London Interaction Centre Autonomous Robots Welfare; J. L. van Hemmen, reports on the theory and TU München, Abt. Physik Personal and Ubiquitous applications of robotic systems capable of Biological Cybernetics is an interdisciplinary Computing publishes peer-reviewed some degree of self-sufficiency. It features medium for experimental, theoretical and international research on handheld, wearable papers that include performance data on actual application-oriented aspects of information and mobile information devices and the robots in the real world. The focus is on the processing in organisms, including sensory, pervasive communications infrastructure that ability to move and be self-sufficient, not on motor, cognitive, and ecological phenomena. supports them to enable the seamless whether the system is an imitation of biology. -
Introducing HTML5.Pdf
ptg HTMLINTRODUCING 5 ptg BRUCE LAWSON REMY SHARP Introducing HTML5 Bruce Lawson and Remy Sharp New Riders 1249 Eighth Street Berkeley, CA 94710 510/524-2178 510/524-2221 (fax) Find us on the Web at: www.newriders.com To report errors, please send a note to [email protected] New Riders is an imprint of Peachpit, a division of Pearson Education Copyright © 2011 by Remy Sharp and Bruce Lawson Project Editor: Michael J. Nolan Development Editor: Jeff Riley/Box Twelve Communications Technical Editors: Patrick H. Lauke (www.splintered.co.uk), Robert Nyman (www.robertnyman.com) Production Editor: Cory Borman Copyeditor: Doug Adrianson Proofreader: Darren Meiss Compositor: Danielle Foster Indexer: Joy Dean Lee Back cover author photo: Patrick H. Lauke Notice of Rights ptg All rights reserved. No part of this book may be reproduced or transmitted in any form by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. For informa- tion on getting permission for reprints and excerpts, contact permissions@ peachpit.com. Notice of Liability The information in this book is distributed on an “As Is” basis without war- ranty. While every precaution has been taken in the preparation of the book, neither the authors nor Peachpit shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the instructions contained in this book or by the com- puter software and hardware products described in it. Trademarks Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. -
0321687299.Pdf
Introducing HTML5 Bruce Lawson and Remy Sharp New Riders 1249 Eighth Street Berkeley, CA 94710 510/524-2178 510/524-2221 (fax) Find us on the Web at: www.newriders.com To report errors, please send a note to [email protected] New Riders is an imprint of Peachpit, a division of Pearson Education Copyright © 2011 by Remy Sharp and Bruce Lawson Project Editor: Michael J. Nolan Development Editor: Jeff Riley/Box Twelve Communications Technical Editors: Patrick H. Lauke (www.splintered.co.uk), Robert Nyman (www.robertnyman.com) Production Editor: Cory Borman Copyeditor: Doug Adrianson Proofreader: Darren Meiss Compositor: Danielle Foster Indexer: Joy Dean Lee Back cover author photo: Patrick H. Lauke Notice of Rights All rights reserved. No part of this book may be reproduced or transmitted in any form by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. For informa- tion on getting permission for reprints and excerpts, contact permissions@ peachpit.com. Notice of Liability The information in this book is distributed on an “As Is” basis without war- ranty. While every precaution has been taken in the preparation of the book, neither the authors nor Peachpit shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the instructions contained in this book or by the com- puter software and hardware products described in it. Trademarks Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and Peachpit was aware of a trademark claim, the designa- tions appear as requested by the owner of the trademark. -
Securing Frame Communication in Browsers by Adam Barth, Collin Jackson, and John C
DOI:10.1145/1516046.1516066 Securing Frame Communication in Browsers By Adam Barth, Collin Jackson, and John C. Mitchell Abstract map, or a photo album, the site runs the risk of incorporat- Many Web sites embed third-party content in frames, ing malicious content. Without isolation, malicious content relying on the browser’s security policy to protect against can compromise the confidentiality and integrity of the malicious content. However, frames provide insufficient user’s session with the integrator. Although the browser’s isolation in browsers that let framed content navigate well-known “same-origin policy”19 restricts script running other frames. We evaluate existing frame navigation poli- in one frame from manipulating content in another frame, cies and advocate a stricter policy, which we deploy in the browsers use a different policy to determine whether one open-source browsers. In addition to preventing undesir- frame is allowed to navigate (change the location of) another. able interactions, the browser’s strict isolation policy also Although browsers must restrict navigation to provide isola- affects communication between cooperating frames. We tion, navigation is the basis of one form of interframe com- therefore analyze two techniques for interframe communi- munication used by leading companies and navigation cation between isolated frames. The first method, fragment can be used to attack a second interframe communication identifier messaging, initially provides confidentiality with- mechanism. out authentication, which we repair using concepts from a Many recent browsers have overly permissive frame well-known network protocol. The second method, post- navigation policies that lead to a variety of attacks. To pre- Message, initially provides authentication, but we dis- vent attacks, we demonstrate against the Google AdSense cover an attack that breaches confidentiality. -
Introducing HTML5 Second Edition
HTMLINTRODUCING SECOND 5EDITION BRUCE LAWSON REMY SHARP Introducing HTML5, Second Edition Bruce Lawson and Remy Sharp New Riders 1249 Eighth Street Berkeley, CA 94710 510/524-2178 510/524-2221 (fax) Find us on the Web at: www.newriders.com To report errors, please send a note to [email protected] New Riders is an imprint of Peachpit, a division of Pearson Education Copyright © 2012 by Remy Sharp and Bruce Lawson Project Editor: Michael J. Nolan Development Editor: Margaret S. Anderson/Stellarvisions Technical Editors: Patrick H. Lauke (www.splintered.co.uk), Robert Nyman (www.robertnyman.com) Production Editor: Cory Borman Copyeditor: Gretchen Dykstra Proofreader: Jan Seymour Indexer: Joy Dean Lee Compositor: Danielle Foster Cover Designer: Aren Howell Straiger Cover photo: Patrick H. Lauke (splintered.co.uk) Notice of Rights All rights reserved. No part of this book may be reproduced or transmitted in any form by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. For informa- tion on getting permission for reprints and excerpts, contact permissions@ peachpit.com. Notice of Liability The information in this book is distributed on an “As Is” basis without war- ranty. While every precaution has been taken in the preparation of the book, neither the authors nor Peachpit shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the instructions contained in this book or by the com- puter software and hardware products described in it. Trademarks Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. -
Open Source Software Seminar — Konstantin Käfer Webkit
WebKit Bug #17229 Konstantin Käfer 1 Open Source SoftwareOpen Seminar Source — Software Konstantin Seminar Käfer Outline ‣ Project Structure and Goals ‣ History ‣ Communication and Process ‣ People ‣ The Bug 2 Open Source Software Seminar — Konstantin Käfer WebKit GTK Android Google Symbian Chrome Safari Qt Toolkit 3 Open Source Software Seminar — Konstantin Käfer 1. Project Structure and Goals WebCore JavaScriptCore Rendering Engine JavaScript Engine WebKit { Wrapper 4 Open Source Software Seminar — Konstantin Käfer 1. Project Structure and Goals Goals ‣ Web Content Engine: mainly web, but also general- purpose display/interaction engine ‣ Portability: Make it usable on many platforms ‣ Hackability: Keep code easy and maintainable ‣ Usability: Use platform-native UI conventions 5 Open Source Software Seminar — Konstantin Käfer 2. History 2. History 1999: Started as KHTML (KDE project) 2002: Apple forked quietly 2005: Apple opens up development process Now: “Unforking” 6 Open Source Software Seminar — Konstantin Käfer 2. History Apple vs. KHTML ‣ Apple did only the minimum required by LGPL ‣ No access to internal CVS ‣ Changes are released as single large patches ‣ Lots of platform-specific code ‣ Only WebCore/JSCore, but not WebKit was released 7 Open Source Software Seminar — Konstantin Käfer 3. Communication and Process Mailing lists Bug tracker IRC Ticket Patch Review Commit 8 Open Source Software Seminar — Konstantin Käfer 3. Communication and Process Mailing lists ‣ webkit-dev: General discussion ‣ webkit-reviews: Receives all review requests ‣ webkit-changes: Receives all commit messages ‣ webkit-unassigned: All unassigned tickets ‣ webkitsdk-dev: Development on Mac OS X 9 Open Source Software Seminar — Konstantin Käfer 3. Communication and Process Bug tracker ‣ Bugzilla 10 Open Source Software Seminar — Konstantin Käfer 3. -
Planet GNOME
GNOME. 101 choses à savoir... mais seulement 10 d'entre elles sont réellement importantes Êtes-vous confortablement installés ? Alors allons-y... ● GNOME, né en Août 1997, est le bébé de 2 mexicains, Miguel de Icaza et Federico Mena Quintero, créant ainsi une alternative de bureau libre, basée sur la GPL. Des débuts sexy + = qui sentent pas très bon Qu'est-ce que GNOME ? ● Le projet GNOME fournit deux choses : – L'environnement de bureau GNOME, un bureau intuitif et attirant pour les utilisateurs finaux. – La plate-forme de développement GNOME, un large framework pour construire des applications qui s'intègrent avec le reste du bureau. ● GNOME est un ensemble de logiciels libres, ainsi qu'une partie du projet GNU, dont le but est de donner aux utilisateurs le niveau de contrôle ultime sur leur bureau, leurs programmes et leurs données. Pourquoi GNOME ? ● GNOME est le bureau choisi par des grands noms de l'industrie comme HP, IBM, Novell, Red Hat et Sun Microsystems. ● GNOME est déjà utilisé dans de grands déploiements gouvernementaux, dans des lieux aussi divers que l'Estrémadure (Espagne) et Pékin (Chine). ● GNOME est le moyen idéal pour réduire les coûts et améliorer la fiabilité. Vous n'avez pas à payer de licences. Un petit tour rapide du bureau... ● Comme la plupart des bureaux, GNOME inclut un gestionnaire de fichiers, un navigateur web et un client email, ainsi qu'une importante quantité d'applications. Le gestionnaire de fichiers Nautilus (en mode spatial) Crée des vignettes de vos images Affiche un aperçu de vos fichiers texte Un petit tour rapide du bureau.. -
Towards Video on the Web with HTML5
Towards Video on the Web with HTML5 Authors François Daoust, Philipp Hoschka — W3C/ERCIM, Sophia-Antipolis, France Charalampos #$ Patrikakis — School o% El!ctrical an& Co"put!r En'in!!rin', ()*A, Ath!ns, +re!ce Rui S. Cruz, Mário S$ (un!s — IST/I(ESC-ID/I(.V, 0isbon, Portu'al Davi& Sala"a .sborn! — Atos R!search an& Innovation, Ma&ri&, Spain Presenter François Daoust 3%&453$or'6, Worl& Wi&! W!1 Consortiu" This presentation http7//555$53$org/89:9/)alks/:9:;-ht"l<-vi&!o-%&/ :; .cto1!r 89:9, Barc!lona, (EM Su""it )h! r!s!arch l!a&in' to th!s! r!sults has r!c!i2!& %un&in' %ro" th! Europ!an *nion>s S!2!nth Fra"!5ork Pro'ra""! ?FP@/899@-89:3A un&!r 'rant a'r!!"!nt nB8;CDC@ - .p!n M!&ia W!1 ?.MW!1A an& nB8;C;@; SociallE 5ar!, colla1oRati2!, sc la1l! Co&in' "E&ia &istri1utio( ?S R CE(A Outline Photo by Elaine Vallet What is HTML5? Let's make sure we're talking about the same thing… Video on the Web codecs, metadata, streaming, fragments More TV-Relevant Features CSS, SVG, Canvas Web Applications !evice AP#s, $idgets W3C: Shaping the Web of the future Web Standards (X)HTML, CSS, XML, SVG, PNG, XSLT, WCAG, RDF, ... Consortium 330 members, from i !"stry % ! rese%rch World-wide (ffices i ma y co" #ries, i &)"!i * Br%zi), C'i %, - !i%, Morocco, So"#' Afri&%, ... One Web! Fo" !e! % ! !ire&#e! by i ve #or of #'e Web, Tim Berners-Lee Global participation 30,000 1eo1)e subscribe! #o mai)i * )ists, 2,3004 1%rtici1% #s i 504 Gro"1s Part 1: What is HTML5? HTML5, what is it? It's a specification developed by the W3C HTML Working Group: Video on the Web Web -
Javascript: the First 20 Years
JavaScript: The First 20 Years ALLEN WIRFS-BROCK, Wirfs-Brock Associates, Inc., USA BRENDAN EICH, Brave Software, Inc., USA Shepherds: Sukyoung Ryu, KAIST, South Korea Richard P. Gabriel: poet, writer, computer scientist How a sidekick scripting language for Java, created at Netscape in a ten-day hack, ships first as a de facto Web standard and eventually becomes the world’s most widely used programming language. This paper tells the story of the creation, design, evolution, and standardization of the JavaScript language over the period of 1995–2015. But the story is not only about the technical details of the language. It is also the story of how people and organizations competed and collaborated to shape the JavaScript language which dominates the Web of 2020. CCS Concepts: • General and reference ! Computing standards, RFCs and guidelines; • Information systems ! World Wide Web; • Social and professional topics ! History of computing; History of programming languages; • Software and its engineering ! General programming languages; Scripting languages. Additional Key Words and Phrases: JavaScript, ECMAScript, Standards, Web browsers, Browser game theory, History of programming languages ACM Reference Format: Allen Wirfs-Brock and Brendan Eich. 2020. JavaScript: The First 20 Years. Proc. ACM Program. Lang. 4, HOPL (June 2020), 190 pages. https://doi.org/10.1145/3386327 1 INTRODUCTION In 2020, the World Wide Web is ubiquitous with over a billion websites accessible from billions of Web-connected devices. Each of those devices runs a Web browser or similar program which is able to process and display pages from those sites. The majority of those pages embed or load source code written in the JavaScript programming language. -
What Is Webkit?
SMASHING WEBKIT 1 CHAPTER 1 WHAT IS WEBKIT? WEBKIT IS AN open-source rendering engine Cascading Style Sheets (CSS). JavaScriptCore designed to display web pages. It powers Google compliments this layout engine with a high- Chrome and Safari as well as a variety of mobile performance interaction engine that provides devices such as iPhone, iPad, and Android feature-rich JavaScript functionality. phones and tablets. It also controls rendering in a variety of desktop applications such as Apple Th is chapter provides a short history of WebKit Mail and those created with Adobe AIR. and a discussion of which browsers, devices, and applications use the engine. You learn the various WebKit basically consists of two components: components that WebKit supports, as well as how WebCore and JavaScriptCore. WebCore controls these diff er across various implementations. all layout and rendering tasks, creating HTML visualizations based onCOPYRIGHTED DOM markup and MATERIAL 005_9781119999133-ch01.indd5_9781119999133-ch01.indd 7 110/19/110/19/11 33:44:44 PPMM PART I: INTRODUCING WEBKIT QUICK HISTORY Th e code that would later become WebKit began in 1998 as part of KDE’s web browser, Konqueror (designed primarily for Linux). As part of an eff ort to build their own web browser, Apple forked the HTML and JavaScript engine from KDE in 2002, naming the ported engine WebKit. Initially Apple and KDE cross-developed the engines, exchanging code patches and enhancements. Th en Apple made a number of unilateral decisions, including converting a portion of the codebase from C++ to Objective C, and dramatically altering other coding approaches. -
GATEKEEPER: Mostly Static Enforcement of Security and Reliability Policies for Javascript Code
GATEKEEPER: Mostly Static Enforcement of Security and Reliability Policies for JavaScript Code Salvatore Guarnieri Benjamin Livshits University of Washington Microsoft Research [email protected] [email protected] Abstract policies of JavaScript code [20, 25, 29, 35]. As a recent report from Finjan Security shows, widget- The advent of Web 2.0 has lead to the proliferation of based attacks are on the rise [17], making widget secu- client-side code that is typically written in JavaScript. rity an increasingly important problem to address. The This code is often combined — or mashed-up — with report also describes well-publicised vulnerabilities in the other code and content from disparate, mutually untrust- Vista sidebar, Live.com, and Yahoo! widgets. The pri- ing parties, leading to undesirable security and reliability mary focus of this paper is on statically enforcing secu- consequences. rity and reliability policies for JavaScript code. These This paper proposes GATEKEEPER, a mostly static ap- policies include restricting widget capabilities, making proach for soundly enforcing security and reliability poli- sure built-in objects are not modified, preventing code in- cies for JavaScript programs. GATEKEEPER is a highly jection attempts, redirect and cross-site scripting detec- extensible system with a rich, expressive policy language, tion, preventing global namespace pollution, taint check- allowing the hosting site administrator to formulate their ing, etc. Soundly enforcing security policies is harder policies as succinct Datalog queries. that one might think at first. For instance, if we want to ensure a widget cannot call document.write The primary application of GATEKEEPER this paper ex- plores is in reasoning about JavaScript widgets such as because this construct allows arbitrary code injection, those hosted by widget portals Live.com and Google/IG. -
Differences from HTML4
Differences from HTML4 W3C Working Draft 28 May 2013 This Version: http://www.w3.org/TR/2013/WD-html5-diff-20130528/ Latest Version: http://www.w3.org/TR/html5-diff/ Latest Editor's Draft: https://rawgithub.com/whatwg/html-differences/master/Overview.html Participate: File a bug (open bugs) Version History: https://github.com/whatwg/html-differences/commits Previous Versions: http://www.w3.org/TR/2012/WD-html5-diff-20121025/ http://www.w3.org/TR/2012/WD-html5-diff-20120329/ http://www.w3.org/TR/2011/WD-html5-diff-20110525/ http://www.w3.org/TR/2011/WD-html5-diff-20110405/ http://www.w3.org/TR/2011/WD-html5-diff-20110405/ http://www.w3.org/TR/2011/WD-html5-diff-20110113/ http://www.w3.org/TR/2010/WD-html5-diff-20101019/ http://www.w3.org/TR/2010/WD-html5-diff-20100624/ http://www.w3.org/TR/2010/WD-html5-diff-20100304/ http://www.w3.org/TR/2009/WD-html5-diff-20090825/ http://www.w3.org/TR/2009/WD-html5-diff-20090423/ http://www.w3.org/TR/2009/WD-html5-diff-20090212/ http://www.w3.org/TR/2008/WD-html5-diff-20080610/ http://www.w3.org/TR/2008/WD-html5-diff-20080122/ Editor: Simon Pieters (Opera Software ASA) <[email protected]> Previous Editor: Anne van Kesteren <[email protected]> Copyright © 2013 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract HTML is the core language of the World Wide Web. The W3C publishes HTML5 and HTML5.1. The WHATWG publishes HTML, which is a rough superset of W3C HTML5.1.