Skip to content
/ iojs Public

Tool for runtime execution of node applications using Javascript.

License

View license
0 stars 2 forks Branches Tags Activity
Star
Notifications You must be signed in to change notification settings

Aquaogen/iojs

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
benchmark
benchmark
 
 
deps
deps
 
 
dist
dist
 
 
doc
doc
 
 
lib
lib
 
 
out
out
 
 
src
src
 
 
test
test
 
 
tools
tools
 
 
AUTHORS
AUTHORS
 
 
BSDmakefile
BSDmakefile
 
 
CHANGELOG.md
CHANGELOG.md
 
 
COLLABORATOR_GUIDE.md
COLLABORATOR_GUIDE.md
 
 
CONTRIBUTING.md
CONTRIBUTING.md
 
 
GOVERNANCE.md
GOVERNANCE.md
 
 
LICENSE
LICENSE
 
 
Makefile
Makefile
 
 
Makefile.build
Makefile.build
 
 
OLD_README.md
OLD_README.md
 
 
README.md
README.md
 
 
ROADMAP.md
ROADMAP.md
 
 
WORKING_GROUPS.md
WORKING_GROUPS.md
 
 
all.html
all.html
 
 
android-configure
android-configure
 
 
common.gypi
common.gypi
 
 
config.gypi
config.gypi
 
 
config.mk
config.mk
 
 
configure
configure
 
 
icu_config.gypi
icu_config.gypi
 
 
iojs
iojs
 
 
iojs-v3.3.1.tar.gz
iojs-v3.3.1.tar.gz
 
 
node
node
 
 
node.gyp
node.gyp
 
 
vcbuild.bat
vcbuild.bat
 
 

Repository files navigation

Google IO.js

Tool for runtime execution of node applications using Javascript.

Running

This repository is PRECOMPILED

./iojs --version

Naming

io.js		Software
iojs.org	Website

Build

Environment Variables (CentOS 7.2.1511)

GNU GCC				PATH > /usr/bin/gcc
PYTHON				PATH > /usr/bin/python
CLANG				?
GNU Make			PATH > /usr/bin/make
libexecinfo (BSD)	?

Install Python

cd /path/to/python
export PYTHON=/path/to/python
$PYTHON ./configure
make

Install io.js

cd /path/to/iojs
tar -xvf iojs-3.3.1.tar.gz
./configure
make	
make check
make test
make doc
man doc/iojs.1
iojs -e "console.log('Hello from io.js ' + process.version)"

Contents

Markdowns

  • AUTHORS
  • CHANGELOG
  • COLLABORATOR_GUIDE
  • CONTRIBUTING
  • GOVERNANCE
  • LICENSE
  • ROADMAP
  • README.md
  • WORKING_GROUPS

Directory

.			io.js Source
benchmark	?
deps		?
deps/npm	Node Package Manager
dist		?
doc			Documentation
doc/api		API Documentation
lib			Library
out			?
src			Source Code
test		Source Code Test
tools		?

Files

Releases: 		dist/
Source:			iojs-v3.3.1.tar.gz
Documentation
	API			all.html, doc/api
	Command		make doc; man doc/iojs.1
	io.js		?

Download Verification

Checksum

To check that a downloaded file matches the checksum, run it through sha256sum with a command such as:

$ grep iojs-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -

GPG keys

To verify a SHASUM256.txt.asc, import all GPG keys of individuals authorized to create releases. GPG keys are listed at Release Team.

Use a command such as this to import the keys:

$ gpg --keyserver pool.sks-keyservers.net \
  --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D

Configuration

Android

Be sure you have downloaded and extracted [Android NDK] (https://developer.android.com/tools/sdk/ndk/index.html) before in a folder. Then run:

$ ./android-configure /path/to/your/android-ndk
$ make

'Intl' (ECMA-402)

Intl support is not enabled by default.

'small' (English only)

This option will build with "small" (English only) support, but the full Intl (ECMA-402) APIs. With --download=all it will download the ICU library as needed.

Unix / Macintosh:

$ ./configure --with-intl=small-icu --download=all

Windows:

> vcbuild small-icu download-all

The small-icu mode builds with English-only data. You can add full data at runtime.

'full ICU'

With the --download=all, this may download ICU if you don't have an ICU in deps/icu.

Unix / Macintosh:

$ ./configure --with-intl=full-icu --download=all

Windows:

> vcbuild full-icu download-all
### no 'Intl'


The `Intl` object will not be available. This is the default at
present, so this option is not normally needed.

Unix / Macintosh:

```text
$ ./configure --with-intl=none

Windows:

> vcbuild intl-none

Existing 'ICU'

$ pkg-config --modversion icu-i18n && ./configure --with-intl=system-icu

Specific 'ICU'

You can find other ICU releases at the ICU homepage. Download the file named something like icu4c-**##.#**-src.tgz (or .zip).

Unix / Macintosh

# from an already-unpacked ICU:
$ ./configure --with-intl=[small-icu,full-icu] --with-icu-source=/path/to/icu

# from a local ICU tarball
$ ./configure --with-intl=[small-icu,full-icu] --with-icu-source=/path/to/icu.tgz

# from a tarball URL
$ ./configure --with-intl=full-icu --with-icu-source=https://url/to/icu.tgz

Windows

First unpack latest ICU to deps/icu icu4c-##.#-src.tgz (or .zip) as deps/icu (You'll have: deps/icu/source/...)

> vcbuild full-icu

FIPS-compliant OpenSSL

NOTE: Windows is not yet supported

It is possible to build io.js with OpenSSL FIPS module.

Note that building in this way does not allow you to claim that the runtime is FIPS 140-2 validated. Instead you can indicate that the runtime uses a validated module. See the [security policy] (https://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1747.pdf) page 60 for more details. In addition, the validation for the underlying module is only valid if it is deployed in accordance with its [security policy] (https://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1747.pdf). If you need FIPS validated cryptography it is recommended that you read both the [security policy] (https://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1747.pdf) and [user guide] (https://openssl.org/docs/fips/UserGuide-2.0.pdf).

Instructions:

  1. Obtain a copy of openssl-fips-x.x.x.tar.gz. To comply with the security policy you must ensure the path through which you get the file complies with the requirements for a "secure installation" as described in section 6.6 in the [user guide] (https://openssl.org/docs/fips/UserGuide-2.0.pdf). For evaluation/experimentation you can simply download and verify openssl-fips-x.x.x.tar.gz from https://www.openssl.org/source/
  2. Extract source to openssl-fips folder and cd openssl-fips
  3. ./config
  4. make
  5. make install (NOTE: to comply with the security policy you must use the exact commands in steps 3-5 without any additional options as per Appendix A in the [security policy] (https://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1747.pdf). The only exception is that ./config no-asm can be used in place of ./config )
  6. Get into io.js checkout folder
  7. ./configure --openssl-fips=/path/to/openssl-fips/installdir For example on ubuntu 12 the installation directory was /usr/local/ssl/fips-2.0
  8. Build io.js with make -j
  9. Verify with node -p "process.versions.openssl" (1.0.2a-fips)

Security

All security bugs in io.js are taken seriously and should be reported by emailing [email protected]. This will be delivered to a subset of the project team who handle security issues. Please don't disclose security bugs public until they have been handled by the security team.

Your email will be acknowledged within 24 hours, and you’ll receive a more detailed response to your email within 48 hours indicating the next steps in handling your report.

Teams

The io.js project team comprises a group of core collaborators and a sub-group that forms the Technical Steering Committee (TSC) which governs the project. For more information about the governance of the io.js project, see GOVERNANCE.md.

Technical Steering Committee

Collaborators

Collaborators & TSC members follow the COLLABORATOR_GUIDE.md in maintaining the io.js project.

Release

Releases of Node.js and io.js will be signed with one of the following GPG keys:

The full set of trusted release keys can be imported by running:

gpg --keyserver pool.sks-keyservers.net --recv-keys 9554F04D7259F04124DE6B476D5A82AC7E37093B
gpg --keyserver pool.sks-keyservers.net --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
gpg --keyserver pool.sks-keyservers.net --recv-keys 0034A06D9D9B0064CE8ADF6BF1747F4AD2306D93
gpg --keyserver pool.sks-keyservers.net --recv-keys FD3A5288F042B6850C66B31F09FE44734EB7990E
gpg --keyserver pool.sks-keyservers.net --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D

See the section above on Download Verification for details on what to do with these keys to verify that a downloaded file is official.

Previous releases of Node.js have been signed with one of the following GPG keys:

About

Tool for runtime execution of node applications using Javascript.

Resources

Readme

License

View license
Activity
Custom properties

Stars

0 stars

Watchers

0 watching

Forks

2 forks
Report repository

Releases

No releases published

Packages

No packages published

Languages