你在这里有几个问题。让我们按顺序排列它们。
首先,该类型既没有无参数构造函数,也没有单参数构造函数,从参考源Microsoft.Research.SEAL.Ciphertext
可以看出:
public class Ciphertext : NativeObject
{
public Ciphertext(MemoryPoolHandle pool = null)
{
// Contents omitted
}
public Ciphertext(SEALContext context, MemoryPoolHandle pool = null)
{
// Contents omitted
}
// Additional constructors, methods and members omitted.
第一个构造函数的参数是可选的,但这并不意味着它是无参数的,它只是意味着编译器在代码中不存在该值时提供该值。但是当通过反射调用构造函数时(这是 Json.NET 所做的),仍然需要提供一个值;有关详细信息,请参阅反射 - 使用参数调用构造函数。这种类型缺少真正的无参数构造函数是导致Newtonsoft.Json:无法找到用于 Microsoft.Research.SEAL.Ciphertext 类型的构造函数的原因。要抛出的异常。
(在评论中指出您的问题是sampleClass
缺少默认构造函数,但该评论是错误的。)
由于您无法修改Ciphertext
提供自己的构造方法的标准方法,因此请CustomCreationConverter<T>
像这样使用:
public class CiphertextConverter : CustomCreationConverter<Ciphertext>
{
public override Ciphertext Create(Type objectType)
{
return new Ciphertext(); // Use the default value for the optional parameter
}
}
然后做:
var settings = new JsonSerializerSettings
{
Converters = { new CiphertextConverter() },
};
var array = JsonConvert.DeserializeObject<sampleClass []>(requestBody, settings);
但是,这不起作用,这是您的下一个问题。由于 的大多数公共属性Ciphertext
都是只读的,因此无法从它们中反序列化类型。
在这里失败的演示小提琴 #1 。
那么该怎么办?事实证明,Ciphertext
有两种方法
这些似乎允许我们将 a 序列化为 a Ciphertext
,MemoryStream
然后使用如下转换器将内容作为 Base64 字符串插入 JSON:
public class CiphertextConverter : JsonConverter<Ciphertext>
{
readonly SEALContext context;
public CiphertextConverter(SEALContext context) => this.context = context ?? throw new ArgumentNullException(nameof(context));
public override Ciphertext ReadJson(JsonReader reader, Type objectType, Ciphertext existingValue, bool hasExistingValue, JsonSerializer serializer)
{
var data = serializer.Deserialize<byte []>(reader);
if (data == null)
return null;
var cipherText = new Ciphertext();
using (var stream = new MemoryStream(data))
cipherText.Load(context, stream);
return cipherText;
}
public override void WriteJson(JsonWriter writer, Ciphertext value, JsonSerializer serializer)
{
using (var stream = new MemoryStream())
{
value.Save(stream, ComprModeType.Deflate); // TODO: test to see whether Deflate gives better size vs speed performance in practice.
writer.WriteValue(stream.ToArray());
}
}
}
然后在序列化和反序列化时使用转换器如下:
var settings = new JsonSerializerSettings
{
Converters = { new CiphertextConverter(GlobalContext.Context) },
};
var array = JsonConvert.DeserializeObject<sampleClass []>(requestBody, settings);
但是等等——这个对象是GlobalContext.Context
什么?这给您带来了第三个问题,即您需要SEALContext
客户端和服务器端的兼容对象Ciphertext
通过序列化在两者之间传递。现在,查看Cloud Functions Demo演示应用程序,这似乎是一个正确的假设,因为该应用程序在客户端和服务器端确实具有兼容的上下文:
所以我假设你也这样做。既然你这样做了,上面的转换器应该用于序列化和反序列化。
出于测试目的,我调整了来自https://github.com/microsoft/SEAL/tree/master/dotnet/testsCiphertextTests.SaveLoadTest()
的测试方法和类,以创建以下测试工具:GlobalContext
public class TestClass
{
[TestMethod]
public void JsonNetSaveLoadTest()
{
Debug.WriteLine("Testing Json.NET");
Func<Ciphertext, SEALContext, Ciphertext> roundtrip = (cipher, context) =>
{
var clientArray = new [] { new sampleClass { ciphertext = cipher } };
var settings = new JsonSerializerSettings
{
Converters = { new CiphertextConverter(GlobalContext.Context) },
};
var requestBody = JsonConvert.SerializeObject(clientArray, settings);
Debug.Write(" ");
Debug.WriteLine(requestBody);
Debug.WriteLine(" requestBody.Length={0}", requestBody.Length);
var array = JsonConvert.DeserializeObject<sampleClass []>(requestBody, settings);
Assert.IsTrue(array.Length == clientArray.Length);
var reserializedJson = JsonConvert.SerializeObject(array, settings);
Debug.Write(" ");
Debug.WriteLine(reserializedJson);
Assert.IsTrue(requestBody == reserializedJson);
return array[0].ciphertext;
};
SaveLoadTest(roundtrip);
Console.WriteLine(" passed.");
}
// Adapted from https://github.com/microsoft/SEAL/blob/master/dotnet/tests/CiphertextTests.cs#L113
[TestMethod]
public void DirectSaveLoadTest()
{
Debug.WriteLine("Testing direct save and load:");
Func<Ciphertext, SEALContext, Ciphertext> roundtrip = (cipher, context) =>
{
Ciphertext loaded = new Ciphertext();
Assert.AreEqual(0ul, loaded.Size);
Assert.AreEqual(0ul, loaded.PolyModulusDegree);
Assert.AreEqual(0ul, loaded.CoeffModCount);
using (MemoryStream mem = new MemoryStream())
{
cipher.Save(mem);
mem.Seek(offset: 0, loc: SeekOrigin.Begin);
loaded.Load(context, mem);
}
return loaded;
};
SaveLoadTest(roundtrip);
Debug.WriteLine(" passed.");
}
// Adapted from https://github.com/microsoft/SEAL/blob/master/dotnet/tests/CiphertextTests.cs#L113
static void SaveLoadTest(Func<Ciphertext, SEALContext, Ciphertext> roundtrip)
{
SEALContext context = GlobalContext.Context;
KeyGenerator keygen = new KeyGenerator(context);
Encryptor encryptor = new Encryptor(context, keygen.PublicKey);
Plaintext plain = new Plaintext("2x^3 + 4x^2 + 5x^1 + 6");
Ciphertext cipher = new Ciphertext();
encryptor.Encrypt(plain, cipher);
Assert.AreEqual(2ul, cipher.Size);
Assert.AreEqual(8192ul, cipher.PolyModulusDegree);
Assert.AreEqual(4ul, cipher.CoeffModCount);
var loaded = roundtrip(cipher, context);
Assert.AreEqual(2ul, loaded.Size);
Assert.AreEqual(8192ul, loaded.PolyModulusDegree);
Assert.AreEqual(4ul, loaded.CoeffModCount);
Assert.IsTrue(ValCheck.IsValidFor(loaded, context));
ulong ulongCount = cipher.Size * cipher.PolyModulusDegree * cipher.CoeffModCount;
for (ulong i = 0; i < ulongCount; i++)
{
Assert.AreEqual(cipher[i], loaded[i]);
}
}
}
static class GlobalContext
{
// Copied from https://github.com/microsoft/SEAL/blob/master/dotnet/tests/GlobalContext.cs
static GlobalContext()
{
EncryptionParameters encParams = new EncryptionParameters(SchemeType.BFV)
{
PolyModulusDegree = 8192,
CoeffModulus = CoeffModulus.BFVDefault(polyModulusDegree: 8192)
};
encParams.SetPlainModulus(65537ul);
BFVContext = new SEALContext(encParams);
encParams = new EncryptionParameters(SchemeType.CKKS)
{
PolyModulusDegree = 8192,
CoeffModulus = CoeffModulus.BFVDefault(polyModulusDegree: 8192)
};
CKKSContext = new SEALContext(encParams);
}
public static SEALContext BFVContext { get; private set; } = null;
public static SEALContext CKKSContext { get; private set; } = null;
public static SEALContext Context => BFVContext;
}
工作演示小提琴#2 here。
笔记:
只要是公共的,就不需要sampleClass
用 with标记无参构造函数[JsonConstructor]
。
通过测试,生成的 Base64 字符串Ciphertext
似乎很长,每个 .5 MB 大约为 .5 MB Ciphertext
。因为 Json.NET 在解析过程中完全实现了每个字符串,所以在处理如此巨大的字符串时效率并不高。如果超过最大有效字符串长度或遇到大对象堆碎片,您将需要重新评估您的架构。
免责声明
我不是安全专业人士。我无法告诉您通过网络发送序列化文件是否Ciphertext
会泄漏信息。我也不能建议您如何SEALContext
为您的应用程序选择合适的 - 甚至在客户端和服务器端具有兼容的上下文是否可能会泄漏信息。这个答案只解释了如何通过 Json.NET 序列化特定的 SEAL 对象。