Releases: VirgilSecurity/virgil-crypto-javascript
v4.0.0-alpha.5
August 27, 2019
Interfaces and types in crypto-types package were updated as well as all packages that depend on it.
v4.0.0-alpha.4
August 22, 2019
Fixed
toBuffer
function in@virgilsecurity/data-utils
package. Now it works properly when passed argument is an ArrayBuffer's view.
v4.0.0-alpha.3
August 21, 2019
Introducing new package @virgilsecurity/crypto-types
. The package contains all crypto interfaces to use in other Virgil Security JavaScript libraries. As a bonus, you can create your own type-safe implementation of crypto library based on it.
v4.0.0-alpha.2
August 20, 2019
Fixed
Got rid of the requirement to include node: false
in the webpack.config
of the client apps.
v4.0.0-alpha.1
August 15, 2019
Fixed
- Performance problems in
decrypt*
methods. - Backward compatibility with version 3.x of this library by accepting strings where binary data is expected, e.g. this:
is now allowed, and is functionally equivalent to:
virgilCrypto.encrypt('hello world', myPublicKey);
The assumptions about encoding of the passed string are the same as they were in v3.x and differ from onevirgilCrypto.encrypt({ value: 'hello world', encoding: 'utf8' }, myPublicKey);
method to another. Please consult the source code when in doubt.
v4.0.0-alpha.0
August 9, 2019
Virgil JavaScript Crypto library based on virgil-crypto-c. The library supports WebAssembly as well as asm.js for old browsers.
We improved performance dramatically and decreased bundle size, preserving mostly the same API.
Try it now:
npm install virgil-crypto@next
v3.2.6
June 6, 2019
Fixed
Updated dependencies with potential security vulnerabilities
v3.2.5
May 28, 2019
Fixed
Memory leaks caused by deferred memory deallocation
v3.2.4
May 20, 2019
Fixed
ReactNative support that was accidentally broken in v3.2.2