Warning: file_get_contents(/data/phpspider/zhask/data//catemap/8/redis/2.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Javascript JSEncrypt每次为相同的消息和公钥生成不同的输出_Javascript_Encryption_Public Key Encryption_Public Key - Fatal编程技术网

Javascript JSEncrypt每次为相同的消息和公钥生成不同的输出

Javascript JSEncrypt每次为相同的消息和公钥生成不同的输出,javascript,encryption,public-key-encryption,public-key,Javascript,Encryption,Public Key Encryption,Public Key,我有一个简单的JavaScript代码: <html> <script type="text/javascript" src="http://cdn.rawgit.com/travist/jsencrypt/v2.1.0/bin/jsencrypt.js"></script> <script type="text/javascript"> var message = "This is my message" // we

我有一个简单的JavaScript代码:

<html>
  <script type="text/javascript" src="http://cdn.rawgit.com/travist/jsencrypt/v2.1.0/bin/jsencrypt.js"></script>
  <script type="text/javascript">

    var message = "This is my message"

    // we create a new JSEncrypt object for rsa encryption
    var rsaEncrypt = new JSEncrypt();

    var publicKey = "-----BEGIN PUBLIC KEY-----" +
      "\nMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQK" +
      "BgQCQDxDFOYJpkCaqeX4CBVNCtBjX\nMZgGMo" +
      "lSs2wYrVu1ixr36KpeJcRcYhz+AnyhnUpYkgk" +
      "+hEqJtDSNirU5Dk5oVYYi\ngf2uLogV5Tp/ka" +
      "K49r9vtxldcHraZIgNQjcdeQUd/viKd/3DvM8" +
      "naWR/mTG0nCBE\nrEQkATW/xXynJh/COQIDAQ" +
      "AB\n-----END PUBLIC KEY-----"

    rsaEncrypt.setPublicKey(publicKey);

    var encryptedMessage = rsaEncrypt.encrypt(message);

    console.log(encryptedMessage)
  </script>
</html>
有人能解释这种行为吗?

这是意料之中的

RSA密码系统是以素数为模的群工作的。为了确保所有可能的明文都以相同的安全性进行加密,对明文进行填充以生成略小于模数的填充明文。因为填充是在加密之前应用的,所以密文看起来完全不同

JSEncrypt基于JSBN,而JSBN只实现()。第二种类型的填充引入了随机字节,这些字节在解密后由于标记字节而被删除。填充至少需要11个字节

如果要检查与其他实现的互操作性,需要执行完整的加密-解密周期,并确保返回相同的明文


请注意,现在不应再使用PKCS#1 v1.5填充,而PKCS#1 v.2 OAEP是首选的,它也是随机的。

可能会有一些随机填充。感谢Artjom B的全面回答。
abqE+YkCMKFWgsazbZpfGvoXLci9FL/wZLYUMR6ZFkolsvJC5MdJgq5yn+AXXy8xlKHDOry6czAaOQOTl2HXdKSfsypc8nqDU8Sx5PuEgMYjvJ/dEyfU6jVuxfH1Qmuk6aOGVHePNfDlC4kSjgp1RXToSP5NqAEi24EuMx3uulI=

OzZM03Pki3o631KOuZ5nyQKu1xXRbLHhrR0WnjE5Ns5SssoiCEwlrS+svtP0cbZaYWZJc+FlZQNFUam4iC233BKnY5Nrr5Ppj14eaBvJ4x3FR8FiLwtyEW7nTzisAS7Ys2RKPjUzmkiOCZHwIpXnUO10KVo8763+JIuDB0cDPS4=