Skip to content

Translate 04-git-server generating-ssh-key (Originally #114 ) #222

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

oldsharp
Copy link
Contributor

Refer to #114 .

@networm networm mentioned this pull request Aug 11, 2015
95 tasks
@networm networm added this to the v1.0.0 milestone Aug 11, 2015
Revise the generating-ssh-key section based on the advice of three
public review records.
Revise the generating-ssh-key section based on my own opinions.
First, you should check to make sure you don't already have a key.
By default, a user's SSH keys are stored in that user's `~/.ssh` directory.
You can easily check to see if you have a key already by going to that directory and listing the contents:
如前所述,许多 Git 服务器都使用 SSH 公钥进行认证。
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

原文“That being said”理论上应该表转折语气,用法同“however”,但是这里显然没有转折。暂译为“如前所述”。请各位一起参谋。

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

如果想要翻译成“然而”的话,可能需要加一些东西,比如“可以用密码登录,但是许多 Git 服务器都使用 SSH 公钥进行认证。是出于安全性的考虑。”
但我认为都可以。

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

其实我个人倾向于认为是原文用法存在问题 ;-)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that being said 貌似很多时候确实表示转折,但是这里我更偏向就是简单的承接,转移话题。

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

那我们就暂定为“如前所述”吧!

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@oldsharp 同意修订为“如前说述”

@oldsharp
Copy link
Contributor Author

@networm 修订工作已经完成。

@oldsharp
Copy link
Contributor Author

@secondwtq @IceNature @jeffsui 请检查。

@@ -35,11 +35,11 @@ The key fingerprint is:
d0:82:24:8e:d7:f1:bb:9b:33:53:96:93:49:da:9b:e3 schacon@mylaptop.local
----

First it confirms where you want to save the key (`.ssh/id_rsa`), and then it asks twice for a passphrase, which you can leave empty if you don't want to type a password when you use the key.
首先 `ssh-keygen` 会确认密钥的存储位置(默认是 `.ssh/id_rsa`),然后它会要求你输入两次密钥口令。如果你不想在使用密钥时输入口令,将其留空即可。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

passphrase 那个地方,突然发现我 密钥口令passwordpassphrasekey 傻傻分不清楚...

@oldsharp 这个如果是有一点加密知识的话倒没事,不过对一般读者来说可能有点 confusing。

@networm 另外在以后的工作中需要注意的是 password 一词翻译的一致性。我查了下 passphrase 一词在全书中只出现了两次,全部翻译为 口令(其他的都是命令输出 You need a passphrase to unlock the secret key for ...),然而 password 一词用的比较多。

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@secondwtq 确实,对没有这方面背景的读者来说,可能会造成困惑。
单就这一处来看,结合上下文,应该还是能区分的。
我们不可能也没必要附注上大段的密码学术语知识。只能靠读者自己了;-)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@oldsharp 好吧。

@secondwtq
Copy link
Contributor

@oldsharp 检查完成。

By default, a user's SSH keys are stored in that user's `~/.ssh` directory.
You can easily check to see if you have a key already by going to that directory and listing the contents:
如前所述,许多 Git 服务器都使用 SSH 公钥进行认证。
为了向 Git 服务器提供 SSH 公钥,每个系统用户在尚未拥有的情况下必须事先生成一对密钥。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

每个系统用户在尚未拥有的情况下必须事先生成一对密钥=》如果系统用户尚未拥有密钥,那么他必须事先生成一份

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed.

@IceNature
Copy link
Contributor

@oldsharp 一个问题,检查完成

@oldsharp
Copy link
Contributor Author

@IceNature 修订完成,请检查。

@oldsharp
Copy link
Contributor Author

@networm ready to merge.

networm added a commit that referenced this pull request Aug 14, 2015
…nerating-ssh-key-original-pull-114

Translate 04-git-server generating-ssh-key (Originally #114 )
@networm networm merged commit 1613ce0 into progit:master Aug 14, 2015
@networm
Copy link
Member

networm commented Aug 14, 2015

@oldsharp @secondwtq @IceNature @jeffsui @oranzhang 已合并入主干。

@oldsharp oldsharp deleted the pull/translate/04-git-server/generating-ssh-key-original-pull-114 branch August 14, 2015 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants