[{"data":1,"prerenderedAt":266},["ShallowReactive",2],{"content:zh:sha384-generator":3},{"id":4,"title":5,"body":6,"description":242,"extension":243,"faq":244,"kind":257,"locale":258,"meta":259,"navigation":260,"path":261,"seo":262,"seoTitle":263,"stem":264,"__hash__":265},"pages\u002Fzh\u002Fsha384-generator.md","SHA-384 哈希生成器",{"type":7,"value":8,"toc":231},"minimark",[9,13,17,20,23,26,37,47,50,83,93,108,112,115,119,122,125,129,132,138,142,198,201,223],[10,11,12],"h2",{"id":12},"本工具计算什么",[14,15,16],"p",{},"SHA-384 是 SHA-2 系列中的独立算法，输出 384 位摘要，即 96 个十六进制字符。它与 SHA-512 使用不同的初始化值，所以不能先计算 SHA-512，再把前 96 个字符当作 SHA-384。本工具执行的是 SHA-384 本身。",[14,18,19],{},"当接口规范、签名流程或既有集成明确要求 SHA-384 时，应选择本页。导出时保留算法名称，有助于防止把完整摘要误认为其他算法的截断结果。大小写只是十六进制显示约定，对实际摘要没有影响。",[14,21,22],{},"摘要不等于加密，也不等于数字签名。复现结果前，应确认编码、空格、换行和实际文件字节。若规范要求 HMAC-SHA384，请转到 HMAC 工具并使用对应密钥；直接把密钥拼在消息前后再计算摘要，并不是等价操作。",[10,24,25],{"id":25},"可核对的示例",[14,27,28,32,33,36],{},[29,30,31],"code",{},"UTF-8"," · ",[29,34,35],{},"abc"," · SHA-384",[38,39,45],"pre",{"className":40,"code":42,"language":43,"meta":44},[41],"language-text","cb00753f45a35e8bb5a03d699ac65007272c32ab0eded1631a8b605a43ff5bed8086072ba1e7cc2358baeca134c825a7\n","text","",[29,46,42],{"__ignoreMap":44},[10,48,49],{"id":49},"如何计算与比较",[51,52,53,69,76],"ol",{},[54,55,56,57,61,62,65,66,68],"li",{},"在",[58,59,60],"strong",{},"输入文本","中粘贴需要计算的内容，或点击",[58,63,64],{},"示例","加载 ",[29,67,35],{},"。工具按 UTF-8 编码计算，保留输入中的空格和换行。",[54,70,71,72,75],{},"单条文本模式下，不超过 64 KiB 的非空输入会在停止输入片刻后自动计算。计算空字符串或更大的文本时，请点击",[58,73,74],{},"生成哈希","。修改输入后，旧结果会立即清除。",[54,77,78,79,82],{},"如需核对已保存的文件，请切换到",[58,80,81],{},"文件校验","，确认算法后选择或拖入文件。文件模式会读取原始字节并自动开始计算。",[14,84,85,86,89,90,92],{},"批量处理时，勾选",[58,87,88],{},"每行独立计算","，选择是否包含空行，再点击",[58,91,74],{},"。逐行模式不会自动计算。CRLF、LF 和 CR 仅用于分隔记录，不计入各行摘要；重复行保留各自的原始行号。",[14,94,95,96,99,100,103,104,107],{},"将完整的十六进制参考值粘贴到",[58,97,98],{},"比较预期值（可选）","，再点击",[58,101,102],{},"核对","。比较时忽略字母大小写和首尾空白，但不接受内部空格或错误长度。",[58,105,106],{},"复制","会保留完整结果。TXT、CSV 导出包含输入标识、算法和摘要，不包含原始文本或密钥。",[10,109,111],{"id":110},"限制隐私与下一步","限制、隐私与下一步",[14,113,114],{},"文本上限为 10 MiB；逐行模式最多接受 10,000 条记录，按过滤空行前的数量计算。文件队列最多 50 个文件，每个不超过 1 GiB，按 2 MiB 分块依序读取。这些限制用于控制浏览器资源占用，不保证每部手机都能快速处理最大输入；必要时可取消计算。计算在浏览器中完成，正常的页面和资源请求仍会发送到托管服务器。",[10,116,118],{"id":117},"按规范选择-sha-384而不是截短-sha-512","按规范选择 SHA-384，而不是截短 SHA-512",[14,120,121],{},"SHA-384 摘要为 48 字节，每个字节用两个十六进制字符表示，因此本页显示 96 个字符。有些接口使用 Base64 表示相同的摘要字节，看到的字符串长度不同，不代表算法一定不同。",[14,123,124],{},"SHA-384 虽然与 SHA-512 同属一个算法家族，但初始值不同。计算 SHA-512 后保留前 96 个字符，不能得到 SHA-384。请在处理文件前选对算法，保留完整输出。证书或签名流程标明 SHA-384 时，本页只能复现原始摘要，不会解析签名结构，也不会自动识别实际被签名的字节范围。",[10,126,128],{"id":127},"实际验证截短-sha-512为什么不成立","实际验证“截短 SHA-512”为什么不成立",[14,130,131],{},"分别在本页和 SHA-512 页面点击示例。把 abc 的 SHA-384 与 abc 的 SHA-512 前 96 个字符对照：长度虽然相同，值却不同。",[38,133,136],{"className":134,"code":135,"language":43,"meta":44},[41],"SHA-384 \u002F abc:\ncb00753f45a35e8bb5a03d699ac65007272c32ab0eded1631a8b605a43ff5bed8086072ba1e7cc2358baeca134c825a7\nSHA-512 \u002F abc \u002F 仅截取前 96 个十六进制字符（不是 SHA-384）:\nddaf35a193617abacc417349ae20413112e6fa4e89a97ea20a9eeee64b55d39a2192992a274fc1a836ba3c23a3feebbd\n",[29,137,135],{"__ignoreMap":44},[10,139,141],{"id":140},"sha-384-的格式和构造误区","SHA-384 的格式和构造误区",[143,144,145,161],"table",{},[146,147,148],"thead",{},[149,150,151,155,158],"tr",{},[152,153,154],"th",{},"现象",[152,156,157],{},"原因",[152,159,160],{},"处理方式",[162,163,164,176,187],"tbody",{},[149,165,166,170,173],{},[167,168,169],"td",{},"截短的 SHA-512 对不上参考值",[167,171,172],{},"SHA-384 不是普通 SHA-512 的子串",[167,174,175],{},"明确选择 SHA-384 后重新计算。",[149,177,178,181,184],{},[167,179,180],{},"参考值采用 Base64",[167,182,183],{},"当前比较框只接受十六进制",[167,185,186],{},"正确解码并重新编码，或索取十六进制参考值。",[149,188,189,192,195],{},[167,190,191],{},"证书签名比摘要长很多",[167,193,194],{},"数字签名不等于原始摘要",[167,196,197],{},"使用对应的签名验证工具及正确的签名输入。",[10,199,200],{"id":200},"相关工具与指南",[202,203,204,211,217],"ul",{},[54,205,206],{},[207,208,210],"a",{"href":209},"\u002Fzh\u002Fsha512-generator","SHA-512",[54,212,213],{},[207,214,216],{"href":215},"\u002Fzh\u002Fhmac-generator","HMAC 消息认证工具",[54,218,219],{},[207,220,222],{"href":221},"\u002Fzh\u002Ffile-md5","文件校验工具",[14,224,225],{},[207,226,230],{"href":227,"rel":228},"https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F180-4\u002Fupd1\u002Ffinal",[229],"nofollow","FIPS 180-4",{"title":44,"searchDepth":232,"depth":232,"links":233},2,[234,235,236,237,238,239,240,241],{"id":12,"depth":232,"text":12},{"id":25,"depth":232,"text":25},{"id":49,"depth":232,"text":49},{"id":110,"depth":232,"text":111},{"id":117,"depth":232,"text":118},{"id":127,"depth":232,"text":128},{"id":140,"depth":232,"text":141},{"id":200,"depth":232,"text":200},"计算完整的 SHA-384 摘要，输出 96 位十六进制值，而不是截取 SHA-512。","md",[245,248,251,254],{"question":246,"answer":247},"截取 SHA-512 可以得到 SHA-384 吗？","不能。SHA-384 使用不同初始化值，应直接选择 SHA-384 算法。",{"question":249,"answer":250},"为什么 SHA-384 是 48 字节，却显示 96 个字符？","十六进制每两个字符表示一个字节。48 字节的完整 SHA-384 摘要因此需要 96 个十六进制字符。",{"question":252,"answer":253},"HMAC-SHA384 是把密钥和消息拼起来计算 SHA-384 吗？","不是。HMAC 使用有明确定义的带密钥构造。请到 HMAC 页面选择 HMAC-SHA-384，直接拼接密钥与消息并不等价。",{"question":255,"answer":256},"能用本页验证 SHA-384 证书签名吗？","不能。证书签名验证还涉及签名结构、公钥算法和验证规则。本页只计算文本或文件的原始摘要。","tool","zh",{},true,"\u002Fzh\u002Fsha384-generator",{"title":5,"description":242},"SHA-384 哈希生成器 — md5hash.net","zh\u002Fsha384-generator","EdsR7IDmOCwv-G2XrAOebg3w7T2p5JI9wLUl9maNIU4",1792048884655]