blocks|key|278951|text|该消息表示origin的主机密钥不在受信任的主机文件中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|278952|要解决此问题，请打开到origin的普通SSH连接，SSH将询问您是否要信任远程主机(从Git控制台)：|278953|$+ssh+127.0.0.1
The+authenticity+of+host+'127.0.0.1+(127.0.0.1)'+can't+be+established.
RSA+key+fingerprint+is+<FINGERPRINT>.
Are+you+sure+you+want+to+continue+connecting+(yes/no)?|code-block|syntax|javascript|278954|如果您信任远程主机(即类型为yes)，则SSH会将其密钥添加到已知主机列表中。|278955|在此之后，您应该能够执行git+push+origin。|278956|或者，您也可以手动将origin的密钥添加到.ssh/known_hosts，但这要求您遵循sshd手册页中所述的known_hosts文件格式(+AUTHORIZED_KEYS+file+format+一节)。|BOLD|278957|entityMap|0|LINK|mutability|MUTABLE|url|http://linux.die.net/man/8/sshd^0|5|6|0|B|6|0|0|E|3|0|C|F|0|A|6|M|G|1A|4|1L|B|22|S|1A|4|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|17|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]|$9|1N|A|1O|B|S]]|D|@$9|1P|A|1Q|1|1R]]|E|$]]|$1|T|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]]|U|$V|$5|W|X|Y|E|$Z|10]]]]

The message means that the host key of <code>origin</code> is not present in your trusted hosts file.

To get around this, open a plain SSH connection to <code>origin</code> and SSH will ask you if you want to trust the remote host (from the Git console):

<pre><code>$ ssh 127.0.0.1
The authenticity of host '127.0.0.1 (127.0.0.1)' can't be established.
RSA key fingerprint is &lt;FINGERPRINT&gt;.
Are you sure you want to continue connecting (yes/no)?
</code></pre>

If you trust the remote host (i.e. type <code>yes</code>), SSH will add its key to the list of known hosts.

After that, you should be able to do your <code>git push origin</code>.

As an alternative, you could also manually add the key of <code>origin</code> to <code>.ssh/known_hosts</code> but this requires that you adhere to the format of the <code>known_hosts</code> file as described in the man page of <a href="http://linux.die.net/man/8/sshd" rel="nofollow noreferrer"><code>sshd</code></a> (Section AUTHORIZED_KEYS FILE FORMAT).

blocks|key|2991369|text|仅仅通过ssh连接到主机是不够的，至少在Windows上是这样。这会将主机密钥添加到ssh/known_hosts，但错误仍然存在。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2991370|您需要关闭git+bash窗口并打开一个新窗口。然后清除注册表缓存，然后推送/拉入工作。|2991371|entityMap^0|16|F|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Just ssh'ing to the host is not enough, on Windows at least. That adds the host key to <code>ssh/known_hosts</code> but the error still persists.

You need to close the git bash window and open a new one. Then the registry cache is cleared and the push/pull then works.

blocks|key|280923|text|尝试在Git+Bash提示符下执行"set+%7C+grep+-i+ssh“|type|unstyled|depth|inlineStyleRanges|entityRanges|data|280924|如果你的设置和我的一样，你可能有以下设置：|280925|GIT_SSH='C:\Program+Files+(x86)\PuTTY\plink.exe'
PLINK_PROTOCOL=ssh
SVN_SSH='"C:\\Program+Files+(x86)\\PuTTY\\plink.exe"'|code-block|syntax|javascript|280926|我做了一个|280927|unset+GIT_SSH
unset+PLINK_PROTOCOL
unset+GIT_SVN|280928|在那之后它起作用了，..我猜putty将它的密钥保存在其他地方，即$HOME/.ssh或其他什么地方...(我还在$HOME设置为"C:\Users\usrnam“而不是"/C/Users/usrnam/”的机器上遇到了一个问题。|280929|无论如何，您的里程数可能会有所不同，但这为我解决了问题。:-)|280930|(可能只做未设置的GIT_SSH就足够了，但我很幸运)|280931|注意:如果unset对你不起作用，试试这个：|280932|set+GIT_SSH=|280933|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|17|8|@]|9|@]|A|$G|H]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

Try doing a "set | grep -i ssh" from the Git Bash prompt

If your setup is like mine you probably have these set:

<pre><code>GIT_SSH='C:\Program Files (x86)\PuTTY\plink.exe'
PLINK_PROTOCOL=ssh
SVN_SSH='"C:\\Program Files (x86)\\PuTTY\\plink.exe"'
</code></pre>

I did a 

<pre><code>unset GIT_SSH
unset PLINK_PROTOCOL
unset GIT_SVN
</code></pre>

and it worked after that,.. I guess putty saves its keys somewhere else as $HOME/.ssh or something... (I've also had a problem on a box where $HOME was set to "C:\Users\usrnam" instead of "/C/Users/usrnam/" 

anyway, your mileage may vary, but that fixed it for me. :-)

(probably just doing the unset GIT_SSH is enough, but I was on a roll)

Note: if unset doesn't work for you, try this:

<pre><code>set GIT_SSH=
</code></pre>

blocks|key|282527|text|雷内，你的HOME变量设置不正确。要么将其更改为c:\Users\(your-username)，要么直接更改为%25USERNAME%25。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|282528|entityMap^0|5|4|O|O|1K|A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

Rene, your <code>HOME</code> variable isn't set correctly. Either change it to <code>c:\Users\(your-username)</code> or just to <code>%USERNAME%</code>.

blocks|key|2991392|text|使用Plink的解决方案|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2991393|将this+python+script保存到known_hosts.py|offset|length|style|CODE|2991394|#!+/usr/bin/env+python

#+$Id$
#+Convert+OpenSSH+known_hosts+and+known_hosts2+files+to+"new+format"+PuTTY
#+host+keys.
#+++usage:
#+++++kh2reg.py+[+--win+]+known_hosts1+2+3+4+...+>+hosts.reg
#+++++++Creates+a+Windows+.REG+file+(double-click+to+install).
#+++++kh2reg.py+--unix++++known_hosts1+2+3+4+...+>+sshhostkeys
#+++++++Creates+data+suitable+for+storing+in+~/.putty/sshhostkeys+(Unix).
#+Line+endings+are+someone+else's+problem+as+is+traditional.
#+Developed+for+Python+1.5.2.

import+fileinput
import+base64
import+struct
import+string
import+re
import+sys
import+getopt

def+winmungestr(s):
++++"Duplicate+of+PuTTY's+mungestr()+in+winstore.c:1.10+for+Registry+keys"
++++candot+=+0
++++r+=+""
++++for+c+in+s:
++++++++if+c+in+'+\*?%25~'+or+ord(c)<ord('+')+or+(c+==+'.'+and+not+candot):
++++++++++++r+=+r+%2B+("%25%25%2502X"+%25+ord(c))
++++++++else:
++++++++++++r+=+r+%2B+c
++++++++candot+=+1
++++return+r

def+strtolong(s):
++++"Convert+arbitrary-length+big-endian+binary+data+to+a+Python+long"
++++bytes+=+struct.unpack(">%25luB"+%25+len(s),+s)
++++return+reduce+((lambda+a,+b:+(long(a)+<<+8)+%2B+long(b)),+bytes)

def+longtohex(n):
++++"""Convert+long+int+to+lower-case+hex.

++++Ick,+Python+(at+least+in+1.5.2)+doesn't+appear+to+have+a+way+to
++++turn+a+long+int+into+an+unadorned+hex+string+--+%25+gets+upset+if+the
++++number+is+too+big,+and+raw+hex()+uses+uppercase+(sometimes),+and
++++adds+unwanted+"0x...L"+around+it."""

++++plain=string.lower(re.match(r"0x([0-9A-Fa-f]*)l?$",+hex(n),+re.I).group(1))
++++return+"0x"+%2B+plain

output_type+=+'windows'

try:
++++optlist,+args+=+getopt.getopt(sys.argv[1:],+'',+[+'win',+'unix'+])
++++if+filter(lambda+x:+x[0]+==+'--unix',+optlist):
++++++++output_type+=+'unix'
except+getopt.error,+e:
++++sys.stderr.write(str(e)+%2B+"\n")
++++sys.exit(1)

if+output_type+==+'windows':
++++#+Output+REG+file+header.
++++sys.stdout.write("""REGEDIT4

[HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys]
""")

#+Now+process+all+known_hosts+input.
for+line+in+fileinput.input(args):

++++try:
++++++++#+Remove+leading/trailing+whitespace+(should+zap+CR+and+LF)
++++++++line+=+string.strip+(line)

++++++++#+Skip+blanks+and+comments
++++++++if+line+==+''+or+line[0]+==+'#':
++++++++++++raise+"Skipping+input+line"

++++++++#+Split+line+on+spaces.
++++++++fields+=+string.split+(line,+'+')

++++++++#+Common+fields
++++++++hostpat+=+fields[0]
++++++++magicnumbers+=+[]+++#+placeholder
++++++++keytype+=+""++++++++#+placeholder

++++++++#+Grotty+heuristic+to+distinguish+known_hosts+from+known_hosts2:
++++++++#+is+second+field+entirely+decimal+digits?
++++++++if+re.match+(r"\d*$",+fields[1]):

++++++++++++#+Treat+as+SSH-1-type+host+key.
++++++++++++#+Format:+hostpat+bits10+exp10+mod10+comment...
++++++++++++#+(PuTTY+doesn't+store+the+number+of+bits.)
++++++++++++magicnumbers+=+map+(long,+fields[2:4])
++++++++++++keytype+=+"rsa"

++++++++else:

++++++++++++#+Treat+as+SSH-2-type+host+key.
++++++++++++#+Format:+hostpat+keytype+keyblob64+comment...
++++++++++++sshkeytype,+blob+=+fields[1],+base64.decodestring+(fields[2])

++++++++++++#+'blob'+consists+of+a+number+of
++++++++++++#+++uint32++++N+(big-endian)
++++++++++++#+++uint8[N]++field_data
++++++++++++subfields+=+[]
++++++++++++while+blob:
++++++++++++++++sizefmt+=+">L"
++++++++++++++++(size,)+=+struct.unpack+(sizefmt,+blob[0:4])
++++++++++++++++size+=+int(size)+++#+req'd+for+slicage
++++++++++++++++(data,)+=+struct.unpack+(">%25lus"+%25+size,+blob[4:size%2B4])
++++++++++++++++subfields.append(data)
++++++++++++++++blob+=+blob+[struct.calcsize(sizefmt)+%2B+size+:+]

++++++++++++#+The+first+field+is+keytype+again,+and+the+rest+we+can+treat+as
++++++++++++#+an+opaque+list+of+bignums+(same+numbers+and+order+as+stored
++++++++++++#+by+PuTTY).+(currently+embedded+keytype+is+ignored+entirely)
++++++++++++magicnumbers+=+map+(strtolong,+subfields[1:])

++++++++++++#+Translate+key+type+into+something+PuTTY+can+use.
++++++++++++if+++sshkeytype+==+"ssh-rsa":+++keytype+=+"rsa2"
++++++++++++elif+sshkeytype+==+"ssh-dss":+++keytype+=+"dss"
++++++++++++else:
++++++++++++++++raise+"Unknown+SSH+key+type",+sshkeytype

++++++++#+Now+print+out+one+line+per+host+pattern,+discarding+wildcards.
++++++++for+host+in+string.split+(hostpat,+','):
++++++++++++if+re.search+(r"[*?!]",+host):
++++++++++++++++sys.stderr.write("Skipping+wildcard+host+pattern+'%25s'\n"
+++++++++++++++++++++++++++++++++%25+host)
++++++++++++++++continue
++++++++++++elif+re.match+(r"\%7C",+host):
++++++++++++++++sys.stderr.write("Skipping+hashed+hostname+'%25s'\n"+%25+host)
++++++++++++++++continue
++++++++++++else:
++++++++++++++++m+=+re.match+(r"\[([%5E]]*)\]:(\d*)$",+host)
++++++++++++++++if+m:
++++++++++++++++++++(host,+port)+=+m.group(1,2)
++++++++++++++++++++port+=+int(port)
++++++++++++++++else:
++++++++++++++++++++port+=+22
++++++++++++++++#+Slightly+bizarre+output+key+format:+'type@port:hostname'
++++++++++++++++#+XXX:+does+PuTTY+do+anything+useful+with+literal+IP[v4]s?
++++++++++++++++key+=+keytype+%2B+("@%25d:%25s"+%25+(port,+host))
++++++++++++++++value+=+string.join+(map+(longtohex,+magicnumbers),+',')
++++++++++++++++if+output_type+==+'unix':
++++++++++++++++++++#+Unix+format.
++++++++++++++++++++sys.stdout.write('%25s+%25s\n'+%25+(key,+value))
++++++++++++++++else:
++++++++++++++++++++#+Windows+format.
++++++++++++++++++++#+XXX:+worry+about+double+quotes?
++++++++++++++++++++sys.stdout.write("\"%25s\"=\"%25s\"\n"
+++++++++++++++++++++++++++++++++++++%25+(winmungestr(key),+value))

++++except+"Unknown+SSH+key+type",+k:
++++++++sys.stderr.write("Unknown+SSH+key+type+'%25s',+skipping\n"+%25+k)
++++except+"Skipping+input+line":
++++++++pass|code-block|syntax|javascript|2991395|已在Win7x64和Python+2.7上测试。|2991396|然后运行：|2991397|ssh-keyscan+-t+rsa+bitbucket.org+>>~/.ssh/known_hosts
python+--win+known_hosts.py+>known_hosts.reg
start+known_hosts.reg|2991398|并选择导入到注册表中。keyscan将检索该域的公钥(我在使用bitbucket时遇到了问题)，然后python脚本将其转换为Plink格式。|2991399|entityMap|0|LINK|mutability|MUTABLE|url|http://svn.tartarus.org/sgt/putty/contrib/kh2reg.py?view=markup|1|http://www.python.org/download/releases/^0|0|M|E|1|I|0|0|0|A|A|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|H|3|I|5|J|7|1B|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1C|8|@]|9|@$D|1D|E|1E|1|1F]]|A|$]]|$1|O|3|P|5|6|7|1G|8|@]|9|@]|A|$]]|$1|Q|3|R|5|J|7|1H|8|@]|9|@]|A|$K|L]]|$1|S|3|T|5|6|7|1I|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]|12|$5|X|Y|Z|A|$10|13]]]]

<h2>Solution with Plink</h2>

Save <a href="http://svn.tartarus.org/sgt/putty/contrib/kh2reg.py?view=markup" rel="nofollow">this python script</a> to <code>known_hosts.py</code>:

<pre><code>#! /usr/bin/env python

# $Id$
# Convert OpenSSH known_hosts and known_hosts2 files to "new format" PuTTY
# host keys.
# usage:
# kh2reg.py [ --win ] known_hosts1 2 3 4 ... &gt; hosts.reg
# Creates a Windows .REG file (double-click to install).
# kh2reg.py --unix known_hosts1 2 3 4 ... &gt; sshhostkeys
# Creates data suitable for storing in ~/.putty/sshhostkeys (Unix).
# Line endings are someone else's problem as is traditional.
# Developed for Python 1.5.2.

import fileinput
import base64
import struct
import string
import re
import sys
import getopt

def winmungestr(s):
 "Duplicate of PuTTY's mungestr() in winstore.c:1.10 for Registry keys"
 candot = 0
 r = ""
 for c in s:
 if c in ' \*?%~' or ord(c)&lt;ord(' ') or (c == '.' and not candot):
 r = r + ("%%%02X" % ord(c))
 else:
 r = r + c
 candot = 1
 return r

def strtolong(s):
 "Convert arbitrary-length big-endian binary data to a Python long"
 bytes = struct.unpack("&gt;%luB" % len(s), s)
 return reduce ((lambda a, b: (long(a) &lt;&lt; 8) + long(b)), bytes)

def longtohex(n):
 """Convert long int to lower-case hex.

 Ick, Python (at least in 1.5.2) doesn't appear to have a way to
 turn a long int into an unadorned hex string -- % gets upset if the
 number is too big, and raw hex() uses uppercase (sometimes), and
 adds unwanted "0x...L" around it."""

 plain=string.lower(re.match(r"0x([0-9A-Fa-f]*)l?$", hex(n), re.I).group(1))
 return "0x" + plain

output_type = 'windows'

try:
 optlist, args = getopt.getopt(sys.argv[1:], '', [ 'win', 'unix' ])
 if filter(lambda x: x[0] == '--unix', optlist):
 output_type = 'unix'
except getopt.error, e:
 sys.stderr.write(str(e) + "\n")
 sys.exit(1)

if output_type == 'windows':
 # Output REG file header.
 sys.stdout.write("""REGEDIT4

[HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys]
""")

# Now process all known_hosts input.
for line in fileinput.input(args):

 try:
 # Remove leading/trailing whitespace (should zap CR and LF)
 line = string.strip (line)

 # Skip blanks and comments
 if line == '' or line[0] == '#':
 raise "Skipping input line"

 # Split line on spaces.
 fields = string.split (line, ' ')

 # Common fields
 hostpat = fields[0]
 magicnumbers = [] # placeholder
 keytype = "" # placeholder

 # Grotty heuristic to distinguish known_hosts from known_hosts2:
 # is second field entirely decimal digits?
 if re.match (r"\d*$", fields[1]):

 # Treat as SSH-1-type host key.
 # Format: hostpat bits10 exp10 mod10 comment...
 # (PuTTY doesn't store the number of bits.)
 magicnumbers = map (long, fields[2:4])
 keytype = "rsa"

 else:

 # Treat as SSH-2-type host key.
 # Format: hostpat keytype keyblob64 comment...
 sshkeytype, blob = fields[1], base64.decodestring (fields[2])

 # 'blob' consists of a number of
 # uint32 N (big-endian)
 # uint8[N] field_data
 subfields = []
 while blob:
 sizefmt = "&gt;L"
 (size,) = struct.unpack (sizefmt, blob[0:4])
 size = int(size) # req'd for slicage
 (data,) = struct.unpack ("&gt;%lus" % size, blob[4:size+4])
 subfields.append(data)
 blob = blob [struct.calcsize(sizefmt) + size : ]

 # The first field is keytype again, and the rest we can treat as
 # an opaque list of bignums (same numbers and order as stored
 # by PuTTY). (currently embedded keytype is ignored entirely)
 magicnumbers = map (strtolong, subfields[1:])

 # Translate key type into something PuTTY can use.
 if sshkeytype == "ssh-rsa": keytype = "rsa2"
 elif sshkeytype == "ssh-dss": keytype = "dss"
 else:
 raise "Unknown SSH key type", sshkeytype

 # Now print out one line per host pattern, discarding wildcards.
 for host in string.split (hostpat, ','):
 if re.search (r"[*?!]", host):
 sys.stderr.write("Skipping wildcard host pattern '%s'\n"
 % host)
 continue
 elif re.match (r"\|", host):
 sys.stderr.write("Skipping hashed hostname '%s'\n" % host)
 continue
 else:
 m = re.match (r"\[([^]]*)\]:(\d*)$", host)
 if m:
 (host, port) = m.group(1,2)
 port = int(port)
 else:
 port = 22
 # Slightly bizarre output key format: 'type@port:hostname'
 # XXX: does PuTTY do anything useful with literal IP[v4]s?
 key = keytype + ("@%d:%s" % (port, host))
 value = string.join (map (longtohex, magicnumbers), ',')
 if output_type == 'unix':
 # Unix format.
 sys.stdout.write('%s %s\n' % (key, value))
 else:
 # Windows format.
 # XXX: worry about double quotes?
 sys.stdout.write("\"%s\"=\"%s\"\n"
 % (winmungestr(key), value))

 except "Unknown SSH key type", k:
 sys.stderr.write("Unknown SSH key type '%s', skipping\n" % k)
 except "Skipping input line":
 pass
</code></pre>

Tested on Win7x64 and <a href="http://www.python.org/download/releases/" rel="nofollow">Python 2.7</a>.

Then run:

<pre><code>ssh-keyscan -t rsa bitbucket.org &gt;&gt;~/.ssh/known_hosts
python --win known_hosts.py &gt;known_hosts.reg
start known_hosts.reg
</code></pre>

And choose to import into the registry. The keyscan will retrieve the public key for the domain (I had my problems with bitbucket), and then the python script will convert it to Plink format.

blocks|key|280947|text|对于那些通过标准命令提示符使用PuTTY在Windows上设置MSYS+Git的用户，将主机添加到PuTTY缓存的方法是运行|type|unstyled|depth|inlineStyleRanges|entityRanges|data|280948|>+plink.exe+<host>|code-block|syntax|javascript|280949|例如：|280950|>+plink.exe+codebasehq.com

The+server's+host+key+is+not+cached+in+the+registry.+You
have+no+guarantee+that+the+server+is+the+computer+you
think+it+is.
The+server's+rsa2+key+fingerprint+is:
ssh-rsa+2048+2e:db:b6:22:f7:bd:48:f6:da:72:bf:59:d7:75:d7:4e
If+you+trust+this+host,+enter+"y"+to+add+the+key+to
PuTTY's+cache+and+carry+on+connecting.
If+you+want+to+carry+on+connecting+just+once,+without
adding+the+key+to+the+cache,+enter+"n".
If+you+do+not+trust+this+host,+press+Return+to+abandon+the
connection.
Store+key+in+cache?+(y/n)|280951|只需回答y，然后Ctrl%2BC其余部分。|offset|length|style|CODE|280952|不过一定要检查指纹。这个警告是有充分理由的。某些git服务的指纹(请编辑以添加更多内容)：|280953|16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48|280954|Bitbucket：97:8c:1b:f2:6f:14:6b:5c:3b:ec:aa:46:46:74:7c:40|unordered-list-item|280955|
|280956|Gitorious：7e:af:8d:ec:f0:39:5e:ba:52:16:ce:19:fa:d4:b8:7d|280957|
：|280958|GitHub|280959|280960|entityMap|0|LINK|mutability|MUTABLE|url|https://help.github.com/articles/what-are-github-s-ssh-key-fingerprints|1|https://confluence.atlassian.com/display/BITBUCKET/Use%2Bthe%2BSSH%2Bprotocol%2Bwith%2BBitbucket|2|https://gitorious.org/about/faq^0|0|0|0|0|4|1|0|0|0|1B|0|1B|0|0|A|1B|A|1B|1|0|0|A|1B|A|1B|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1J|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1K|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|1L|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|1M|8|@$M|1N|N|1O|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1P|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1Q|8|@$M|1R|N|1S|O|P]]|9|@$M|1T|N|1U|1|1V]]|A|$]]|$1|U|3|V|5|W|7|1W|8|@$M|1X|N|1Y|O|P]]|9|@$M|1Z|N|20|1|21]]|A|$]]|$1|X|3|Y|5|6|7|22|8|@]|9|@]|A|$]]|$1|Z|3|10|5|W|7|23|8|@$M|24|N|25|O|P]]|9|@$M|26|N|27|1|28]]|A|$]]|$1|11|3|12|5|6|7|29|8|@]|9|@]|A|$]]|$1|13|3|14|5|W|7|2A|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]]|17|$18|$5|19|1A|1B|A|$1C|1D]]|1E|$5|19|1A|1B|A|$1C|1F]]|1G|$5|19|1A|1B|A|$1C|1H]]]]

For those of you who are setting up MSYS Git on Windows using PuTTY via the standard command prompt, the way to add a host to PuTTY's cache is to run

<pre><code>&gt; plink.exe &lt;host&gt;
</code></pre>

For example:

<pre><code>&gt; plink.exe codebasehq.com

The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's rsa2 key fingerprint is:
ssh-rsa 2048 2e:db:b6:22:f7:bd:48:f6:da:72:bf:59:d7:75:d7:4e
If you trust this host, enter "y" to add the key to
PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n)
</code></pre>

Just answer <code>y</code>, and then Ctrl+C the rest.

Do check the fingerprint though. This warning is there for a good reason. Fingerprints for some git services (please edit to add more):

<ul>
<li>GitHub: <a href="https://help.github.com/articles/what-are-github-s-ssh-key-fingerprints" rel="noreferrer"><code>16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48</code></a></li>
<li>Bitbucket: <a href="https://confluence.atlassian.com/display/BITBUCKET/Use+the+SSH+protocol+with+Bitbucket" rel="noreferrer"><code>97:8c:1b:f2:6f:14:6b:5c:3b:ec:aa:46:46:74:7c:40</code></a></li>
<li>Gitorious: <a href="https://gitorious.org/about/faq" rel="noreferrer"><code>7e:af:8d:ec:f0:39:5e:ba:52:16:ce:19:fa:d4:b8:7d</code></a></li>
</ul>

blocks|key|280983|text|我怀疑您的GIT_SSH环境变量设置为%25ProgramFiles(x86)%25\putty\plink.exe。由于某些原因，PLink不使用用户目录中的.ssh/known_hosts文件来存储远程主机密钥。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|280984|如果这确实是您的情况，如果您想使用pageant，则可能是故意这样做的，那么您需要首先使用PLink连接到主机。|280985|"$GIT_SSH"+user@hostname|code-block|syntax|javascript|280986|您应该会收到类似的消息|280987|The+server's+host+key+is+not+cached+in+the+registry.+You
have+no+guarantee+that+the+server+is+the+computer+you
think+it+is.
The+server's+rsa2+key+fingerprint+is:
ssh-rsa+2048+86:7b:1b:12:85:35:8a:b7:98:b6:d2:97:5e:96:58:1d
If+you+trust+this+host,+enter+"y"+to+add+the+key+to
PuTTY's+cache+and+carry+on+connecting.
If+you+want+to+carry+on+connecting+just+once,+without
adding+the+key+to+the+cache,+enter+"n".
If+you+do+not+trust+this+host,+press+Return+to+abandon+the
connection.
Store+key+in+cache?+(y/n)|280988|一旦您回答了问题的y并成功连接到远程主机，您就应该完成了所有设置。继续，再试一次推送。|280989|entityMap^0|5|7|J|Z|24|G|0|0|0|0|0|9|1|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|13|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|14|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|T|$]]

I suspect that your <code>GIT_SSH</code> environment variable is set to <code>%ProgramFiles(x86)%\putty\plink.exe</code>.
For some reason, PLink does not use the <code>.ssh/known_hosts</code> file in your user directory to store the remote hosts keys.

If this is actually your case, and it might be so on purpose if you want to use pageant, you need to use PLink to connect to the host first.

<pre><code>"$GIT_SSH" user@hostname
</code></pre>

You should get a similar message

<pre><code>The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's rsa2 key fingerprint is:
ssh-rsa 2048 86:7b:1b:12:85:35:8a:b7:98:b6:d2:97:5e:96:58:1d
If you trust this host, enter "y" to add the key to
PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n)
</code></pre>

Once you have answered <code>y</code> to the question and successfully connected to the remote host, you should be all set. Go ahead and try your push again.

blocks|key|284560|text|有同样的问题，并且忘记了在实际存储库的端口上连接到SSH，而不仅仅是一般的SSH端口，那么主机密钥就不同了！|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|284561|entityMap^0|M|W|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Had the same issue, and forget to connect to SSH on port where is actuall repository, not just general SSH port, then the host key is different!

blocks|key|282581|text|当我试图在我的Windows7机器上克隆存储库时，我也遇到了同样的问题。我尝试了这里提到的大多数答案。他们对我来说都不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|282582|对我来说起作用的是，运行Pageant(身份验证代理)程序。一旦Pageant在后台运行，我就可以克隆、推送和拉入存储库。这对我来说很有效，可能是因为我设置了我的公钥，每当第一次使用它时，都需要一个密码&+Pageant启动。|offset|length|style|BOLD|282583|entityMap^0|0|K|2L|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I too had the same issue when I was trying to clone a repository on my Windows 7 machine. I tried most of the answers mentioned here. None of them worked for me. 

What worked for me was, running the Pageant (Putty authentication agent) program. Once the Pageant was running in the background I was able to clone, push &amp; pull from/to the repository. This worked for me, may be because I've setup my public key such that whenever it is used for the first time a password is required &amp; the Pageant starts up.

blocks|key|2991589|text|只需打开Putty并尝试建立到您想要推送代码的远程服务器的连接。当对话框出现时，按Yes(您信任remote)，然后一切正常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2991590|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Just open Putty and try to establish connection to remote server you want to push your code.
when the dialog appears press Yes(you trust remote) then everything would be OK.

blocks|key|284626|text|从PuTTY更改为OpenSSH为我解决了这个问题，不需要取消设置GIT_SSH等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|284627|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Changing from PuTTY to OpenSSH fixed this issue for me, without needing to unset GIT_SSH, etc.

blocks|key|2991650|text|我用这个workaround解决了类似的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2991651|您只需切换到Embedded+Git，按下“是”按钮，然后切换回系统Git即可。|2991652|您可以在以下位置找到此选项|2991653|Tools+->+Options+->+Git|code-block|syntax|javascript|2991654|entityMap|0|LINK|mutability|MUTABLE|url|https://confluence.atlassian.com/display/SOURCETREEKB/Trust%2BA%2BServer's%2BHost%2BKey%2Bwhen%2BNo%2BButton%2Bis%2BAvailable%2Bto%2BTrust%2BIt^0|4|A|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|C|$K|L]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

I solved similar problem using this <a href="https://confluence.atlassian.com/display/SOURCETREEKB/Trust+A+Server&#39;s+Host+Key+when+No+Button+is+Available+to+Trust+It" rel="nofollow">workaround</a>.

You just have to switch to Embedded Git, push, press Yes button and then switch back to System Git.

You can find this option in

<pre><code>Tools -&gt; Options -&gt; Git
</code></pre>

blocks|key|2991673|text|直接使用Bash添加主机并不能解决问题，在Git扩展中使用'Fetch+all‘时仍然会出现错误。通过在一个分支上使用'Pull‘，所需的主机由带有Bash弹出屏幕的Git扩展自动添加。完成此操作后，我可以再次使用“Fetch+All”。不确定Git扩展有什么不同之处。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2991674|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Adding the host directly with Bash didn't solve the issue, the error still occurred when using 'Fetch all' in Git Extensions. By using 'Pull' on one branch, the required host was added automatically by Git Extensions with a Bash pop-up screen. After doing this I was able to use 'Fetch All' again. Not sure what is done by Git Extensions differently.

blocks|key|2991693|text|我已经尝试了上面所有的方法，但它们都不能在我的笔记本电脑上解决同样的问题。最后，我没有在git+bash中将分支推送到原点，而是使用TortoiseGit的push选项进行推送，然后弹出一个窗口，要求我将新的主机密钥添加到缓存中，单击yes按钮后，现在一切正常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2991694|希望这对你们所有人都有帮助。|2991695|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I have tried all the methods above but none of them could fix the same issue on my laptop. Finally instead of pushing the branch to origin in git bash, I trun to use TortoiseGit's push option to do the pushing, then a window pops-up to ask me to add the new host key to cache, after clicking the yes button, everything goes fine now.

Hope it helps to you all.

blocks|key|282661|text|工作环境：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|282662|Windows+10|282663|git|unordered-list-item|282664|
|282665|putty|282666|
的|282667|282668|282669|优先：根据Regedit删除注册表中的putty+known_hosts。|282670|然后：在Window的cmd中执行命令%25GIT_SSH%25+user@hostname解决了这个问题。|CODE|282671|希望能对大家有所帮助。|282672|entityMap^0|0|5|0|0|0|0|0|0|0|0|0|3|0|0|3|J|N|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|14|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|15|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|16|8|@]|D|@]|E|$]]|$1|M|3|N|5|J|7|17|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|18|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|J|7|19|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|W]]|D|@]|E|$]]|$1|X|3|Y|5|6|7|1J|8|@]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]]|10|$]]

Working environment: 

<ul>
<li>Windows 10</li>
<li>git</li>
<li>putty</li>
</ul>

First: Delete putty known_hosts in registy according to the Regedit. 
Then: Executing the command <code>%GIT_SSH% user@hostname</code> in Window's cmd solves the problem.

Hope it helps you all.

blocks|key|3205405|text|我换了硬盘，安装了Windows。当尝试上传文件时收到此命令窗口。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3205406|我按下"y"，然后按Ctrl+%2B+C。打开putty.exe，添加一个旧的键，然后返回到git并推送文件。|offset|length|style|CODE|3205407|entityMap^0|0|L|9|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I changed a hard disk, installed Windows. When tried to upload files received this command window.

I pressed "y", then Ctrl + C. Opened <code>putty.exe</code>, added an old key ther returned to git and pushed files.

blocks|key|2991758|text|只需卸载Git扩展并选择OpenSSH重新安装，而不是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2991759|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Just uninstall Git Extensions and Install again by choosing OpenSSH instead of

blocks|key|284698|text|在Windows7或Windows10中，对我起作用的技巧是删除GIT_SSH系统变量。它以前被设置为使用Plink，现在被Putty取代。这导致了Plink.exe错误|type|unstyled|depth|inlineStyleRanges|entityRanges|data|284699|还有一个旧的Git+(32位版本)安装和更新到Git(例如Git-2.20.1-64-bit.exe)，因为PC是64位操作系统。|284700|无论如何，Git甚至没有使用Putty/Plink，因为在Git安装中，默认使用Open+SSH。|284701|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In Windows 7 or 10, the trick that worked for me is deleting the GIT_SSH system variable. It was set before to use Plink, and now was replaced by Putty. This was causing Plink.exe error

There was also an old installation of Git (32-bit version) and updating to Git(e.g. Git-2.20.1-64-bit.exe) since the PC was 64-bit OS.

Anyway the Putty/Plink was not even used by Git since in the Git installation it was default to use Open SSH.

blocks|key|282771|text|正如Roman+Starkov回答的那样，plink需要将主机添加到它的缓存中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|282772|对于使用Git+Extensions的用户|BOLD|282773|282774|Open+Git+Extensions|ordered-list-item|282775|转至工具->设置->+SSH|282776|将路径复制到"plink.exe“(如果使用PuTTY)+/+"klink.exe”(如果使用KiTTY)|282777|在控制台中，运行以下命令：|282778|<代码>G213|282779|(替换为实际路径)|282780|<the+path+to+plink/klink.exe>+<address+to+the+server>|code-block|syntax|javascript|282781|例如：|282782|%25ProgramData%25\chocolatey\lib\kitty\tools\klink.exe+codebasehq.com|282783|注意:确保使用与扩展相同的plink/klink！|282784|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/12448986/68955^0|L|5|2|D|0|0|4|E|0|0|0|0|0|0|0|0|0|0|0|0|8|0^^$0|@$1|2|3|4|5|6|7|1F|8|@$9|1G|A|1H|B|C]]|D|@$9|1I|A|1J|1|1K]]|E|$]]|$1|F|3|G|5|6|7|1L|8|@$9|1M|A|1N|B|H]]|D|@]|E|$]]|$1|I|3|-4|5|6|7|1O|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1P|8|@]|D|@]|E|$]]|$1|M|3|N|5|L|7|1Q|8|@]|D|@]|E|$]]|$1|O|3|P|5|L|7|1R|8|@]|D|@]|E|$]]|$1|Q|3|R|5|L|7|1S|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1T|8|@]|D|@]|E|$]]|$1|U|3|V|5|6|7|1U|8|@]|D|@]|E|$]]|$1|W|3|X|5|Y|7|1V|8|@]|D|@]|E|$Z|10]]|$1|11|3|12|5|6|7|1W|8|@]|D|@]|E|$]]|$1|13|3|14|5|Y|7|1X|8|@]|D|@]|E|$Z|10]]|$1|15|3|16|5|6|7|1Y|8|@$9|1Z|A|20|B|H]]|D|@]|E|$]]|$1|17|3|-4|5|6|7|21|8|@]|D|@]|E|$]]]|18|$19|$5|1A|1B|1C|E|$1D|1E]]]]

As answered by <a href="https://stackoverflow.com/a/12448986/68955">Roman Starkov</a>, <code>plink</code> needs to add the host to it's cache.

For people using Git Extensions:

<ol>
<li>Open Git Extensions</li>
<li>Go to Tools -> Settings -> SSH</li>
<li>Copy the path to "plink.exe" (if using PuTTY) / "klink.exe" (if using KiTTY)</li>
<li>In a console, run the following command:</li>
</ol>

(replace with the actual paths)

<pre><code>&lt;the path to plink/klink.exe&gt; &lt;address to the server&gt;
</code></pre>

e.g.

<pre><code>%ProgramData%\chocolatey\lib\kitty\tools\klink.exe codebasehq.com
</code></pre>

Note: Make sure to use the same plink/klink that Git Extensions is using!

blocks|key|2991869|text|如果您在使用ATLASSIAN+SOURCETREE执行git推送/拉入操作时收到有关无法识别主机密钥的消息，您将无法回答y/n，并且推送/拉入操作将在不缓存密钥的情况下中止。但是，转到SSH+Tools->Options+(General选项卡)并将SourceTree客户端(在SSH+Client+Configuration下)从PuTTY更改为OpenSSH，这样就可以在不更改任何其他内容的情况下缓存密钥。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2991870|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you receive the message about the unrecognized host key while doing git push/pull operations using ATLASSIAN SOURCETREE you do not have the ability to answer y/n and the push/pull operation will be aborted without caching the key. However going to SourceTree Tools-&gt;Options (General Tab) and changing the SSH Client under (under SSH Client Configuration) from PuTTY to OpenSSH will allow the key to be cached without changing anything else.

I try to push changes from my local repo to a remote repo. When I type:

<pre><code>git push origin
</code></pre>

I get the following error:

<pre><code>The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's rsa2 key fingerprint is:
ssh-rsa 2048 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
Connection abandoned.
fatal: The remote end hung up unexpectedly
</code></pre>

How can I solve this? I'm using git from the command line in Windows 7.

Edit

When I try to do a simple ssh

<pre><code>ssh user@hostname
</code></pre>

I get the following error:

<pre><code>Could not create directory '/c//%HOMEDRIVE%%HOMEPATH%/.ssh'.
percent_expand: unknown key %H
</code></pre>

Somehow it will not create the directory, because the path is invalid. How to fix this?

@eckes: Edit2

My Home is set to <code>%HOMEDRIVE%%HOMEPATH%</code> is this correct?

git - Server host key not cached

身份验证

服务器

Bitbucket

Windows

Python

GitHub

Unix

我尝试将更改从本地存储库推送到远程存储库。当我键入时：git push origin我得到以下错误：The server's host key is not cached in the registry. Youhave no guarantee that the server is the computer yout...

问git -服务器主机密钥未缓存
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问git -服务器主机密钥未缓存EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问git -服务器主机密钥未缓存
EN