-
-
Notifications
You must be signed in to change notification settings - Fork 56
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
1 addition
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,18 +1,4 @@ | ||
browserify-sign [![Build Status](https://travis-ci.org/crypto-browserify/browserify-sign.svg)](https://travis-ci.org/crypto-browserify/browserify-sign) | ||
=== | ||
|
||
a package to duplicate the functionality of node's crypto public key functions, much of this is based on [Fedor Indutny's](https://github.com/indutny) work on [tls.js](https://github.com/indutny/tls.js). | ||
|
||
# done | ||
|
||
- basic rsa signing and verifying with the right api | ||
|
||
# todo | ||
|
||
- ~~tests to make sure we actually did it~~ | ||
- ~~chinese remainder theorom?~~ | ||
- ~~eliptical curve signing~~ | ||
- ~~publicEncrypt and privateDecrypt?~~ (out of scope) | ||
- ~~other key encodings (non rss format public keys)~~ | ||
- dsa keys? | ||
- ~~keys with passwords~~ | ||
A package to duplicate the functionality of node's crypto public key functions, much of this is based on [Fedor Indutny's](https://github.com/indutny) work on [tls.js](https://github.com/indutny/tls.js). |
dd76c98
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@calvinmetcalf, is it worth putting any information here?
dd76c98
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe a note that due to api compatability issues we don't use the native crypto api?