Native-Client-Announce Google Group

Native Client support on ARM

2013-01-22T21:32:08Z

Hi everybody,

It's been baking in the codebase for a while, and we're now extremely
pleased to announce Native Client support on ARM:
[link].

Also, check out the release notes:
[link].

Debuggers and a Visual Studio add-in for Native Client

2012-10-17T21:14:20Z

Hi everybody,

We just announced the nacl-gdb debugger for Windows, Mac, and Linux and a
Visual Studio add-in to make Native Client development easier and faster:

[link]

Both are available in the SDK. Comments and suggestions are very welcome on

Mono for Native Client now available through the SDK

2012-05-05T05:25:30Z

Hi everyone,

Versions of Mono for Native Client are now available for download in the
SDK. These are compiled with glibc and the libmono comes as a dynamic
library. Only pepper_19 and above has Mono available.

Note that you must keep your pepper_X and naclmono_X bundles in sync (ie,
don't update one without updating the other) or you will probably be unable

PSA: new nacl64-gdb debugger for 64-bit Windows and Linux

2012-03-06T20:36:16Z

We are happy to announce nacl64-gdb - our new port of GNU GDB for debugging NaCl applications on 64-bit Windows and Linux. Please find the instructions on how to get and use nacl64-gdb at [link]
For those who want to debug on 64-bit Windows under Visual Studio, we are pleased to inform you that this is now possible with nacl64-gdb used together with WinGDB. The detailed instructions are at [link]

Video from Native Client event now available

2011-12-14T18:34:32Z

Hi everybody,
On December 8, 2011, at an event held at Google, we presented the latest
news on Native Client and showcased work from some of the early adopters of
the technology, including Square Enix, Supergiant Games, Heartwood Studios,
and Unity Technologies. The video from the event is now available at

PSA: pepper_17 bundle updated.

2011-11-18T16:40:01Z

All:
The pepper_17 bundle has been updated. In this version:
- mouselock example
- libnacl.so has been removed from the glibc toolchain. This should make
building with libmono easier.
./naclsdk update pepper_17 --force # for mac, linux
naclsdk update pepper_17 --force # for Windows.
Enjoy!

PSA: pepper_16 bundle updated.

2011-11-18T00:07:02Z

All:
The pepper_16 bundle has been updated to include a mouselock example.
./naclsdk update pepper_16 --force # for mac, linux
naclsdk update pepper_16 --force # for Windows.
Enjoy!

Announce: NaCl SDK version 1.0.

2011-10-13T14:47:54Z

We are happy to announce Version 1.0 of the Native Client SDK utility. You
no longer need to download individual SDKs, instead you can use one utility
to update your Native Client SDK to the latest platforms.
To get this new NaCl SDK, visit:
[link] and follow the

PSA: gdb support for NaCl on Windows

2011-10-07T21:19:26Z

While we are still a long way from debugging Native Client applications in a
Windows specific software environment (read: Visual Studio) we have made it
a little easier to debug native client applications using the GNU Debugger,
also known as gdb.
You can now find detailed instructions here:
[link]

PSA: pepper_15 platform update.

2011-09-26T21:46:25Z

The pepper_15 platform has been updated to revision 1208, to fix a build bug
on Windows:
[link]
To get this bundle,
python sdk_update.py update
Thanks!

Re: PSA: Developer Beta of sdk_update available.

2011-09-23T02:16:47Z

Cross-posting to native-client-announce.
Folks,
A Developer Beta version of the Native Client SDK is available via the new
sdk_update utility.
There are still some rough edges to this new utility, but we thought we'd
push it early so you can get the Pepper 15 APIs that support 3D development
in Native Client.

PSA: load progress and error handling example

2011-09-14T20:51:00Z

[Cross-posting from native-client-discuss. -- Christian S.]
Folks,
tl;dr load_progress in the SDK has been update to handle browser loading
errors.
The SDK has an example called 'load_progress' which shows how to handle
'progress' events and some load events. However, is lacked example code for
handling things like browser compatibility. The example in the repo has

Native Client SDK 0.5 for Chrome 14 and beyond now available to try

2011-07-29T21:33:54Z

Hi everyone,
On the Native Client team we have been working hard towards ABI (application
binary interface) stability in Chrome for Native Client applications. We are
pleased to inform you that with Chrome 14 we have now achieved this
milestone, so that applications you build for Chrome 14 will continue to

Native Client and Web Portability

2010-03-17T23:02:45Z

Today we are pleased to share some of our plans for instruction-set
portability in Native Client. Please see this blog
post<[link]>
for
more details, including links to two papers we are sharing on the subject.
Brad Chen

Attention Security Sleuths!

2010-02-17T19:55:03Z

As we have stated on numerous occasions, we have open sourced Native Client
in part because we believe the scrutiny of the community will help us build
a system that is safer and generally better. Our experience with the Native
Client Security
Contest<[link]>

Security vulnerability in NaCl on x86-32

2010-01-13T19:53:38Z

We have found a vulnerability in Native Client for x86-32. The hole
has been present in all releases of Native Client since August. It
may allow untrusted code to jump to arbitrary locations within its
code segment, effectively subverting the validator's notion of the
instruction stream.
Because official Native Client releases only allow execution of code

Native Client Chrome Integration

2009-10-06T00:16:08Z

Last week we made a small step in integrating Native Client with the browser
by adding it to the Google Chrome Developer Channel behind a command line
flag.
Until now, using Native Client from a browser required installing an NPAPI
plugin. This was the right choice for our research release; however, NPAPI

Help Wanted!

2009-09-10T15:29:41Z

Are you an expert in Compilers? Operating Systems? Computer Architecture?
Web Security? All of the above? Are you an exceptionally talented engineer
with a passion for building things right? If so then you might like to help
us build Native Client. To learn more please send a resume to
bradc...@google.com.

Native Client and a platform independent NPAPI proposal

2009-07-08T01:13:02Z

All,
A number of us have been looking at how to address some of the issues we
have observed in writing NPAPI plugins that need to be supported across
multiple operating systems and browser platforms, and also the issues of
using NPAPI from inside a Native Client module. I am happy to announce
that we have just put a proposal on the Mozilla wiki describing some changes

And the winner is...

2009-07-07T23:08:54Z

The Native Client Team would like to congratulate the winners of the Native
Client Security Contest. Please have a look at this blog
post<[link]>and
the contest
site <[link]> for all the

Native Client Update - June 2009

2009-06-11T00:14:03Z

This seems like an appropriate time to share some perspective and some plans
on the Native Client project. We've made a lot of progress since our open
source release in December, and as we firm up plans for the next year or so
we want to share some of our thinking with you.
To date, Native Client has been presented primarily as a research project.

A Fresher SVN repository

2009-05-12T17:36:50Z

To date the Native Client team at Google has been working with an private
source code repository and periodically mirroring our tree to the external
SVN repository hosted on code.google.com. During the next week or two, we
will be transitioning to using the external SVN repository as our main
development repository. Our ultimate goal is to make the system friendlier

Native Client at upcoming events

2009-05-11T23:24:43Z

In case you're interested, Native Client presentations will be happening at
several events during the next month:
IEEE Symposium on Security and Privacy
18-20 May 2009
The Claremont Resort
Oakland, CA USA
[link]
Google I/O
27-28 May 2009
Moscone West
San Francisco, CA USA
[link]

One Week Warning!

2009-04-28T20:47:07Z

*Attention Teams:* Only one week left in the Native Client Security
Contest<[link]>.
Send us your issues --- No time to loose!
*Please remember* that you must submit a* final summary* to guide the jury
in evaluating your submitted issues. The summary is your chance to directly

new NaCl release

2009-04-24T15:25:05Z

A new Native Client release went out yesterday evening. Some noteworthy
changes:
- GDB support. We now ship a Linux version of GDB that works with
sandboxed NaCl modules. Enjoy!
- The Linux outer sandbox is included in this release, disabled by
default.
- Many bug fixes, including a number of contest issues. We also decided

Security Contest - Only Two Weeks Left!

2009-04-21T18:20:58Z

There are only two weeks left in the Native Client Security
Contest<[link]>and
there's never been a better time to report bugs! So far we've seen
twenty-four submitted issues from seven teams, so it's definitely not too
late to be competitive. We've seen some great buffer overflows, information

Reminder: Native Client Security Contest

2009-04-08T00:49:47Z

Just a friendly reminder that there's only about a month left in the Native
Client Security Contest. Some very interesting bugs have been found: see
[link] for the gory details. Although
we're very pleased with the bugs we've seen so far, there aren't that many
teams that have submitted valid issues. There's never been a better time to

Google Summer of Code

2009-03-31T22:31:16Z

Native Client has received Google Summer of Code funding. From
[link]
*Google Summer of Code* is a global program that offers student developers
stipends to write code for various open source software projects. We have
worked with several open source, free software, and technology-related

release 56 is obsolete

2009-03-31T01:40:25Z

It appears that some people may have downloaded release 56, which was
visible briefly on the code site; please note that it's been
superceded by release 57.

Our apologies.

Native Client Engineering Team

Release 57 now available for download

2009-03-31T01:33:45Z

Release 57 is now available for download.

Some highlights of this release:

- the expiration date was extended from 17 April to 30 April.

- the ABI number has been incremented; you will need to rebuild all
your NaCl modules.

- NaCl modules can no longer be loaded from file: URLs; the

release 46 now available for download

2009-03-13T04:01:08Z

Some highlights of this release:
- The freshness date was extended from 17 March to 17 April.
- ABI number has been incremented; you will need to rebuild all your NaCl
modules.
- Added a "platform_qualification_test", to be used someday as an
additional sanity check on the platform before install and before launching

Announcing the Native Client Security Contest

2009-02-25T17:50:43Z

Today we announced the Native Client Security
Contest<[link]>on the
Google
Code blog <[link]>. Please have a look at
the blog post and the contest site for more information. In particular be
sure to take note of the following:

video and slides now available

2009-02-12T19:53:28Z

The slides from the Native Client tech talk as well as a video of the
Stanford talk are now linked from the project home page,
[link].
Enjoy!
Brad Chen

updated source release

2009-01-18T16:13:54Z

We updated our source release on Friday. Key changes are as follows:
- We've revised our ABI version number. Please update your browser plugin
and rebuild any NaCl modules you're working with.
- The system now supports multiple NaCl graphics areas in a single HTML
page.
- We've added a Lua intepreter. See native_client/tests/lua.

More university talks scheduled

2009-01-14T14:28:15Z

Please check the our Tech Talks
wiki<[link]>for more
details on three additional tech talks that have been scheduled:
- 20 January: Stanford University
- 28 January: Massachusetts Institute of Technology
- 29 January: Carnegie Mellon University
For those who can't attend a talk, we plan to post the slides and a YouTube

Updated Downloads

2008-12-23T15:10:12Z

We updated our downloads this week to address both issues reported
externally and some continuing internal work. Changes include:
- Addressed typo in error message [Issue 13].
- Disallow call/jump indirections [Issue 23] as in:
ff 12 call (*edx)
Clarified the comment for cld/std in ncdecode_table.c

University tech-talk series

2008-12-19T19:20:57Z

To help the community learn more about Native Client, we will be scheduling
a number of technical talks at major universities. The first talks are in
Europe and are as follows:
- 7 January 2009: Swiss Federal Institute of Technology Zürich (ETH Zürich)
- 8 January 2009: Université Pierre & Marie Curie (Paris-VI)

Kudos for the first validated exploit!

2008-12-13T16:42:43Z

I'm please to announce that the first Native Client exploit from outside
Google has been submitted as Issue
23<[link]>to the
project site. User defend.the.world found an inner-sandbox escape due
to a defect in the validator. The validator was checking for calls through

Updated Downloads; Please Read

2008-12-12T03:10:15Z

We are extremely pleased with the interest we've seen in Native Client.
We're delighted that so many researchers and developers recognize its
potential to help us build better and safer web applications. Today's new
downloads should address some build problems. We also removed debugging code
that could be dangerous if enabled, and added some safety features to make