Skip to content
This repository has been archived by the owner on Jul 15, 2019. It is now read-only.

release v0.1 #78

Open
wants to merge 170 commits into
base: master
Choose a base branch
from
Open

release v0.1 #78

wants to merge 170 commits into from

Conversation

adon-at-work
Copy link
Contributor

@maditya, this branch is the most updated one, and is ready to be deployed to the alpha channel.
please have a quick look and let's get this pushed out.

adon added 22 commits January 13, 2016 11:34
no more gmonkeystub.js
- restrict to yahoo email lookup for now
- expect empty existing index and entry hash in tree proof
- use “25519” as the default key name
- skipped verifying the old key when updating a new key
- refused to generate key when there’s an existing private key
with PASSPHRASE_ENCRYPTION_LINK disabled for now
- asynchronously check chip validity once a recipient is entered
- support per message passphrase encryption
@adon-at-work adon-at-work force-pushed the v0.1.1 branch 3 times, most recently from 63e4a92 to f95dbed Compare February 23, 2016 06:36
bemasc added 3 commits April 21, 2016 10:47
Previously, the benchmark code would run all benchmarks in parallel, resulting in pathological results when mixing synchronous and asynchronous benchmarks.
-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=119373860
This lets e2e use WebCrypto inside a Web Worker, and also preserves Closure typechecking.
-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=119675116
With this change:
 * Keys generated with WebCrypto will be have location == WEB_CRYPTO
 * These keys can be saved to the keyring
 * When loaded from the keyring, these keys will have location == JAVASCRIPT
 * If e2e is compiled with nonstandard flags, all operations on JAVASCRIPT P-256 keys can be performed using WebCrypto
-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=119746227
@yahoocla
Copy link

CLA is valid!

@adon-at-work adon-at-work force-pushed the v0.1.1 branch 2 times, most recently from bcaa263 to 77e1e0e Compare May 10, 2016 05:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants