每次使用git commit / git stash都会要求输入密码。

3
我购买了一台新电脑,现在当我尝试执行$ git commit$ git stash 时,会提示输入密码。 You need a passphrase to unlock the secret key for user: "Anthony Mayfield <contact@anthonymayfield.com>" 2048-bit RSA key, ID 489A9781, created 2016-04-20 我该怎么做才能防止这种情况发生呢?谢谢。
Gitconfig:
[alias]

    # View abbreviated SHA, description, and history graph of the latest 20 commits
    l = log --pretty=oneline -n 20 --graph --abbrev-commit

    # View the current working tree status using the short format
    s = status -s

    # Show the diff between the latest commit and the current state
    d = !"git diff-index --quiet HEAD -- || clear; git --no-pager diff --patch-with-stat"

    # `git di $number` shows the diff between the state `$number` revisions ago and the current state
    di = !"d() { git diff --patch-with-stat HEAD~$1; }; git diff-index --quiet HEAD -- || clear; d"

    # Pull in remote changes for the current repository and all its submodules
    p = !"git pull; git submodule foreach git pull origin master"

    # Clone a repository including all submodules
    c = clone --recursive

    # Commit all changes
    ca = !git add -A && git commit -av

    # Switch to a branch, creating it if necessary
    go = "!f() { git checkout -b \"$1\" 2> /dev/null || git checkout \"$1\"; }; f"

    # Show verbose output about tags, branches or remotes
    tags = tag -l
    branches = branch -a
    remotes = remote -v

    # Amend the currently staged files to the latest commit
    amend = commit --amend --reuse-message=HEAD

    # Credit an author on the latest commit
    credit = "!f() { git commit --amend --author \"$1 <$2>\" -C HEAD; }; f"

    # Interactive rebase with the given number of latest commits
    reb = "!r() { git rebase -i HEAD~$1; }; r"

    # Remove the old tag with this name and tag the latest commit with it.
    retag = "!r() { git tag -d $1 && git push origin :refs/tags/$1 && git tag $1; }; r"

    # Find branches containing commit
    fb = "!f() { git branch -a --contains $1; }; f"

    # Find tags containing commit
    ft = "!f() { git describe --always --contains $1; }; f"

    # Find commits by source code
    fc = "!f() { git log --pretty=format:'%C(yellow)%h  %Cblue%ad  %Creset%s%Cgreen  [%cn] %Cred%d' --decorate --date=short -S$1; }; f"

    # Find commits by commit message
    fm = "!f() { git log --pretty=format:'%C(yellow)%h  %Cblue%ad  %Creset%s%Cgreen  [%cn] %Cred%d' --decorate --date=short --grep=$1; }; f"

    # Remove branches that have already been merged with master
    # a.k.a. ‘delete merged’
    dm = "!git branch --merged | grep -v '\\*' | xargs -n 1 git branch -d"

    # List contributors with number of commits
    contributors = shortlog --summary --numbered

    # Merge GitHub pull request on top of the current branch or,
    # if a branch name is specified, on top of the specified branch
    mpr = "!f() { \
        declare currentBranch=\"$(git symbolic-ref --short HEAD)\"; \
        declare branch=\"${2:-$currentBranch}\"; \
        if [ $(printf \"%s\" \"$1\" | grep '^[0-9]\\+$' > /dev/null; printf $?) -eq 0 ]; then \
            git fetch origin refs/pull/$1/head:pr/$1 && \
            git checkout -B $branch && \
            git rebase $branch pr/$1 && \
            git checkout -B $branch && \
            git merge pr/$1 && \
            git branch -D pr/$1 && \
            git commit --amend -m \"$(git log -1 --pretty=%B)\n\nCloses #$1.\"; \
        fi \
    }; f"

[apply]

    # Detect whitespace errors when applying a patch
    whitespace = fix

[core]

    # Use custom `.gitignore` and `.gitattributes`
    excludesfile = ~/.gitignore
    attributesfile = ~/.gitattributes

    # Treat spaces before tabs and all kinds of trailing whitespace as an error
    # [default] trailing-space: looks for spaces at the end of a line
    # [default] space-before-tab: looks for spaces before tabs at the beginning of a line
    whitespace = space-before-tab,-indent-with-non-tab,trailing-space

    # Make `git rebase` safer on OS X
    # More info: <http://www.git-tower.com/blog/make-git-rebase-safe-on-osx/>
    trustctime = false

    # Prevent showing files whose names contain non-ASCII symbols as unversioned.
    # http://michael-kuehnel.de/git/2014/11/21/git-mac-osx-and-german-umlaute.html
    precomposeunicode = false

[color]

    # Use colors in Git commands that are capable of colored output when
    # outputting to the terminal. (This is the default setting in Git ≥ 1.8.4.)
    ui = auto

[color "branch"]

    current = yellow reverse
    local = yellow
    remote = green

[color "diff"]

    meta = yellow bold
    frag = magenta bold # line info
    old = red # deletions
    new = green # additions

[color "status"]

    added = yellow
    changed = green
    untracked = cyan

[commit]

    # https://help.github.com/articles/signing-commits-using-gpg/
    gpgsign = true

[diff]

    # Detect copies as well as renames
    renames = copies

[diff "bin"]

    # Use `hexdump` to diff binary files
    textconv = hexdump -v -C

[help]

    # Automatically correct and execute mistyped commands
    autocorrect = 1

[merge]

    # Include summaries of merged commits in newly created merge commit messages
    log = true

[push]

    # Use the Git 1.x.x default to avoid errors on machines with old Git
    # installations. To use `simple` instead, add this to your `~/.extra` file:
    # `git config --global push.default simple`. See http://git.io/mMah-w.
    default = matching
    # Make `git push` push relevant annotated tags when pushing branches out.
    followTags = true

# URL shorthands

[url "git@github.com:"]

    insteadOf = "gh:"
    pushInsteadOf = "github:"
    pushInsteadOf = "git://github.com/"

[url "git://github.com/"]

    insteadOf = "github:"

[url "git@gist.github.com:"]

    insteadOf = "gst:"
    pushInsteadOf = "gist:"
    pushInsteadOf = "git://gist.github.com/"

[url "git://gist.github.com/"]

    insteadOf = "gist:"
[user]
    email = contact@anthonymayfield.com
    signingkey = [scrubbed]
[credential]
    helper = osxkeychain

你能重新生成RSA密钥吗?https://help.github.com/articles/generating-an-ssh-key/并且不要添加密码保护。 - cgmckeever
这个网址的解决方案可能会有所帮助:http://askubuntu.com/questions/362280/enter-ssh-passphrase-once。 - ceejayoz
我重新生成了一个没有密码的SSH密钥,但它仍然要求我输入密码。 - Anthony
不知怎么地,它正在使用 GPG 密钥或其他什么东西 :\ - Anthony
你能否发布你的全局 ~/.gitconfig 文件和本地仓库的 git 配置文件? - Madara's Ghost
所以我通过Homebrew卸载了GPG,现在当我尝试隐藏一些东西时,我会得到以下错误:error: cannot run gpg: No such file or directory error: could not run gpg. Cannot save the current index state. 为什么我需要使用GPG来进行Git操作?我不能只使用我的SSH密钥吗? - Anthony
2个回答

4

您的git配置文件中commit.gpgsign已设置为true

通过以下方式将其设置为false:

git config --global commit.gpgsign false
# --global flag depends on the scope of the config.

或者,您可以将其设置为没有密码的不同GPG密钥(或者gpg代理可以为您处理的密钥),方法如下:

git config --global user.signingkey KEY_ID

GPG签名与用于身份验证服务器的SSH密钥不同。 SSH确保您已经通过认证并被授权向服务器推送,GPG签名确保您推送的提交确实是由您编写的。
一些有趣的阅读材料:
- 使用签名提交保证代码库完整性 - 一个可怕的Git故事 - 每个Git提交加密签名的优点是什么? - Git SCM - 签署您的工作

0

我已经解决了。

这是使用GPG密钥,但我完全不知道为什么要使用它。

我的GPG密钥有一个密码,我生成了一个新的没有密码的GPG密钥,但我的git配置文件仍在使用旧密钥。

我用新密钥替换了旧密钥,现在它可以工作了。


有很多关于Git GPG签名的在线文档(https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work)。如果您正在使用GPG密钥,则必须自己设置,或者是您购买计算机的人设置的。假设这是您自己设置的,因为它要求输入您的名称 :) - Michael Sondergaard

网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接