webcrypto 包为 Flutter 提供了跨平台的 Web Cryptography API 实现,可在 Android、iOS、Web、macOS、Windows 和 Linux 上实现安全的加密操作,如密钥生成、加密、解密和数字签名。该包提供了一致的接口,与基于浏览器的 Web Crypto API 相似,使在 Flutter 应用中实现安全数据处理更加容易。对于需要强大安全功能而无需编写特定于平台代码的应用程序,该包特别有用。该包由 Google 维护,并在 GitHub 上开源。
适合场景
安全数据加密
数字签名验证
密钥管理
跨平台加密
安全的令牌处理
主要特点
跨平台兼容性
符合 Web Crypto API 规范
支持对称和非对称加密
开源并由 Google 维护
无需原生代码
适合对象
需要安全数据存储的应用程序
认证系统
安全通信协议
注重隐私的应用程序
熟悉 Web Crypto API 的开发人员
使用建议
需要理解密码学概念
不适合高性能加密密集型工作负载
依赖于 Dart 的异步模型
仅限标准 Web Crypto 算法
可能需要额外的验证才能用于生产环境
原始 README
以下为关联源码仓库的 README 原文快照,最新内容请访问源码仓库。
Cross-Platform Web Cryptography Implementation
This package provides a cross-platform implementation of the
Web Cryptography API.
Disclaimer: This is not an officially supported Google product.
This packages provides an implementation of the
Web Cryptography API across multiple platforms. Outside the
browser, this package features a native implementation embedding
BoringSSL using dart:ffi. When used inside a
web browser this package wraps the window.crypto APIs and
providing the same Dart API as the native implementation.
This way, package:webcrypto provides the same crypto API on Android, iOS, Web, Windows, Linux and Mac.
BoringSSL, Chrome and Firefox implementations pass the same test cases.
Missing:
Exceptions and errors thrown for invalid input is not tested yet.
The native implementation executes on the main-thread, however, all expensive
APIs are asynchronous, so they can be offloaded in the future.
For a discussion of the API design of this package,
see doc/design-rationale-md.
System dependencies
When you have a dependency on package:webcrypto, it will use
hooks to build BoringSSL. Thus, your system
must have:
cmake, and,
a C compiler (like gcc or clang)
Limitations
This package has a few limitations compared to the
Web Cryptography API. For a discussion of parity with
Web Cryptography APIs see doc/webcrypto-parity.md.
deriveKey is not supported, however, keys can always be created from
derivedBits which is supported.
wrapKey is not supported, however, keys can be exported and encrypted.
unwrapKey is not supported, however, keys can be decrypted and imported.
AES-KW is not supported because it does not support encrypt/decrypt.
Compatibility notes
This package has many tests cases to asses compatibility across the native
implementation using BoringSSL and various browser implementations of the
Web Cryptography APIs.
At the moment compatibility testing is limited to native implementation,
Chrome, Firefox and Safari.
Known Issues:
Chrome and BoringSSL does not support valid ECDH spki-formatted keys exported
by Firefox prior to version 72.
Firefox does not support PKCS8 import/export for ECDSA and ECDH keys.
Firefox does not handle counter wrap around for AES-CTR.
Safari does not support P-521 for ECDSA and ECDH.
The browser implementation of streaming methods for encryption,
decryption, signing and verification buffers the entire input, because
window.crypto does not expose a streaming API. However, the native
implementation using BoringSSL does support streaming.
In browsers, operations backed by window.crypto.subtle require a secure
context. When loaded from an insecure context, package:webcrypto throws
UnsupportedError for those operations with guidance to use HTTPS or a
trustworthy local origin such as localhost. fillRandomBytes() continues
to work because it uses window.crypto.getRandomValues(), which browsers
expose outside secure contexts.