The information security world is focused on two new security vulnerabilities, “Spectre” and “Meltdown”, that represent vulnerabilities embedded in computer hardware. Lawfare readers should respond in two ways: keep their operating systems up to date and, critically, install an ad-blocker for your web browser. (Here are guides on how to do so in Chrome and Firefox.) In fact, a proper response to Spectre should involve ad-blocking on all government computers. Other than that, don’t worry.
Readers who just wanted to know what to do can stop reading. But for those curious about some of the technical background on these vulnerabilities and why ad-blocking is an essential security measure for a modern computer, read on.
"In a blog post titled Blink: A rendering engine for the Chromium project, Google has announced that Chromium (the open source backend for Chrome) will be switching to Blink, a new WebKit-based web rendering engine. Quoting: 'Chromium uses a different multi-process architecture than other WebKit-based browsers, and supporting multiple architectures over the years has led to increasing complexity for both the WebKit and Chromium projects. This has slowed down the collective pace of innovation... This was not an easy decision. We know that the introduction of a new rendering engine can have significant implications for the web. Nevertheless, we believe that having multiple rendering engines—similar to having multiple browsers—will spur innovation and over time improve the health of the entire open web ecosystem. ... In the short term, Blink will bring little change for web developers. The bulk of the initial work will focus on internal architectural improvements and a simplification of the codebase. For example, we anticipate that we’ll be able to remove 7 build systems and delete more than 7,000 files—comprising more than 4.5 million lines—right off the bat. Over the long term a healthier codebase leads to more stability and fewer bugs.'"
Remote desktop access programs help users work on a computer through another one. Such programs can be extremely helpful for mutual work between people, technical support, and various help and tutorials. Basically, desktop sharing programs are perfect for all sorts … Continue reading →
Remote desktop access programs help users work on a computer through another one. Such programs can be extremely helpful for mutual work between people, technical support, and various help and tutorials. Basically, desktop sharing programs are perfect for all sorts … Continue reading →
Static blocks of text like the one you’re looking at now are an antiquated and inefficient way to get words into your head. That’s the contention of Boston-based startup Spritz, which has developed a speed-reading text box that shows no more than 13 characters at a time. The Spritz box flashes words at you in quick succession so you don’t have to move your eyes around a page, and in my very quick testing it allowed me to read at more than double my usual reading pace. Spritz has teamed up with Samsung to integrate its speed reading functionality with the upcoming Galaxy S5 smartphone.
The written word, after 8,000 or so years, is still an extremely effective way to get a message from one mind into the minds of others. But even with the advent of the digital age and decades of usability work, font and layout development, we’re still nowhere near optimal efficiency with it yet.
Take this article – I’ve written it in easily digestible chunks, and we’ve presented it in nice, thin, 10 to 14 word columns that should make it easy to scan. But pay attention to what your eyes are doing while you try to read it. Chances are, even if you’re a quick reader, your eyes are jumping around all over the place.
In fact, according to Boston-based startup Spritz, you spend as little as 20 percent of your reading time actually taking in the words you’re looking at, and as much as 80 percent physically moving your eyes around to find the right spot to read each word from. So, the Spritz team decided, why not eliminate that time altogether?
The Spritz reader is a simple, small box that streams text at the reader, one word at a time. The words are presented in a large, very reader-friendly font, and centered around the "optimal recognition point" of each word. In fact, the box will only display a maximum of 13 characters, so larger words are broken up.
What’s really interesting is just how quickly this system can pipe information into your brain. I did a couple of online reading speed tests and found my average reading speed for regular blocks of text is around 330-350 words per minute. But I can comfortably follow a Spritz box at up to 500 words per minute without missing much, losing concentration or feeling any kind of eye strain. In short stints I can follow 800 words per minute, and the team says it’s easy to train yourself to go faster and retain more.
Try it yourself. Here’s 250 words per minute:
Spritz claims that information retention rates on "spritzed" content are equal to or higher than that of traditional text block reading, and that some of its testers are now comfortably ingesting content at 1000 words per minute with no loss of information retention. That’s Tolstoy’s 1,440 page behemoth War and Peace dispatched in a single 10 hour sitting, if you had the concentration for it, or Stieg Larsson's Girl with a Dragon Tattoo in two and a bit hours.
Spritz is also clearly developed to excel on mobile and handheld reading devices, and as such, the company has announced that Spritz will make its mobile debut on the upcoming Samsung Galaxy S5 release. Smartwatch and Google glass-type implementations are also on the radar.
The mobile angle will have to be strong as there are numerous free tools for desktop browsers that can replicate a similar reading experience for free. If you’re using a Chrome browser, check out Spreed as an example.
Perhaps the most significant move for Spritz will be bringing this speed reading technology to bear on your Android e-book library. Anything that can help me get through my reading backlog quicker will be most welcome!
Beginning today, we have disabled new project creation on Google Code. We will be shutting down the service about 10 months from now on January 25th, 2016. Below, we provide links to migration tools designed to help you move your projects off of Google Code. We will also make ourselves available over the next three months to those projects that need help migrating from Google Code to other hosts.
March 12, 2015 - New project creation disabled.
August 24, 2015 - The site goes read-only. You can still checkout/view project source, issues, and wikis.
January 25, 2016 - The project hosting service is closed. You will be able to download a tarball of project source, issues, and wikis. These tarballs will be available throughout the rest of 2016.
Google will continue to provide Git and Gerrit hosting for certain projects like Android and Chrome. We will also continue maintaining our mirrors of projects like Eclipse, kernel.org and others.
How To Migrate Your Data Off Google Code
You’re still waiting for me to explain what I meant when I referred to JavaScript as a last resort. I hinted at it in the preceding paragraph. Not the part on JavaScript debugging, but my reference to CSS and HTML. These do a lot more than paint screens. They are a browser's client-side framework. Everything they do is handled as native code. In other words, they're fast. CSS3 and HTML5 are too inconsistently implemented (if at all) across browsers to design to unless you're specifically targeting Safari, iPhone, or other WebKit-based browsers.
Tom makes the point that the use of AJAX JavaScript breaks Web interoperability. He further points out that HTML is a static layout language, where CSS is dynamic and adaptive. (Use HTML5/DOM for document structure, and CSS4 for presentation - layout, formatting and visual interface).
It is the consistency of the WebKit document model across all WebKit browsers that makes for an interoperable Open Web future. I would not however discount the importance of Firefox and Opera embracing the WebKit document model (HTML5, CSS4, SVG/Canvas, JavaScript, DOM2). That's our guarantee that the future of the Open Web will actually be open.
Tom goes on to suggest that instead of "AJAX", developers would be better off thinking in terms of "ACHJAX": Asynchronous CSS4 - HTML5 - JavaScript and XML ..... with the focus on getting as much done in CSS4 as possible.
InfoWorld's Tom Yager makes the case for the WebKit visual document model over AJAX. The problem with AJAX as he sees it is that it's JavaScript heavy. And that breaks precious Web interoperability. He makes the point that if something can be done in CSS, it should. He also argues that WebKit is the best tool because the document model is that of advanced HTML5 and CSS3.
"... These [WebKit] browsers also share a stellar accelerated JavaScript interpreter that makes the edit/run/debug cycle go faster. They are also the only browsers that deliver on CSS4 and HTML5 standards (with some elements that are proposed to the W3C standards body). Sites that are visually rich may start sprouting "best viewed with Safari" banners until other browsers catch up. The banner would also let users know that your site is optimized for iPhone....."
Humm. Did you catch that? CSS4!!! I guess he's referring to the WebKit penchant for putting advanced graphical transitions and animations into CSS instead of relying on a device specific or OS specific API.
Placing the visual interface instructions in the documents presentation layer (CSS4) is a revolutionary idea. The WebKit model will go a long way towards creating a global interoperability layer that rides above lower device, OS, browser and application specifics. So yes, by all means let's go with CSS4 :)
In the future application developers won't care what desktop operating system you use, they will only care which Fit Client platform is the most pervasive. This is what Adobe AIR, Microsoft Silverlight, Google Gears and Curl are fighting for. Nothing short of the future of desktop and RIA development.
Microsoft brings with it a huge ecosystem of .NET developers - potentially millions of developers already skilled in WPF, XAML and C#. That's a pretty scary for others in the Fit Client arena.
Right now the future of the desktop is completely open. Anyone with enough clout could win the desktop - effectively usurping Microsoft Windows dominate position.
Well well well. The experts are finally starting to get it. WebKit is extraordinary, not as a browser, but as the "Open Web" foundation for web application (RiA) development that spans device and desktop.
The vastly improved hardware and network throughput are not the primary drivers of this sea change. "The biggest jolt to the mobile Web development experience, in my view, has been the iPhone. Its implementation of mobile Safari, while imperfect, has given handsets the real Internet, rather than a hobbled, niched version that was typical in devices that preceded it."
What that means for the future, according to O'Grady, is that the mobile application space "will mirror the development on the client, honestly. It will evolve into a platform barely distinguishable, in many respects, from the traditional desktop browser experience."
One of the primary reasons for the enormous complexity of the Gecko code base is that it aims to provide much more than just an HTML renderer. Mozilla's early goals were extremely ambitious—the original Mozilla application suite included a browser, a complete mail and newsgroup program, a web design tool, and an IRC client. In addition to rendering HTML, Gecko also provides a versatile XML-based user interface rendering framework called XUL that was used extensively in those applications. XUL is still used today to create the Firefox user interface, and it facilitates that browser's support for extensions, which are regarded by many enthusiasts as one of the most valuable features offered by Firefox.
XPCOM, a powerful component system
Gecko 1.9 uses the cross-platform Cairo rendering framework.
The consensus of the developers who are using WebKit is clear: it's an outstanding rendering engine that lends itself to an extremely diverse assortment of practical uses. It is everywhere, and it is gaining traction at a very impressive rate. That traction is causing some developers to question whether Mozilla's Gecko rendering engine is still relevant.
ZoooS LLC today previewed ZoooS Office, a web-based office suite that puts OpenOffice.org 3.0 in a browser, targeting enterprise, SMB, and individual users alike with a blend of software-as-a-service (SaaS) and desktop advantages.
Other key ZoooS Office implementations will include Mozilla XULRunner; Firefox, Opera, Safari as well as the new Google Chrome web browser; social networking sites such as Facebook, MySpace, and Second Life; and Nintendo Wii and Sony PlayStation. Regardless of implementation, ZoooS applications run entirely on the client machine, performing all file operations locally to reduce network traffic, improve application performance, and support offline access.
Public availability of ZoooS Office is scheduled for the fourth quarter of 2008. Initially, ZoooS will deliver the Mozilla XULRunner version, a Firefox plug-in, an Opera widget, and an intranet server. ZoooS will follow up with a Vista gadget and Internet Explorer support in the first half of 2009.
For more information on ZoooS, please visit www.zooos.com.
Yet another wrapper around OpenOffice.org, this time the 3.0 version still in beta. $99.90 per seat for 10 users, Lots of Javascript to give a web collaboration capability. Perhaps most notable so far: [i] a sniff that there's a fair amount of money behind this one; and [ii] an article by Eric Lai says they approached the OOo Project but were rebuffed because they compete with desktop OOo. Support for different browsers planned. an XULRunner plug-in the works. Several mashups mentioned. Claims 80 percent of OOo features available, which is another way of saying that 20 per cent of the features are not supported. Claim that oSays code will be released under GPL. Apparently that's just their custom stuff because OOo 3.0 beta is LGPL. Building a business atop a code base controlled by a malevolent branch of Sun Microsystems seems less than wise. More at zooos.com. Preliminary impression: Like OOo itself, dead end technology that sucks mind and market share from software that supports truly open standards. The world needs to figure out that the OpenDocument format is roughly as open as OOXML. Open standards are fully specified so anyone can implement them.
“The spectacular growth of SharePoint is the result of the great combination of collaboration and information management capabilities it delivers,” Microsoft Co-founder Bill Gates said back in March. “I believe that the success we’ve seen so far is just the beginning for SharePoint.”
the growing popularity of cloud computing means corporate data centers will increasingly start to look like Internet data centers. Cisco has already recognized that as the "network" continues to become the focal point around which our digital personal and work lives revolve, the opportunity to make money will be immense. That's why Chambers never misses an opportunity to talk about "collaboration."
For instance, in the press release announcing the company's latest numbers, he said: "We believe we are entering the next phase of the Internet as growth and productivity will center on collaboration enabled by networked Web 2.0 technologies." But Cisco isn't the only one with this vision - Microsoft (MSFT) and Google (GOOG) are thinking along these lines as well, and are much further ahead in the game.
Also see post from Savio Rodgriguez. PhoneGap is funded by a grant from MIT. Open source.
"PhoneGaps lets developers wrap web applications inside a native application using WebKit, making development easier for those who aren't familiar with Objective-C and Cocoa. In fact, the framework even includes a tool for easily doing this type of "native web app" packaging. And if a native web app wrapper sounds like it would be right up your alley, you can download PhoneGap for free and give it a whirl."
Main features
The main features of the Lively Kernel include:
Small web programming environment and computing kernel,
written entirely with JavaScript. In addition to its application
execution capabilities, the platform can also function as
an integrated development environment (IDE), making the
whole system self-contained and able to improve and
extend itself on the fly.
Programmatic access to the user interface. Our system provides
programmatic access from JavaScript to the user interface via the
Morphic user interface framework. The user interface is built around
an event-based programming model familiar to most web developers.
Asynchronous networking. As in Ajax, you can use asynchronous HTTP
to perform all the network operations asynchronously, without
blocking the user interface.
"The Sun Labs Lively Kernel is a new web programming environment developed at Sun Microsystems Laboratories. The Lively Kernel supports desktop-style applications with rich graphics and direct manipulation capabilities, but without the installation or upgrade hassles that conventional desktop applications have. The system is written entirely in the JavaScript programming language, a language supported by all the web browsers, with the intent that the system can run in commercial web browsers without installation or any plug-in components. The system leverages the dynamic characteristics of the JavaScript language to make it possible to create, modify and deploy applications on the fly, using tools built into the system itself. In addition to its application execution capabilities, the Lively Kernel can also function as an integrated development environment (IDE), making the whole system self-sufficient and able to improve and extend itself dynamically....."
Too little too late? Interestingly, Lively Kernel is 100% JavaScript. Check out this "motivation" rational:
"...The main goal of the Lively Kernel is to bring the same kind of simplicity, generality and flexibility to web programming that we have known in desktop programming for thirty years, but without the installation and upgrade hassles than conventional desktop applications have.
The Lively Kernel places a special emphasis on treating web applications as real applications, as opposed to the document-oriented nature of most web applications today. In general, we want to put programming into web development, as opposed to the current weaving of HTML, XML and CSS documents that is also sometimes referred to as programming. ...."
I agree with the Web document <> Web Application statement. I think the shift though is one where the RiA frames web documents in a new envirnement, blending in massive amounts of data, streaming media and graphics. The WebKit docuemnt model was designed for this p
1. Google will be releasing VP8 under an open source and royalty-free basis. VP8 is a high-quality video codec that Google acquired when they purchased the company On2. The VP8 codec represents a vast improvement in quality-per-bit over Theora and is comparable in quality to H.264.
2. The VP8 codec will be combined with the Vorbis audio codec and a subset of the Matroska container format to build a new standard for Open Video on the web called WebM. You can find out more about the project at its new site: http://www.webmproject.org/.
3. We will include support for WebM in Firefox. You can get super-early WebM builds of Firefox 4 pre-alpha today. WebM will also be included in Google Chrome and Opera.
4. Every video on YouTube will be transcoded into WebM. They have about 1.2 million videos available today and will be working through their back catalog over time. But they have committed to supporting everything.
5. This is something that is supported by many partners, not just Google and others. Content providers like Brightcove have signed up to support WebM as part of a full HTML5 video solution. Hardware companies, encoding providers and other parts of the video stack are all part of the list of companies backing WebM. Even Adobe will be supporting WebM in Flash. Firefox, with its market share and principled leadership and YouTube, with its video reach are the most important partners in this solution, but we are only a small part of the larger ecosystem of video.
"On The Cutting Edge
Midori is blazing fast, utilizing the latest web technologies and a small
but dexterous array of extensions provide all the essential features."
"On The Cutting Edge
Midori is blazing fast, utilizing the latest web technologies and a small
but dexterous array of extensions provide all the essential features."
Yahoo Chief Information Security Officer Alex Stamos announced today at Black Hat 2014 that starting in the fall of this year, the purple-hued company will begin giving users the option of seamlessly wrapping their e-mails in PGP encryption. According to Kashmir Hill at Forbes, the encryption capability will be offered through a modified version of the same End-to-End browser plug-in that Google uses for PGP in Gmail.
The announcement was tweeted by Yan Zhu, who has reportedly been hired by Yahoo to adapt End-to-End for use with Yahoo Mail. Zhu formerly worked as an engineer at the Electronic Frontier Foundation, an organization that has consistently been outspoken in its call for the widespread use of encryption throughout the Web and the Internet in general.
YouTube has decided it's had enough of Adobe's perenially-p0wned Flash and will therefore now default to delivering video with the HTML5 <video> tag.
A post by the video vault's engineering and development team says the move is now possible, and sensible, because the industry has invented useful things like adaptive bitrates, encryption, new codecs and WebRTC that make the <video> usable work in the real world.
Those additions mean HTML5 is at least as functional – or more so – than Flash, and if YouTube detects you are running Chrome, IE 11, Safari 8 and beta versions of Firefox, it'll now deliver video using <video> and flush Flash.
YouTube's also decided to can what it calls the “'old style' of Flash
YouTube seems not to care a jot that its actions are inimical to Adobe, saying it's just doing what all the cool kids – Netflix, Apple, Microsoft and its competitor Vimeo – have already done.
Which is not to say that Flash is dead: those who don't run the browsers above will still get YouTube delivered by whatever technology works bes tin their environment. And that will often – perhaps too often* – be Flash. ®
Bootnote * Until they get p0wned, that is: Flash is so horridly buggy that Apple has just updated its plugin-blockers to foil versions of the product prior to 16.0.0.296 and 13.0.0.264.
"Those who know me best are quick to let me know: I'm a touch stubborn on certain matters. But there is one area where I've found myself caving to the pressures of reality. In this article, I'll make a case for why I believe ChromeOS might end up winning the OS wars."
In a post on Wednesday, researchers Alex Halderman and Nadia Heninger presented compelling research suggesting that the NSA has developed the capability to decrypt a large number of HTTPS, SSH, and VPN connections using an attack on common implementations of the Diffie-Hellman key exchange algorithm with 1024-bit primes. Earlier in the year, they were part of a research group that published a study of the Logjam attack, which leveraged overlooked and outdated code to enforce "export-grade" (downgraded, 512-bit) parameters for Diffie-Hellman. By performing a cost analysis of the algorithm with stronger 1024-bit parameters and comparing that with what we know of the NSA "black budget" (and reading between the lines of several leaked documents about NSA interception capabilities) they concluded that it's likely NSA has been breaking 1024-bit Diffie-Hellman for some time now.
The good news is, in the time since this research was originally published, the major browser vendors (IE, Chrome, and Firefox) have removed support for 512-bit Diffie-Hellman, addressing the biggest vulnerability. However, 1024-bit Diffie-Hellman remains supported for the forseeable future despite its vulnerability to NSA surveillance. In this post, we present some practical tips to protect yourself from the surveillance machine, whether you're using a web browser, an SSH client, or VPN software.
Disclaimer: This is not a complete guide, and not all software is covered.
