fix(zk): proof compatiblity between 32/64b platforms (0.6)

tfhe-zk-pok/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "tfhe-zk-pok"
-version = "0.1.0"
+version = "0.1.1"
 edition = "2021"
 keywords = ["zero", "knowledge", "proof", "vector-commitments"]
 homepage = "https://zama.ai/"

tfhe-zk-pok/src/proofs/pke.rs

@@ -295,7 +295,7 @@ pub fn prove<G: Curve>(
 
     let x_bytes = &*[
         q.to_le_bytes().as_slice(),
-        d.to_le_bytes().as_slice(),
+        (d as u64).to_le_bytes().as_slice(),
         b_i.to_le_bytes().as_slice(),
         t.to_le_bytes().as_slice(),
         &*a.iter().flat_map(|&x| x.to_le_bytes()).collect::<Box<_>>(),
@@ -684,7 +684,7 @@ pub fn verify<G: Curve>(
 
     let x_bytes = &*[
         q.to_le_bytes().as_slice(),
-        d.to_le_bytes().as_slice(),
+        (d as u64).to_le_bytes().as_slice(),
         b_i.to_le_bytes().as_slice(),
         t.to_le_bytes().as_slice(),
         &*a.iter().flat_map(|&x| x.to_le_bytes()).collect::<Box<_>>(),

tfhe-zk-pok/src/proofs/range.rs

@@ -190,7 +190,7 @@ pub fn prove<G: Curve>(
         G::Zp::hash(
             core::slice::from_mut(s),
             &[
-                &i.to_le_bytes(),
+                &(i as u64).to_le_bytes(),
                 v_hat.to_bytes().as_ref(),
                 c_hat.to_bytes().as_ref(),
                 c_y.to_bytes().as_ref(),
@@ -286,7 +286,7 @@ pub fn verify<G: Curve>(
         G::Zp::hash(
             core::slice::from_mut(s),
             &[
-                &i.to_le_bytes(),
+                &(i as u64).to_le_bytes(),
                 v_hat.to_bytes().as_ref(),
                 c_hat.to_bytes().as_ref(),
                 c_y.to_bytes().as_ref(),

tfhe/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "tfhe"
-version = "0.6.4"
+version = "0.6.5"
 edition = "2021"
 readme = "../README.md"
 keywords = ["fully", "homomorphic", "encryption", "fhe", "cryptography"]
@@ -73,7 +73,7 @@ fs2 = { version = "0.4.3", optional = true }
 # While we wait for repeat_n in rust standard library
 itertools = "0.11.0"
 rand_core = { version = "0.6.4", features = ["std"] }
-tfhe-zk-pok = { version = "0.1.0", path = "../tfhe-zk-pok", optional = true }
+tfhe-zk-pok = { version = "0.1.1", path = "../tfhe-zk-pok", optional = true }
 tfhe-versionable = { version = "0.1.0", path = "../utils/tfhe-versionable" }
 
 # wasm deps

tfhe/docs/fundamentals/serialization.md

@@ -15,7 +15,7 @@ Here is a full example:
 
 [dependencies]
 # ...
-tfhe = { version = "0.6.4", features = ["integer","x86_64-unix"]}
+tfhe = { version = "0.6.5", features = ["integer","x86_64-unix"]}
 bincode = "1.3.3"
 ```
 

tfhe/docs/getting_started/installation.md

@@ -9,13 +9,13 @@ First, add **TFHE-rs** as a dependency in your `Cargo.toml`.
 **For `x86_64` machine running a Unix-like OS:**
 
 ```toml
-tfhe = { version = "0.6.4", features = [ "boolean", "shortint", "integer", "x86_64-unix" ] }
+tfhe = { version = "0.6.5", features = [ "boolean", "shortint", "integer", "x86_64-unix" ] }
 ```
 
 **For `ARM` machine running a Unix-like OS:**
 
 ```toml
-tfhe = { version = "0.6.4", features = [ "boolean", "shortint", "integer", "aarch64-unix" ] }
+tfhe = { version = "0.6.5", features = [ "boolean", "shortint", "integer", "aarch64-unix" ] }
 ```
 
 **For `x86_64` machines with the** [**`rdseed instruction`**](https://en.wikipedia.org/wiki/RDRAND) **running Windows:**

tfhe/docs/getting_started/quick_start.md

@@ -47,7 +47,7 @@ fn main() {
 The default configuration for x86 Unix machines is as follows:
 
 ```toml
-tfhe = { version = "0.6.4", features = ["integer", "x86_64-unix"]}
+tfhe = { version = "0.6.5", features = ["integer", "x86_64-unix"]}
 ```
 
 Refer to the [installation documentation](installation.md) for configuration options of different platforms.Learn more about homomorphic types features in the [configuration documentation.](../guides/rust\_configuration.md)

tfhe/docs/guides/data_versioning.md

@@ -2,7 +2,7 @@
 
 This document explains how to save and load versioned data using the data versioning feature.
 
-Starting from v0.6.4, **TFHE-rs** supports versioned data types. This allows you to store data and load it in the future without compatibility concerns. This feature is done by the `tfhe-versionable` crate.
+Starting from v0.6.5, **TFHE-rs** supports versioned data types. This allows you to store data and load it in the future without compatibility concerns. This feature is done by the `tfhe-versionable` crate.
 
 This versioning scheme is compatible with all the [data formats](https://serde.rs/#data-formats) supported by serde.
 
@@ -16,7 +16,7 @@ You can load serialized data with the `unversionize` function, even in newer ver
 
 [dependencies]
 # ...
-tfhe = { version = "0.6.4", features = ["integer","x86_64-unix"]}
+tfhe = { version = "0.6.5", features = ["integer","x86_64-unix"]}
 tfhe-versionable = "0.1.0"
 bincode = "1.3.3"
 ```

tfhe/docs/guides/run_on_gpu.md

@@ -19,13 +19,13 @@ To use the **TFHE-rs** GPU backend in your project, add the following dependency
 If you are using an `x86` machine:
 
 ```toml
-tfhe = { version = "0.6.4", features = [ "boolean", "shortint", "integer", "x86_64-unix", "gpu" ] }
+tfhe = { version = "0.6.5", features = [ "boolean", "shortint", "integer", "x86_64-unix", "gpu" ] }
 ```
 
 If you are using an `ARM` machine:
 
 ```toml
-tfhe = { version = "0.6.4", features = [ "boolean", "shortint", "integer", "aarch64-unix", "gpu" ] }
+tfhe = { version = "0.6.5", features = [ "boolean", "shortint", "integer", "aarch64-unix", "gpu" ] }
 ```
 
 {% hint style="success" %}

tfhe/docs/references/core-crypto-api/tutorial.md

@@ -9,7 +9,7 @@ Welcome to this tutorial about `TFHE-rs` `core_crypto` module.
 To use `TFHE-rs`, it first has to be added as a dependency in the `Cargo.toml`:
 
 ```toml
-tfhe = { version = "0.6.4", features = [ "x86_64-unix" ] }
+tfhe = { version = "0.6.5", features = [ "x86_64-unix" ] }
 ```
 
 This enables the `x86_64-unix` feature to have efficient implementations of various algorithms for `x86_64` CPUs on a Unix-like system. The 'unix' suffix indicates that the `UnixSeeder`, which uses `/dev/random` to generate random numbers, is activated as a fallback if no hardware number generator is available (like `rdseed` on `x86_64` or if the [`Randomization Services`](https://developer.apple.com/documentation/security/1399291-secrandomcopybytes?language=objc) on Apple platforms are not available). To avoid having the `UnixSeeder` as a potential fallback or to run on non-Unix systems (e.g., Windows), the `x86_64` feature is sufficient.
@@ -19,19 +19,19 @@ For Apple Silicon, the `aarch64-unix` or `aarch64` feature should be enabled. `a
 In short: For `x86_64`-based machines running Unix-like OSes:
 
 ```toml
-tfhe = { version = "0.6.4", features = ["x86_64-unix"] }
+tfhe = { version = "0.6.5", features = ["x86_64-unix"] }
 ```
 
 For Apple Silicon or aarch64-based machines running Unix-like OSes:
 
 ```toml
-tfhe = { version = "0.6.4", features = ["aarch64-unix"] }
+tfhe = { version = "0.6.5", features = ["aarch64-unix"] }
 ```
 
 For `x86_64`-based machines with the [`rdseed instruction`](https://en.wikipedia.org/wiki/RDRAND) running Windows:
 
 ```toml
-tfhe = { version = "0.6.4", features = ["x86_64"] }
+tfhe = { version = "0.6.5", features = ["x86_64"] }
 ```
 
 ### Commented code to double a 2-bit message in a leveled fashion and using a PBS with the `core_crypto` module.

tfhe/docs/tutorials/ascii_fhe_string.md

@@ -25,7 +25,7 @@ To use the `FheUint8` type, enable the `integer` feature:
 
 [dependencies]
 # Default configuration for x86 Unix machines:
-tfhe = { version = "0.6.4", features = ["integer", "x86_64-unix"]}
+tfhe = { version = "0.6.5", features = ["integer", "x86_64-unix"]}
 ```
 
 Refer to the [installation guide](../getting\_started/installation.md) for other configurations.

tfhe/docs/tutorials/parity_bit.md

@@ -18,7 +18,7 @@ This function returns a Boolean (`true` or `false`) so that the total count of `
 # Cargo.toml
 
 # Default configuration for x86 Unix machines:
-tfhe = { version = "0.6.4", features = ["integer", "x86_64-unix"]}
+tfhe = { version = "0.6.5", features = ["integer", "x86_64-unix"]}
 ```
 
 Refer to the [installation](../getting\_started/installation.md) for other configurations.