Crypto browserify, crypto browserify.

Crypto browserify

Crypto is extra serious so please do not hesitate to review the code, and post comments if you do.

Best forex bonuses now

Here is the subset that is currently implemented:

Crypto-browserify

A port of node's crypto module to the browser.

The goal of this module is to reimplement node's crypto module, in pure javascript so that it can run in the browser.

Here is the subset that is currently implemented:

• Createhash (sha1, sha224, sha256, sha384, sha512, md5, rmd160)


• Createhmac (sha1, sha224, sha256, sha384, sha512, md5, rmd160)


• Pbkdf2


• Pbkdf2sync


• Randombytes


• Pseudorandombytes


• Createcipher (aes)


• Createdecipher (aes)


• Creatediffiehellman


• Createsign (rsa, ecdsa)


• Createverify (rsa, ecdsa)


• Createecdh (secp256k1)


• Publicencrypt/privatedecrypt (rsa)


• Privateencrypt/publicdecrypt (rsa)

These features from node's crypto are still unimplemented.

• Createcredentials

Contributions

If you are interested in writing a feature, please implement as a new module, which will be incorporated into crypto-browserify as a dependency.

All deps must be compatible with node's crypto (generate example inputs and outputs with node, and save base64 strings inside JSON, so that tests can run in the browser. See sha.Js

Crypto is extra serious so please do not hesitate to review the code, and post comments if you do.

License

Current tags

75 versions

• 3.12.0 . 3 years ago


• 3.11.1 . 4 years ago


• 3.11.0 . 5 years ago


• 3.10.0 . 5 years ago


• 3.9.14 . 6 years ago


• 3.9.13 . 6 years ago


• 3.9.12 . 6 years ago


• 3.9.11 . 6 years ago


• 3.9.10 . 6 years ago


• 3.9.9 . 6 years ago


• 3.9.8 . 6 years ago


• 3.9.7 . 6 years ago


• 3.9.6 . 6 years ago


• 3.9.4 . 6 years ago


• 3.9.3 . 6 years ago


• 3.9.2 . 6 years ago


• 3.9.1 . 6 years ago


• 3.9.0 . 6 years ago


• 3.8.3 . 6 years ago


• 3.8.1 . 6 years ago


• 3.8.0 . 6 years ago


• 3.7.2 . 6 years ago


• 3.7.1 . 6 years ago


• 3.7.0 . 6 years ago


• 3.6.0 . 6 years ago


• 3.5.1 . 6 years ago


• 3.5.0 . 6 years ago


• 3.4.3 . 6 years ago


• 3.4.1 . 6 years ago


• 3.4.0 . 6 years ago


• 3.3.0 . 6 years ago


• 3.2.8 . 6 years ago


• 3.2.7 . 6 years ago


• 3.2.6 . 6 years ago


• 3.2.5 . 6 years ago


• 3.2.4 . 6 years ago


• 3.2.2 . 6 years ago


• 3.2.1 . 6 years ago


• 3.2.0 . 6 years ago


• 3.1.0 . 6 years ago


• 3.0.2 . 6 years ago


• 3.0.1 . 6 years ago


• 3.0.0 . 6 years ago


• 2.1.10 . 6 years ago


• 2.1.8 . 7 years ago


• 2.1.7 . 7 years ago


• 2.1.6 . 7 years ago


• 2.1.5 . 7 years ago


• 2.1.4 . 7 years ago


• 2.1.3 . 7 years ago


• 2.1.2 . 7 years ago


• 2.1.1 . 7 years ago


• 2.1.0 . 7 years ago


• 2.0.0 . 7 years ago


• 1.0.9 . 7 years ago


• 1.0.8 . 7 years ago


• 1.0.7 . 7 years ago


• 1.0.6 . 7 years ago


• 1.0.5 . 7 years ago


• 1.0.4 . 7 years ago


• 1.0.3 . 7 years ago


• 1.0.2 . 7 years ago


• 1.0.1 . 7 years ago


• 1.0.0 . 7 years ago


• 0.4.0 . 7 years ago


• 0.3.0 . 7 years ago


• 0.2.3 . 8 years ago


• 0.2.2 . 8 years ago


• 0.2.1 . 8 years ago


• 0.2.0 . 8 years ago


• 0.1.2 . 8 years ago


• 0.1.1 . 8 years ago


• 0.1.0 . 9 years ago


• 0.0.1 . 9 years ago


• 0.0.0 . 9 years ago

• Browserify-cipher ^1.0.0


• Browserify-sign ^4.0.0


• Create-ecdh ^4.0.0


• Create-hash ^1.1.0


• Create-hmac ^1.1.0


• Diffie-hellman ^5.0.0


• Inherits ^2.0.1


• Pbkdf2 ^3.0.3


• Public-encrypt ^4.0.0


• Randombytes ^2.0.0


• Randomfill ^1.0.3

1.3.2

Pseudorandombytes ^2.0.0

Safe-buffer ^5.1.1

Standard ^5.0.2

Tape

Crypto-browserify

Implementation of crypto for the browser

Package health score

Popularity

The npm package crypto-browserify receives a total of 9,374,744 downloads a week. As such, we scored crypto-browserify popularity level to be influential project.

Based on project statistics from the github repository for the npm package crypto-browserify, we found that it has been starred 457 times, and that 682 other projects on the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Security

Security and license risk for significant versions

Version

Release date

Direct vulnerabilities

Indirect vulnerabilities

License risks

You can connect your project's repository to snyk to stay up to date on security alerts and receive automatic fix pull requests.

We found a way for you to contribute to the project! Looks like crypto-browserify is missing a security policy.

Maintenance

Further analysis of the maintenance status of crypto-browserify based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is inactive.

An important project maintenance signal to consider for crypto-browserify is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the github repository had at least 1 pull request or issue interacted with by the community.

Community

With more than 10 contributors for the crypto-browserify repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like crypto-browserify is missing a code of conduct.

Embed package health score badge

Copy markdown

Package

We detected a total of 38 direct & transitive dependencies for crypto-browserify. See the full dependency tree of crypto-browserify

Crypto-browserify has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Crypto-browserify

A port of node's crypto module to the browser.

The goal of this module is to reimplement node's crypto module, in pure javascript so that it can run in the browser.

Here is the subset that is currently implemented:

• Createhash (sha1, sha224, sha256, sha384, sha512, md5, rmd160)


• Createhmac (sha1, sha224, sha256, sha384, sha512, md5, rmd160)


• Pbkdf2


• Pbkdf2sync


• Randombytes


• Pseudorandombytes


• Createcipher (aes)


• Createdecipher (aes)


• Creatediffiehellman


• Createsign (rsa, ecdsa)


• Createverify (rsa, ecdsa)


• Createecdh (secp256k1)


• Publicencrypt/privatedecrypt (rsa)


• Privateencrypt/publicdecrypt (rsa)

These features from node's crypto are still unimplemented.

• Createcredentials

Contributions

If you are interested in writing a feature, please implement as a new module, which will be incorporated into crypto-browserify as a dependency.

All deps must be compatible with node's crypto (generate example inputs and outputs with node, and save base64 strings inside JSON, so that tests can run in the browser. See sha.Js

Crypto is extra serious so please do not hesitate to review the code, and post comments if you do.

Performance of hashing in javascript crypto libraries.

Dominic tarr (stackvm mad science university) 2014-04-04 (v1.1.1)

Abstract

The performance of a cryptography library is not its most important consideration, but performance is still highly important. If performance is too low, it affects the usability, and so less cryptography will be used. In this article, I've compared the performance of the sha hashing functions in several javascript crypto libraries. These have wildly varying performance, and some have non-linear performance characteristics, and there are a few that have dramatically better perfomance.

Method

So far, I have benchmarks for measuring hashing performance against input size, and key derivation performance (pbkdf2) as the number of iterations are increased. Hashing a "large" file measures throughput, while key derivation depends on creating many hashes repeatedly - whether many hashes can be created in succession is quite a different measurement.

Since javascript timers are not very precise, if the time taking to hash is under 100 ms, the hash is repeated until the elapsed time is > 100ms, and the the time taken is adjusted to time_taken/repeated_runs .

All benchmarks where run on a macbook air 11 running archlinux and node@0.10.25

Crypto libraries tested

• Stanford javascript crypto library ( sjcl )


• Crypto-js


• Forge


• Crypto-browserify (I am the author of this module)

These libraries where also benchmarked, but they only implemented some of the features tested.

• Crypto-mx (sha256)


• Git-sha1 (sha1)


• Jshashes (sha1, sha256)


• Rusha (sha1)

Hashing a 0-10MB file

Since each library provides a different API, each api has been wrapped to a function that takes a buffer, and then converts to a format that the algorithm can process, and calls the hash function with one buffer.

Since javascript did not originally include a way to represent binary, some of the older implementations use arrays of numbers or binary strings. This extra step is not necessarily fair on them, however it would be surprising if encoding had more than a small effect on hashing performance.

Sha1, time taken against input size.

(y-axis shows total time taken, lower is better)

Every implementation behaves basically linearly with input size, except that crypto-browserify and git-sha1 becomes more efficient once input size becomes about 2MB. Below 2MB, forge is slightly ahead of crypto-browserify. Rusha is consistently the fastest, although at the low end of this graph it's difficult to see by much. And sjcl , crypto-js , and jshashes are significantly slower as size increases.

Sha1, bytes hashed per millisecond

(y-axis shows size/time, higher is better)

Rusha stands out impressively ahead of all others. Crypto-browserify and git-sha1 are close, and interestingly make a very similar non-linear step at about 2mb input size. Probably this is because they both allocate typed arrays, and that slows them down at low input sizes. A future experiment will be to manage typedarrays with pooling, to make repeated hashes faster.

Looking at this graph it appears that rusha is certainly the best implementation, but there is a significant problem - it is not streaming, so you need to buffer the entire file into memory before hashing it. This is not a problem if you are hashing small files, or few files at a time. But if you need to hash a large number of files at as they arrive it will may be slower, due to being unable to process what has arrived inbetween chunks. This will be the subject of a future experiment.

Crypto-browserify and git-sha1 are both capable of streaming.

It is temping to think of the change in performance as an good thing, but I think it's better to interpret any departure from linear as signs of trouble - or at least room for improvement. Hashing small inputs is very important, since most inputs are probably small.

Sha256, time taken against input size.

(y-axis shows total time taken, lower is better)

Sjcl and crypto-js performance at sha256 seems much the same as for sha1, but forge is faster than crypto-browserify, which doesn't show any improvement with input size.

Sha256, time taken against input size.

(y-axis shows size/time, higher is better)

Forge is clearly faster, and crypto-browserify does not show any improvement. Also note that the performance of both forge and crypto-browserify is over 20k bytes per ms, about the performance of crypto-browserify 's sha1.

An interesting thing here is that crypto-browserify and forge both use very different binary representations. Crypto-browserify uses node.Js buffers (or feross/buffer, a polyfill on top of typedarrays in the browser) where as forge uses binary strings. Binary strings is not expected to be faster than typedarrays, but may have some benefits in copying from one string to another, since strings are immutable, and there is the possibility that v8 is doing something clever here.

Key derivation (pbkdf2)

Pbkdf2(sha1), time taken against iterations.

(y-axis shows total time taken, lower is better)

This graph shows that crypto-js 's pbkdf2 has non-linear performance. Something is clearly wrong, as there is no reason this should not be linear. Compared to crypto-js , the other libraries are not even on this scale.

Pbkdf(sha1), iterations per millisecond.

(y-axis shows size/time, higher is better)

Looking at the iterations per ms, we see that sjcl , which was the slowest on large files, is the fastest with rapid iterations. This suggests that there is something about the crypto-browserify and forge implementations which make the hash objects heavy to create, but efficient once created. If this is correct, they could possibly be improved with pooling, or some other thing to lighten iterations.

Rusha unfortunately does not have a pbkdf2 feature, this could easily be added, and it would be interesting to see if it's performance continues to be impressive.

Pbkdf2(sha256), time taken against iterations.

(y-axis shows total time taken, lower is better)

Again, crypto-js has non-linear scaling.

Pbkdf2(sha256), iterations per millisecond.

(y-axis shows size/time, higher is better)

Interestingly, the relative performance of sjcl is even more impressive, about 4 times greater than sha1 (it's not surprising that sha256 is the default hash algorithm for sjcl)

Hashing small files

(zoomed into bottom left of the earlier hashing bytes/ms graphs)

Is sjcl 's superior pbkdf2 performance due to better performance at small values? If so, we would expect to see the lines cross if we zoomed in on the bottom left corner of the bytes-hashed-per-millisecond graphs.

Sha1 on small inputs (bytes/ms)

(y-axis shows size/time, higher is better)

Sha256 on small inputs (bytes/ms)

(y-axis shows size/time, higher is better)

Sjcl is not faster at pure hashes in small values, therefore, the key to it's performance must be in another aspect of the implementation.

Comparison of fastest hashes.

If you where implementing a new crypto system that must run in the browser, which is the most performant algorithim to use? In this experiment we compare the best implementations of different algorithms.

The fastest sha1 implementation is included in the graph, but only for comparison. Weaknesses have been discovered in sha1, and it should not be used in a new system.

Blake2s is a new algorithm designed specifically to be performant is the fastest implementation. Rusha is close behind it, and forge's sha256 all implementations display nearly completely linear performance.

Future work

By optimizing for the specifics of a key derivation algorithm (i.E. Writing a fixed size input, instead of a variable one) it may be possible to improve iterated hash performance significantly.

It will also be worthwhile running the benchmarks under different javascript engines (browsers)

And prehaps most interesting, would be to construct a realistic benchmark for streaming hashes. Normally, I have observed that buffering is faster if only one file is processed, however if many files are to be processed, then you can process part of the file while waiting for the rest to arrive.

Conclusion

The hash algorithms in sjcl, crypto-browserify, and forge, have been optimized for different purposes. It appears that crypto-js hasn't been optimized, after the correctness of the implementation has been verified.

Crypto-browserify

A port of node's crypto module to the browser.

The goal of this module is to reimplement node's crypto module, in pure javascript so that it can run in the browser.

Here is the subset that is currently implemented:

• Createhash (sha1, sha224, sha256, sha384, sha512, md5, rmd160)


• Createhmac (sha1, sha224, sha256, sha384, sha512, md5, rmd160)


• Pbkdf2


• Pbkdf2sync


• Randombytes


• Pseudorandombytes


• Createcipher (aes)


• Createdecipher (aes)


• Creatediffiehellman


• Createsign (rsa, ecdsa)


• Createverify (rsa, ecdsa)


• Createecdh (secp256k1)


• Publicencrypt/privatedecrypt (rsa)


• Privateencrypt/publicdecrypt (rsa)

These features from node's crypto are still unimplemented.

• Createcredentials

Contributions

If you are interested in writing a feature, please implement as a new module, which will be incorporated into crypto-browserify as a dependency.

All deps must be compatible with node's crypto (generate example inputs and outputs with node, and save base64 strings inside JSON, so that tests can run in the browser. See sha.Js

Crypto is extra serious so please do not hesitate to review the code, and post comments if you do.

License

Current tags

75 versions

• 3.12.0 . 3 years ago


• 3.11.1 . 4 years ago


• 3.11.0 . 5 years ago


• 3.10.0 . 5 years ago


• 3.9.14 . 6 years ago


• 3.9.13 . 6 years ago


• 3.9.12 . 6 years ago


• 3.9.11 . 6 years ago


• 3.9.10 . 6 years ago


• 3.9.9 . 6 years ago


• 3.9.8 . 6 years ago


• 3.9.7 . 6 years ago


• 3.9.6 . 6 years ago


• 3.9.4 . 6 years ago


• 3.9.3 . 6 years ago


• 3.9.2 . 6 years ago


• 3.9.1 . 6 years ago


• 3.9.0 . 6 years ago


• 3.8.3 . 6 years ago


• 3.8.1 . 6 years ago


• 3.8.0 . 6 years ago


• 3.7.2 . 6 years ago


• 3.7.1 . 6 years ago


• 3.7.0 . 6 years ago


• 3.6.0 . 6 years ago


• 3.5.1 . 6 years ago


• 3.5.0 . 6 years ago


• 3.4.3 . 6 years ago


• 3.4.1 . 6 years ago


• 3.4.0 . 6 years ago


• 3.3.0 . 6 years ago


• 3.2.8 . 6 years ago


• 3.2.7 . 6 years ago


• 3.2.6 . 6 years ago


• 3.2.5 . 6 years ago


• 3.2.4 . 6 years ago


• 3.2.2 . 6 years ago


• 3.2.1 . 6 years ago


• 3.2.0 . 6 years ago


• 3.1.0 . 6 years ago


• 3.0.2 . 6 years ago


• 3.0.1 . 6 years ago


• 3.0.0 . 6 years ago


• 2.1.10 . 6 years ago


• 2.1.8 . 7 years ago


• 2.1.7 . 7 years ago


• 2.1.6 . 7 years ago


• 2.1.5 . 7 years ago


• 2.1.4 . 7 years ago


• 2.1.3 . 7 years ago


• 2.1.2 . 7 years ago


• 2.1.1 . 7 years ago


• 2.1.0 . 7 years ago


• 2.0.0 . 7 years ago


• 1.0.9 . 7 years ago


• 1.0.8 . 7 years ago


• 1.0.7 . 7 years ago


• 1.0.6 . 7 years ago


• 1.0.5 . 7 years ago


• 1.0.4 . 7 years ago


• 1.0.3 . 7 years ago


• 1.0.2 . 7 years ago


• 1.0.1 . 7 years ago


• 1.0.0 . 7 years ago


• 0.4.0 . 7 years ago


• 0.3.0 . 7 years ago


• 0.2.3 . 8 years ago


• 0.2.2 . 8 years ago


• 0.2.1 . 8 years ago


• 0.2.0 . 8 years ago


• 0.1.2 . 8 years ago


• 0.1.1 . 8 years ago


• 0.1.0 . 9 years ago


• 0.0.1 . 9 years ago


• 0.0.0 . 9 years ago

• Browserify-cipher ^1.0.0


• Browserify-sign ^4.0.0


• Create-ecdh ^4.0.0


• Create-hash ^1.1.0


• Create-hmac ^1.1.0


• Diffie-hellman ^5.0.0


• Inherits ^2.0.1


• Pbkdf2 ^3.0.3


• Public-encrypt ^4.0.0


• Randombytes ^2.0.0


• Randomfill ^1.0.3

1.3.2

Pseudorandombytes ^2.0.0

Safe-buffer ^5.1.1

Standard ^5.0.2

Tape

Crypto-browserify
tag v3.9.1

Partial implementation of node's `crypto` for the browser

License MIT install bower install crypto-browserify#v3.9.1

Sourcerank 12

Documentation

A port of node's crypto module to the browser.

The goal of this module is to reimplement node's crypto module, in pure javascript so that it can run in the browser.

Here is the subset that is currently implemented:

• Createhash (sha1, sha224, sha256, sha384, sha512, md5, rmd160)


• Createhmac (sha1, sha224, sha256, sha384, sha512, md5, rmd160)


• Pbkdf2


• Pbkdf2sync


• Randombytes


• Pseudorandombytes


• Createcipher (aes)


• Createdecipher (aes)


• Creatediffiehellman


• Createsign (rsa, ecdsa)


• Createverify (rsa, ecdsa)


• Createecdh (secp256k1)


• Publicencrypt/privatedecrypt (rsa)


• Privateencrypt/publicdecrypt (rsa)

These features from node's crypto are still unimplemented.

• Createcredentials

If you are interested in writing a feature, please implement as a new module, which will be incorporated into crypto-browserify as a dependency.

All deps must be compatible with node's crypto (generate example inputs and outputs with node, and save base64 strings inside JSON, so that tests can run in the browser. See sha.Js

Crypto is extra serious so please do not hesitate to review the code, and post comments if you do.

Crypto-browserify
tag v3.9.1

Partial implementation of node's `crypto` for the browser

License MIT install bower install crypto-browserify#v3.9.1

Sourcerank 12

Documentation

A port of node's crypto module to the browser.

The goal of this module is to reimplement node's crypto module, in pure javascript so that it can run in the browser.

Here is the subset that is currently implemented:

• Createhash (sha1, sha224, sha256, sha384, sha512, md5, rmd160)


• Createhmac (sha1, sha224, sha256, sha384, sha512, md5, rmd160)


• Pbkdf2


• Pbkdf2sync


• Randombytes


• Pseudorandombytes


• Createcipher (aes)


• Createdecipher (aes)


• Creatediffiehellman


• Createsign (rsa, ecdsa)


• Createverify (rsa, ecdsa)


• Createecdh (secp256k1)


• Publicencrypt/privatedecrypt (rsa)


• Privateencrypt/publicdecrypt (rsa)

These features from node's crypto are still unimplemented.

• Createcredentials

If you are interested in writing a feature, please implement as a new module, which will be incorporated into crypto-browserify as a dependency.

All deps must be compatible with node's crypto (generate example inputs and outputs with node, and save base64 strings inside JSON, so that tests can run in the browser. See sha.Js

Crypto is extra serious so please do not hesitate to review the code, and post comments if you do.

Crypto browserify

• Accounting


• Ajax-framework


• Application-framework


• Audio-editor


• Automation


• Big-data


• Blog-engine


• Browser


• Build-tool


• Business-process-management


• Cache


• Charting-library


• Chat-server


• Code-coverage


• Collaboration


• Column-database


• Document-management


• Data-extraction


• Database


• E-commerce


• Email-client


• Embedded-database


• Enterprise-search


• Erp


• Facebook-alternative


• Faq-system


• Finance


• Forum-software


• Ftp


• Full-text-search


• Game-engine


• Geocoding


• Git


• Graph-database


• Healthcare-information-system


• Helpdesk


• Html-parser


• Html-to-text


• Human-resource-management


• Identity-management


• Image-compression


• Information-retrieval


• Instant-messaging


• Intrusion-detection-system


• Issue-tracking


• Java-framework


• Java-games


• Jquery-plugin


• Json


• Jvm


• Key-management


• Key-value-store


• Language-detection


• Linux-operating-system


• Linux-tools


• Log-analysis


• Mail-client


• Mail-server


• Mailing-list


• Media-player


• Media-server


• Message-queue


• Micro-blogging


• Mobile-framework


• Natural-language-processing


• Network-management


• Networking-library


• Neural-network


• No-sql


• Nodejs


• Oauth


• Object-database


• Ocr


• Office-suite


• Online-shopping


• Operating-system


• Orm


• Package-manager


• Pdf-library


• Personnel-finance


• Photo-management


• Programming-language


• Proxy-server


• Qa-tools


• Qr-code


• Question


• Records-management


• Relational-database


• Reporting-tool


• Rrdtool


• School-management


• Screen-capture


• Search-engine


• Server-monitoring


• Shopping-cart


• Skype-alternative


• Sms-library


• Social-networking


• Testing-tool


• Text-extraction


• Text-to-speech


• Ticketing


• Twitter-client


• Ubuntu-fork


• Uml-tool


• Unit-testing


• Url-shortning-service


• Version-control


• Video-cms


• Video-conference


• Video-player


• Virtualization


• Visualization


• Voip-server


• Vpn


• Web-analytics


• Web-application-framework


• Web-browser


• Webcrawler


• Webserver


• Wysiwyg-editor


• Xml-parser


• Xmpp


• Xps-viewer


• Zip


• Zlib

Createecdh - browserify version of crypto.Createecdh

In io.Js or node >= 0.11 this module is just a shortcut to crypto.Createecdh. In node

tags	diffie hellman diffiehellman ecdh
implementation	javascript
license	MIT
platform	OS-independent

Related projects

Diffie-hellman_backdoor - how to backdoor diffie-hellman

The whitepaper is on eprint.

Telehash-js - telehash javascript module for node.Js and browserify

This module presents a simple high-level API for using telehash v3 for both node and browserify. The browser crypto that powers this is only possible thanks to the incredible work done by the team behind forge, tom wu, and the sanford javascript crypto library.

Python cryptographic toolkit

Cryptkit is a small, fast cryptographic toolkit for python. It implements rijndael(AES), SHA 256, elliptic curve PKI, diffie-hellman key exchange and nyberg-ruppel signature/verification. Comprehensive enough to provide a secure socket alternative to SSL

Docker-letsencrypt-nginx-proxy-companion - letsencrypt companion container for nginx-proxy

Letsencrypt-nginx-proxy-companion is a lightweight companion container for the nginx-proxy. It allows the creation/renewal of let's encrypt certificates automatically. See let's encrypt section for configuration details.NOTE: the first time this container is launched it generates a new diffie-hellman group file. This process can take several minutes to complete (be patient).

Empyre - A post-exploitation OS X/linux agent written in python 2.7

Empyre is a pure python post-exploitation agent built on cryptologically-secure communications and a flexible architecture. It is based heavily on the controller and communication structure of empire. The diffie hellman implementation is from mark loiseau's project here, licensed under version 3.0 of the GNU general public license.

Bee2 - A cryptographic library

Bee2 is a cryptographic library which implements cryptographic algorithm and protocols standardized in belarus. Additionally, bee2 implements digital signature algorithms standardized in russia and ukraine.

Crypto-browserify - partial implementation of node's `crypto` for the browser

A port of node's crypto module to the browser. The goal of this module is to reimplement node's crypto module, in pure javascript so that it can run in the browser.

Themis - crypto library for storage and messaging for objc, android, C++, JS, python, ruby and PHP

Themis is open-source high-level cryptographic services library for mobile and server platforms, providing secure messaging and secure data storage. Themis provides three important cryptographic services secure messaging, secure session and secure storage.

Ring - safe, fast, small crypto using rust

Ring is focused on the implementation, testing, and optimization of a core set of cryptographic operations exposed via an easy-to-use (and hard-to-misuse) API. Ring exposes a rust API and is written in a hybrid of rust, C, and assembly language. Ring is focused on general-purpose cryptography. Webpki X.509 certificate validation is done in the webpki project, which is built on top of ring. Also, multiple groups are working on implementations of cryptographic protocols like TLS, SSH, and DNSSEC on top of ring.

Node-rsa - node.Js RSA library

This library developed and tested primary for node.Js, but it still can work in browsers with browserify. You can specify some options by second/third constructor argument, or over key.Setoptions() method.

Browserify-shim - �� makes commonjs incompatible files browserifyable.

For a version compatible with browserify@1.X run npm install browserify-shim@1.X instead. For a version compatible with the v2 API npm install browserify-shim@2.X instead.

Karma-browserify - A fast browserify integration for karma that handles large projects with ease

Karma-browserify is a fast browserify integration for karma that handles large projects with ease. Get the plug-in via npm.

Livereactload - live code editing with browserify and react

Live code editing with browserify and react. Hot reloading is de facto in today's front-end scene but unfortunately there isn't any decent implementation for browserify yet. This is shame because (in my opinion) browserify is the best bundling tool at the moment.

Featherduster - an automated, modular cryptanalysis tool; i.E., a weapon of math destruction

Featherduster is a tool written by daniel "unicornfurnace" crowley of NCC group for breaking crypto which tries to make the process of identifying and exploiting weak cryptosystems as easy as possible. Cryptanalib is the moving parts behind featherduster, and can be used independently of featherduster. Why "featherduster"? There's an in-joke amongst some crypto folk where using crypto poorly, or to solve a problem that crypto isn't meant to solve is called "sprinkling magical crypto fairy dust on it". Featherduster is for cleaning up magical crypto fairy dust.

Debowerify - A browserify transform to enable the easy use of bower components in browserify client javascript projects

A browserify transform to enable the easy use of bower components in browserify client javascript projects. This can be used in conjunction with deamdify to require AMD components from bower as well.

Css-modulesify - A browserify plugin to load CSS modules

A browserify plugin to load CSS modules. Please note that this is still highly experimental.

Browserify-hmr - hot module replacement plugin for browserify

Open http://localhost:8080/ and try updating label.Jsx and interval.Js. Hot module replacement works by re-executing updated modules. The hot module replacement API must be used to define which modules can accept updates, and what to do when a module is going to be updated.

Grunt-browserify - grunt task for node-browserify

Grunt task for node-browserify. This plugin requires grunt

Tsify - browserify plugin for compiling typescript

Note that when using the browserify CLI, compilation will always halt on the first error encountered, unlike the regular typescript CLI. This behavior can be overridden in the API, as shown in the API example. Also note that the square brackets [ ] in the example above are required if you want to pass parameters to tsify; they don't denote an optional part of the command.

Sheetify - :sparkles: modular CSS bundler for browserify

Modular CSS bundler for browserify. Works with npm modules like browserify does. Sheetify is very good for namespacing static css assets in your javascript code. Currently there is no support for dynamic variables within sheetify, however you could achieve this by setting the inline style property of an element.

Crypto browserify

• Accounting


• Ajax-framework


• Application-framework


• Audio-editor


• Automation


• Big-data


• Blog-engine


• Browser


• Build-tool


• Business-process-management


• Cache


• Charting-library


• Chat-server


• Code-coverage


• Collaboration


• Column-database


• Document-management


• Data-extraction


• Database


• E-commerce


• Email-client


• Embedded-database


• Enterprise-search


• Erp


• Facebook-alternative


• Faq-system


• Finance


• Forum-software


• Ftp


• Full-text-search


• Game-engine


• Geocoding


• Git


• Graph-database


• Healthcare-information-system


• Helpdesk


• Html-parser


• Html-to-text


• Human-resource-management


• Identity-management


• Image-compression


• Information-retrieval


• Instant-messaging


• Intrusion-detection-system


• Issue-tracking


• Java-framework


• Java-games


• Jquery-plugin


• Json


• Jvm


• Key-management


• Key-value-store


• Language-detection


• Linux-operating-system


• Linux-tools


• Log-analysis


• Mail-client


• Mail-server


• Mailing-list


• Media-player


• Media-server


• Message-queue


• Micro-blogging


• Mobile-framework


• Natural-language-processing


• Network-management


• Networking-library


• Neural-network


• No-sql


• Nodejs


• Oauth


• Object-database


• Ocr


• Office-suite


• Online-shopping


• Operating-system


• Orm


• Package-manager


• Pdf-library


• Personnel-finance


• Photo-management


• Programming-language


• Proxy-server


• Qa-tools


• Qr-code


• Question


• Records-management


• Relational-database


• Reporting-tool


• Rrdtool


• School-management


• Screen-capture


• Search-engine


• Server-monitoring


• Shopping-cart


• Skype-alternative


• Sms-library


• Social-networking


• Testing-tool


• Text-extraction


• Text-to-speech


• Ticketing


• Twitter-client


• Ubuntu-fork


• Uml-tool


• Unit-testing


• Url-shortning-service


• Version-control


• Video-cms


• Video-conference


• Video-player


• Virtualization


• Visualization


• Voip-server


• Vpn


• Web-analytics


• Web-application-framework


• Web-browser


• Webcrawler


• Webserver


• Wysiwyg-editor


• Xml-parser


• Xmpp


• Xps-viewer


• Zip


• Zlib

Createecdh - browserify version of crypto.Createecdh

In io.Js or node >= 0.11 this module is just a shortcut to crypto.Createecdh. In node

tags	diffie hellman diffiehellman ecdh
implementation	javascript
license	MIT
platform	OS-independent

Related projects

Diffie-hellman_backdoor - how to backdoor diffie-hellman

The whitepaper is on eprint.

Telehash-js - telehash javascript module for node.Js and browserify

This module presents a simple high-level API for using telehash v3 for both node and browserify. The browser crypto that powers this is only possible thanks to the incredible work done by the team behind forge, tom wu, and the sanford javascript crypto library.

Python cryptographic toolkit

Cryptkit is a small, fast cryptographic toolkit for python. It implements rijndael(AES), SHA 256, elliptic curve PKI, diffie-hellman key exchange and nyberg-ruppel signature/verification. Comprehensive enough to provide a secure socket alternative to SSL

Docker-letsencrypt-nginx-proxy-companion - letsencrypt companion container for nginx-proxy

Letsencrypt-nginx-proxy-companion is a lightweight companion container for the nginx-proxy. It allows the creation/renewal of let's encrypt certificates automatically. See let's encrypt section for configuration details.NOTE: the first time this container is launched it generates a new diffie-hellman group file. This process can take several minutes to complete (be patient).

Empyre - A post-exploitation OS X/linux agent written in python 2.7

Empyre is a pure python post-exploitation agent built on cryptologically-secure communications and a flexible architecture. It is based heavily on the controller and communication structure of empire. The diffie hellman implementation is from mark loiseau's project here, licensed under version 3.0 of the GNU general public license.

Bee2 - A cryptographic library

Bee2 is a cryptographic library which implements cryptographic algorithm and protocols standardized in belarus. Additionally, bee2 implements digital signature algorithms standardized in russia and ukraine.

Crypto-browserify - partial implementation of node's `crypto` for the browser

A port of node's crypto module to the browser. The goal of this module is to reimplement node's crypto module, in pure javascript so that it can run in the browser.

Themis - crypto library for storage and messaging for objc, android, C++, JS, python, ruby and PHP

Themis is open-source high-level cryptographic services library for mobile and server platforms, providing secure messaging and secure data storage. Themis provides three important cryptographic services secure messaging, secure session and secure storage.

Ring - safe, fast, small crypto using rust

Ring is focused on the implementation, testing, and optimization of a core set of cryptographic operations exposed via an easy-to-use (and hard-to-misuse) API. Ring exposes a rust API and is written in a hybrid of rust, C, and assembly language. Ring is focused on general-purpose cryptography. Webpki X.509 certificate validation is done in the webpki project, which is built on top of ring. Also, multiple groups are working on implementations of cryptographic protocols like TLS, SSH, and DNSSEC on top of ring.

Node-rsa - node.Js RSA library

This library developed and tested primary for node.Js, but it still can work in browsers with browserify. You can specify some options by second/third constructor argument, or over key.Setoptions() method.

Browserify-shim - �� makes commonjs incompatible files browserifyable.

For a version compatible with browserify@1.X run npm install browserify-shim@1.X instead. For a version compatible with the v2 API npm install browserify-shim@2.X instead.

Karma-browserify - A fast browserify integration for karma that handles large projects with ease

Karma-browserify is a fast browserify integration for karma that handles large projects with ease. Get the plug-in via npm.

Livereactload - live code editing with browserify and react

Live code editing with browserify and react. Hot reloading is de facto in today's front-end scene but unfortunately there isn't any decent implementation for browserify yet. This is shame because (in my opinion) browserify is the best bundling tool at the moment.

Featherduster - an automated, modular cryptanalysis tool; i.E., a weapon of math destruction

Featherduster is a tool written by daniel "unicornfurnace" crowley of NCC group for breaking crypto which tries to make the process of identifying and exploiting weak cryptosystems as easy as possible. Cryptanalib is the moving parts behind featherduster, and can be used independently of featherduster. Why "featherduster"? There's an in-joke amongst some crypto folk where using crypto poorly, or to solve a problem that crypto isn't meant to solve is called "sprinkling magical crypto fairy dust on it". Featherduster is for cleaning up magical crypto fairy dust.

Debowerify - A browserify transform to enable the easy use of bower components in browserify client javascript projects

A browserify transform to enable the easy use of bower components in browserify client javascript projects. This can be used in conjunction with deamdify to require AMD components from bower as well.

Css-modulesify - A browserify plugin to load CSS modules

A browserify plugin to load CSS modules. Please note that this is still highly experimental.

Browserify-hmr - hot module replacement plugin for browserify

Open http://localhost:8080/ and try updating label.Jsx and interval.Js. Hot module replacement works by re-executing updated modules. The hot module replacement API must be used to define which modules can accept updates, and what to do when a module is going to be updated.

Grunt-browserify - grunt task for node-browserify

Grunt task for node-browserify. This plugin requires grunt

Tsify - browserify plugin for compiling typescript

Note that when using the browserify CLI, compilation will always halt on the first error encountered, unlike the regular typescript CLI. This behavior can be overridden in the API, as shown in the API example. Also note that the square brackets [ ] in the example above are required if you want to pass parameters to tsify; they don't denote an optional part of the command.

Sheetify - :sparkles: modular CSS bundler for browserify

Modular CSS bundler for browserify. Works with npm modules like browserify does. Sheetify is very good for namespacing static css assets in your javascript code. Currently there is no support for dynamic variables within sheetify, however you could achieve this by setting the inline style property of an element.

Пакет: node-crypto-browserify (3.12.0-3)

Ссылки для node-crypto-browserify

Ресурсы debian:

Исходный код node-crypto-browserify:

Сопровождающие:

Внешние ресурсы:

Подобные пакеты:

• Node-loader-runner


• Node-schema-utils


• Node-path-browserify


• Node-querystring-es3


• Node-libs-browser


• Node-source-list-map


• Node-delegates


• Node-memory-fs


• Node-css-selector-tokenizer


• Node-acorn-dynamic-import


• Node-json-loader

Implementation of crypto for the browser

This library is an implementation of node's crypto for the browser.

This library is a dependency for webpack. Webpack takes code targeted at node.Js and makes it run in the browser. Node.Js comes with API of its own that is not available in the browsers. Webpack exposes this code to programs that are unaware they are running in a browser.

Node.Js is an event-based server-side javascript engine.

Другие пакеты, относящиеся к node-crypto-browserify

Загрузка node-crypto-browserify

загрузить для всех доступных архитектур

архитектура	размер пакета	В установленном виде	файлы
all	5,2 кб	20,0 кб	[список файлов]

Эта страница также доступна на следующих языках (как установить язык по умолчанию):

Чтобы сообщить о проблеме, связанной с веб-сайтом, отправьте сообщение (на английском) в список рассылки debian-www@lists.Debian.Org. Прочую контактную информацию см. На странице debian как с нами связаться.

Авторские права © 1997 - 2021 SPI inc.; см. Условия лицензии. Debian это торговый знак компании SPI inc. Об этом сайте.

So, let's see, what we have: crypto-browserify A port of node's crypto module to the browser. The goal of this module is to reimplement node's crypto module, in pure javascript so that it can run in the browser. At crypto browserify