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
Merge pull request #161 from shinji-san/release-v0.10.2
Release - v0.10.2
Changed
- FinitePoint: Use `ReadOnlySpan<char>` for `string` parameters in ctor and methods.
Deprecated
- The Secret Legacy Mode is marked as deprecated and will be removed in one of the next releases.
Fixed
- Fixed NETSDK1187 warning (see #151). Locale 'de-de' is normalized to the standard locale 'de-DE'.
Resolves: #161
@@ -146,13 +146,13 @@ Afterwards, use the function `Reconstruction` to re-construct the original secre
146
146
147
147
The length of the shares is based on the security level. It's possible to pre-define a security level by `ctor` or the `SecurityLevel` property. The pre-defined security level will be overriden, if the secret size is greater than the Mersenne prime, which is calculated by means of the security level. It is not necessary to define a security level for a re-construction.
148
148
149
-
## Attention: Breaking change - Normal and legacy mode in v0.7.0
149
+
## Attention: Breaking change - Normal and legacy mode in v0.7.0 [Deprecated]
150
150
151
151
Library version 0.7.0 introduces a normal mode and a legacy mode for secrets. The normal mode is the new and default mode. The legacy mode is for backward compatibility.
152
152
153
153
*Why was the normal mode introduced?*
154
154
155
-
The normal mode supports positive secret values and also negative secret values like negative integer numbers or byte arrays with most significant byte greater than 0x7F. The legacy mode generates shares that can't be used to reconstruct negative secret values. So the original secret and the reconstructed secret aren't identical for negative secret values (e.g. `BigInetger secret = -2000`). The legacy mode only returns correct results for positive secret values.
155
+
The normal mode supports positive secret values and also negative secret values like negative integer numbers or byte arrays with most significant byte greater than 0x7F. The legacy mode generates shares that can't be used to reconstruct negative secret values. So the original secret and the reconstructed secret aren't identical for negative secret values (e.g. `BigInteger secret = -2000`). The legacy mode only returns correct results for positive secret values.
0 commit comments