Edit File by line
/home/barbar84/www/wp-conte.../plugins/sujqvwi/ShExBy/shex_roo.../proc/self/root/usr/share/gnupg
File: help.zh_CN.txt
# help.zh_CN.txt - zh_CN GnuPG online help
[0] Fix | Delete
# Copyright (C) 2007 Free Software Foundation, Inc.
[1] Fix | Delete
#
[2] Fix | Delete
# This file is part of GnuPG.
[3] Fix | Delete
#
[4] Fix | Delete
# GnuPG is free software; you can redistribute it and/or modify
[5] Fix | Delete
# it under the terms of the GNU General Public License as published by
[6] Fix | Delete
# the Free Software Foundation; either version 3 of the License, or
[7] Fix | Delete
# (at your option) any later version.
[8] Fix | Delete
#
[9] Fix | Delete
# GnuPG is distributed in the hope that it will be useful,
[10] Fix | Delete
# but WITHOUT ANY WARRANTY; without even the implied warranty of
[11] Fix | Delete
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
[12] Fix | Delete
# GNU General Public License for more details.
[13] Fix | Delete
#
[14] Fix | Delete
# You should have received a copy of the GNU General Public License
[15] Fix | Delete
# along with this program; if not, see <https://www.gnu.org/licenses/>.
[16] Fix | Delete
[17] Fix | Delete
[18] Fix | Delete
.gpg.edit_ownertrust.value
[19] Fix | Delete
在这里指定的数值完全由您自己决定;这些数值永远不会被输出给任何第三方。
[20] Fix | Delete
我们需要它来实现“信任网络”;这跟隐含建立起来的“验证网络”无关。
[21] Fix | Delete
.
[22] Fix | Delete
[23] Fix | Delete
.gpg.edit_ownertrust.set_ultimate.okay
[24] Fix | Delete
要建立起信任网络,GnuPG 需要知道哪些密钥是可绝对信任的――通常
[25] Fix | Delete
就是您拥有私钥的那些密钥。回答“yes”将此密钥设成可绝对信任的
[26] Fix | Delete
[27] Fix | Delete
.
[28] Fix | Delete
[29] Fix | Delete
.gpg.untrusted_key.override
[30] Fix | Delete
如果您无论如何要使用这把未被信任的密钥,请回答“yes”。
[31] Fix | Delete
.
[32] Fix | Delete
[33] Fix | Delete
.gpg.pklist.user_id.enter
[34] Fix | Delete
输入您要递送的报文的接收者的用户标识。
[35] Fix | Delete
.
[36] Fix | Delete
[37] Fix | Delete
.gpg.keygen.algo
[38] Fix | Delete
选择使用的算法。
[39] Fix | Delete
[40] Fix | Delete
DSA (也叫 DSS)即“数字签名算法”(美国国家标准),只能够用作签名。
[41] Fix | Delete
[42] Fix | Delete
Elgamal 是一种只能用作加密的算法。
[43] Fix | Delete
[44] Fix | Delete
RSA 可以用作签名或加密。
[45] Fix | Delete
[46] Fix | Delete
第一把密钥(主钥)必须具有签名的能力。
[47] Fix | Delete
.
[48] Fix | Delete
[49] Fix | Delete
.gpg.keygen.algo.rsa_se
[50] Fix | Delete
通常来说用同一把密钥签名及加密并不是个好主意。这个算法只在特定的情况
[51] Fix | Delete
下使用。请先咨询安全方面的专家。
[52] Fix | Delete
.
[53] Fix | Delete
[54] Fix | Delete
.gpg.keygen.size
[55] Fix | Delete
请输入密钥的尺寸
[56] Fix | Delete
.
[57] Fix | Delete
[58] Fix | Delete
.gpg.keygen.size.huge.okay
[59] Fix | Delete
请回答“yes”或“no”
[60] Fix | Delete
.
[61] Fix | Delete
[62] Fix | Delete
.gpg.keygen.size.large.okay
[63] Fix | Delete
请回答“yes”或“no”
[64] Fix | Delete
.
[65] Fix | Delete
[66] Fix | Delete
.gpg.keygen.valid
[67] Fix | Delete
请输入提示所要求的数值。
[68] Fix | Delete
您可以输入 ISO 日期格式(YYYY-MM-DD),但是出错时您不会得到友好的响应
[69] Fix | Delete
――系统会尝试将给定值解释为时间间隔。
[70] Fix | Delete
.
[71] Fix | Delete
[72] Fix | Delete
.gpg.keygen.valid.okay
[73] Fix | Delete
请回答“yes”或“no”
[74] Fix | Delete
.
[75] Fix | Delete
[76] Fix | Delete
.gpg.keygen.name
[77] Fix | Delete
请输入密钥持有人的名字
[78] Fix | Delete
.
[79] Fix | Delete
[80] Fix | Delete
.gpg.keygen.email
[81] Fix | Delete
请输入电子邮件地址(可选项,但强烈推荐使用)
[82] Fix | Delete
.
[83] Fix | Delete
[84] Fix | Delete
.gpg.keygen.comment
[85] Fix | Delete
请输入注释(可选项)
[86] Fix | Delete
.
[87] Fix | Delete
[88] Fix | Delete
.gpg.keygen.userid.cmd
[89] Fix | Delete
N 修改姓名。
[90] Fix | Delete
C 修改注释。
[91] Fix | Delete
E 修改电子邮件地址。
[92] Fix | Delete
O 继续产生密钥。
[93] Fix | Delete
Q 中止产生密钥。
[94] Fix | Delete
.
[95] Fix | Delete
[96] Fix | Delete
.gpg.keygen.sub.okay
[97] Fix | Delete
如果您允许生成子钥,请回答“yes”(或者“y”)。
[98] Fix | Delete
.
[99] Fix | Delete
[100] Fix | Delete
.gpg.sign_uid.okay
[101] Fix | Delete
请回答“yes”或“no”
[102] Fix | Delete
.
[103] Fix | Delete
[104] Fix | Delete
.gpg.sign_uid.class
[105] Fix | Delete
当您为某把密钥上某个用户标识添加签名时,您必须首先验证这把密钥确实属于
[106] Fix | Delete
署名于它的用户标识上的那个人。了解到您曾多么谨慎地对此进行过验证,对其
[107] Fix | Delete
他人是非常有用的
[108] Fix | Delete
[109] Fix | Delete
“0” 表示您对您有多么仔细地验证这把密钥的问题不表态。
[110] Fix | Delete
[111] Fix | Delete
“1” 表示您相信这把密钥属于那个声明是主人的人,但是您不能或根本没有验
[112] Fix | Delete
证过。如果您为一把属于类似虚拟人物的密钥签名,这个选择很有用。
[113] Fix | Delete
[114] Fix | Delete
“2” 表示您随意地验证了那把密钥。例如,您验证了这把密钥的指纹,或比对
[115] Fix | Delete
照片验证了用户标识。
[116] Fix | Delete
[117] Fix | Delete
“3” 表示您做了大量而详尽的验证密钥工作。例如,您同密钥持有人验证了密
[118] Fix | Delete
钥指纹,而且通过查验附带照片而难以伪造的证件(如护照)确认了密钥持
[119] Fix | Delete
有人的姓名与密钥上的用户标识一致,最后您还(通过电子邮件往来)验证
[120] Fix | Delete
了密钥上的电子邮件地址确实属于密钥持有人。
[121] Fix | Delete
[122] Fix | Delete
请注意上述关于验证级别 2 和 3 的说明仅是例子而已。最终还是由您自己决定
[123] Fix | Delete
当您为其他密钥签名时,什么是“随意”,而什么是“大量而详尽”。
[124] Fix | Delete
[125] Fix | Delete
如果您不知道应该选什么答案的话,就选“0”。
[126] Fix | Delete
.
[127] Fix | Delete
[128] Fix | Delete
.gpg.change_passwd.empty.okay
[129] Fix | Delete
请回答“yes”或“no”
[130] Fix | Delete
.
[131] Fix | Delete
[132] Fix | Delete
.gpg.keyedit.save.okay
[133] Fix | Delete
请回答“yes”或“no”
[134] Fix | Delete
.
[135] Fix | Delete
[136] Fix | Delete
.gpg.keyedit.cancel.okay
[137] Fix | Delete
请回答“yes”或“no”
[138] Fix | Delete
.
[139] Fix | Delete
[140] Fix | Delete
.gpg.keyedit.sign_all.okay
[141] Fix | Delete
如果您想要为所有用户标识签名的话就选“yes”
[142] Fix | Delete
.
[143] Fix | Delete
[144] Fix | Delete
.gpg.keyedit.remove.uid.okay
[145] Fix | Delete
如果您真的想要删除这个用户标识的话就回答“yes”。
[146] Fix | Delete
所有相关认证在此之后也会丢失!
[147] Fix | Delete
.
[148] Fix | Delete
[149] Fix | Delete
.gpg.keyedit.remove.subkey.okay
[150] Fix | Delete
如果可以删除这把子钥,请回答“yes”
[151] Fix | Delete
.
[152] Fix | Delete
[153] Fix | Delete
.gpg.keyedit.delsig.valid
[154] Fix | Delete
这是一份在这把密钥上有效的签名;通常您不会想要删除这份签名,
[155] Fix | Delete
因为要与这把密钥或拥有这把密钥的签名的密钥建立认证关系可能
[156] Fix | Delete
相当重要。
[157] Fix | Delete
.
[158] Fix | Delete
[159] Fix | Delete
.gpg.keyedit.delsig.unknown
[160] Fix | Delete
这份签名无法被检验,因为您没有相应的密钥。您应该暂缓删除它,
[161] Fix | Delete
直到您知道此签名使用了哪一把密钥;因为用来签名的密钥可能与
[162] Fix | Delete
其他已经验证的密钥存在信任关系。
[163] Fix | Delete
.
[164] Fix | Delete
[165] Fix | Delete
.gpg.keyedit.delsig.invalid
[166] Fix | Delete
这份签名无效。应当把它从您的钥匙环里删除。
[167] Fix | Delete
.
[168] Fix | Delete
[169] Fix | Delete
.gpg.keyedit.delsig.selfsig
[170] Fix | Delete
这是一份将密钥与用户标识相联系的签名。通常不应删除这样的签名。
[171] Fix | Delete
事实上,一旦删除,GnuPG可能从此就不能再使用这把密钥了。因此,
[172] Fix | Delete
只有在这把密钥的第一个自身签名因某些原因失效,而有第二个自身签
[173] Fix | Delete
字可用的情况下才这么做。
[174] Fix | Delete
.
[175] Fix | Delete
[176] Fix | Delete
.gpg.keyedit.updpref.okay
[177] Fix | Delete
用现有的首选项更新所有(或选定的)用户标识的首选项。所有受影响的自身签
[178] Fix | Delete
字的时间戳都会增加一秒钟。
[179] Fix | Delete
[180] Fix | Delete
.
[181] Fix | Delete
[182] Fix | Delete
.gpg.passphrase.enter
[183] Fix | Delete
请输入密码:这是一个秘密的句子
[184] Fix | Delete
[185] Fix | Delete
.
[186] Fix | Delete
[187] Fix | Delete
.gpg.passphrase.repeat
[188] Fix | Delete
请再次输入上次的密码,以确定您到底键入了些什么。
[189] Fix | Delete
.
[190] Fix | Delete
[191] Fix | Delete
.gpg.detached_signature.filename
[192] Fix | Delete
请给定要添加签名的文件名
[193] Fix | Delete
.
[194] Fix | Delete
[195] Fix | Delete
.gpg.openfile.overwrite.okay
[196] Fix | Delete
如果可以覆盖这个文件,请回答“yes”
[197] Fix | Delete
.
[198] Fix | Delete
[199] Fix | Delete
.gpg.openfile.askoutname
[200] Fix | Delete
请输入一个新的文件名。如果您直接按下了回车,那么就会使用显示在括
[201] Fix | Delete
号中的默认的文件名。
[202] Fix | Delete
.
[203] Fix | Delete
[204] Fix | Delete
.gpg.ask_revocation_reason.code
[205] Fix | Delete
您应该为这份吊销证书指定一个原因。根据情境的不同,您可以从下列清单中
[206] Fix | Delete
选出一项:
[207] Fix | Delete
“密钥已泄漏”
[208] Fix | Delete
如果您相信有某个未经许可的人已取得了您的私钥,请选此项。
[209] Fix | Delete
“密钥已替换”
[210] Fix | Delete
如果您已用一把新密钥代替旧的,请选此项。
[211] Fix | Delete
“密钥不再被使用”
[212] Fix | Delete
如果您已决定让这把密钥退休,请选此项
[213] Fix | Delete
“用户标识不再有效”
[214] Fix | Delete
如果这个用户标识不再被使用了,请选此项;这通常用表明某个电子邮
[215] Fix | Delete
件地址已不再有效。
[216] Fix | Delete
[217] Fix | Delete
.
[218] Fix | Delete
[219] Fix | Delete
.gpg.ask_revocation_reason.text
[220] Fix | Delete
您也可以输入一串文字,描述发布这份吊销证书的理由。请尽量使这段文
[221] Fix | Delete
字简明扼要。
[222] Fix | Delete
键入一空行以结束输入。
[223] Fix | Delete
[224] Fix | Delete
.
[225] Fix | Delete
[226] Fix | Delete
[227] Fix | Delete
[228] Fix | Delete
# Local variables:
[229] Fix | Delete
# mode: fundamental
[230] Fix | Delete
# coding: utf-8
[231] Fix | Delete
# End:
[232] Fix | Delete
[233] Fix | Delete
It is recommended that you Edit text format, this type of Fix handles quite a lot in one request
Function