You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: bump version to 9.0.1 and update documentation
This commit bumps the version from 9.0.0 to 9.0.1 across the plugin and all example applications. It also includes significant documentation updates and a dependency maintenance.
### Documentation
- **Biometric Decryption**: Added a new section to `README.md` describing the decryption lifecycle, accompanied by a process diagram.
- **Windows Integration**: Clarified platform-specific details for Windows Hello, including the use of `KeyCredentialManager`, TPM backing, and the RSA-2048 constraint.
- **Metadata**: Updated `pubspec.yaml` description to explicitly mention support for Android, iOS, macOS, and Windows.
### Maintenance
- **Android**: Updated `androidx.biometric:biometric` dependency from `1.4.0-alpha04` to `1.4.0-alpha05`.
- **Version Bump**: Updated version strings in `pubspec.yaml`, `pubspec.lock` files, podspecs, and the example app's UI.
- **Assets**: Added `usecase-2.jpeg` to support new documentation.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,10 @@
1
+
## [9.0.1] - 2025-12-21
2
+
3
+
***Feature:** Added "Biometric Decryption" section to `README.md` with a detailed lifecycle diagram (`usecase-2.png`) and process description.
4
+
***Improved:** Enhanced Windows platform documentation to clarify `KeyCredentialManager` usage, TPM backing, RSA-2048 constraints, and lack of decryption support.
5
+
***Metadata:** Updated `pubspec.yaml` description to explicitly include supported platforms and Windows Hello.
Copy file name to clipboardExpand all lines: README.md
+20-6Lines changed: 20 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,7 +164,7 @@ To get started with Biometric Signature, follow these steps:
164
164
165
165
```yaml
166
166
dependencies:
167
-
biometric_signature: ^9.0.0
167
+
biometric_signature: ^9.0.1
168
168
```
169
169
170
170
| | Android | iOS | macOS | Windows |
@@ -240,13 +240,15 @@ platform :osx, '10.15'
240
240
241
241
### Windows Integration
242
242
243
-
This plugin uses **Windows Hello** for biometric authentication on Windows 10 and later.
243
+
### Windows Integration
244
+
245
+
This plugin uses **Windows Hello** (`Windows.Security.Credentials.KeyCredentialManager`) for biometric authentication on Windows 10 and later. Keys are typically backed by the device's **TPM (Trusted Platform Module)** for hardware-grade security.
244
246
245
247
**Platform Limitations:**
246
-
- Windows only supports **RSA keys** (ECDSA is ignored)
247
-
- Windows Hello **always authenticates** during key creation (`enforceBiometric` is effectively always `true`)
248
-
-`setInvalidatedByBiometricEnrollment` and `useDeviceCredentials` are ignored
249
-
-**Decryption is not supported** on Windows
248
+
-**Key Type**: Windows Hello only supports **RSA-2048**keys (ECDSA requests are automatically promoted to RSA).
249
+
-**Authentication**: Windows Hello **always authenticates** during key creation (`enforceBiometric` is effectively always `true`).
250
+
-**Configuration**: `setInvalidatedByBiometricEnrollment` and `useDeviceCredentials`arguments are ignored on this platform.
251
+
-**Decryption**: **Not supported**. The Windows Hello API is designed primarily for authentication (signing) and does not expose general decryption capabilities for these keys.
250
252
251
253
No additional configuration is required. The plugin will automatically use Windows Hello when available.
252
254
@@ -273,6 +275,18 @@ This package simplifies server authentication using biometrics. The following im
273
275
274
276
When a user enrolls in biometrics, a key pair is generated. The private key is securely stored on the device, while the public key is sent to a server for registration. To authenticate, the user is prompted to use their biometrics, unlocking the private key. A cryptographic signature is then generated and sent to the server for verification. If the server successfully verifies the signature, it returns an appropriate response, authorizing the user.
275
277
278
+
### Biometric Decryption
279
+
280
+
The plugin also supports secure decryption, ensuring that sensitive data transmitted from the server can only be accessed by the authenticated user on their specific device.
0 commit comments