reassign: github verify

Signed-off-by: LetMeFly666 <814114971@qq.com>

Author: LetMeFly666

Solutions/Other-English-LearningNotes-SomeWords.md

@@ -915,6 +915,7 @@ tags: [其他, 知识, 英语, Notes]
 |deform|v. 改变...的外形，损毁...的形状，使成畸形|
 |||
 |denominate|v. 以...(某种货币)为单位，将...命名为，称...为|
+|||
 
 <p class="wordCounts">单词收录总数</p>
 

Solutions/Other-Github-How2Make1VerifiedCommit.md

@@ -1,10 +1,10 @@
 ---
-title: Github - 如何提交一个带有“verified”标识的commit
+title: Github - 如何提交一个带有“verified”标识的commit/如何验证一次commit的签名
 date: 2024-12-28 22:09:55
 tags: [其他, Github]
 ---
 
-# Github - 如何提交一个带有“verified”标识的commit
+# Github - 如何提交一个带有“verified”标识的commit/如何验证一次commit的签名
 
 ## 前言(Why)
 
@@ -22,7 +22,7 @@ tags: [其他, Github]
 > 
 > 验证记录包含一个时间戳，用于标记验证完成的时间。 此持久记录可确保已验证状态的一致性，为存储库内的参与提供稳定的历史记录。 可以通过将鼠标悬停在 GitHub 上的“Verified”徽章上，或者通过[REST API](https://docs.github.com/zh/rest/commits/commits)访问提交（其中包含一个 verified_at 字段）来查看此时间戳。
 
-## How
+## How 2 make 1 verify
 
 因为SSH密钥对还可以当<span title="验证身份用">Authentication Key</span>，所以这里介绍如何使用SSH密钥对对一次commit签名（~~其实是因为我**暂时**不太了解GPG Key~~）。
 
@@ -40,6 +40,52 @@ git config user.signingkey <ssh公钥路径>  # 配置ssh公钥路径
 
 在本地进行一次commit并push到Github，顺利的话，在Commit历史记录中就能看到Verified标了。
 
+## How 2 verify 1 commit
+
+我对一次commit通过ssh密钥进行了签名，那么我如何**验证**这次签名呢？
+
+首先需要创建一个签名验证文件，例如`C:\Users\{username}\.ssh\allowed_signers`。
+
+对于一个ssh公钥(例如`C:\Users\{username}\.ssh\id_rsa.pub`)，格式是这样的：
+
+```
+ssh-rsa(也有可能是ssh-ed25519等) NzaC1lZDI1NTE5AAAAAC3NzaC1lZDI1NTE5AAAAI...很长一串... Tisfy@qq.com
+```
+
+也就是`加密算法 公钥数据 邮箱`。
+
+我们要调换一下顺序为`邮箱 加密算法 公钥数据`并放到`allowed_signers`(或其他)新文件中。
+
+只会在git中配置：
+
+```bash
+git config gpg.ssh.allowedSignersFile c:/Users/{username}/.ssh/allowed_signers
+```
+
+然后就能通过commit的hash验证了：
+
+```bash
+git verify-commit cd2f160fc1e6d91db48b033bd6e5ac08102454ba
+```
+
+## 如何对一个commit重新签名
+
+假设你已经配置好了签名方式：
+
+对最新一次提交重新签名：
+
+```bash
+git commit --amend -S --no-edit
+```
+
+对历史提交重新签名：
+
+```bash
+git filter-branch -f --commit-filter 'git commit-tree -S "$@";' <commit-range>
+# <commit-range>是重新签名的commit范围，例如HEAD~3..HEAD
+# 若是当前分支的所有commit，可将<commit-range>设为HEAD
+```
+
 ## End
 
 但是注意，git版本大于等于2.41才支持上述配置。

reassign.py

@@ -0,0 +1,65 @@
+'''
+Author: LetMeFly
+Date: 2024-12-31 16:51:29
+LastEditors: LetMeFly.xyz
+LastEditTime: 2025-01-01 18:00:25
+'''
+import os
+import subprocess
+
+
+# 判断一个commit是否按配置签名
+def verify_commit(commit_hash: str) -> bool:
+    result = subprocess.run(
+        ['git', 'verify-commit', commit_hash],
+        stdout=subprocess.PIPE,
+        stderr=subprocess.PIPE,
+    )
+    return not result.returncode
+
+
+# 获取一个commit的上一个commit
+def get_parent_commit(commit_hash: str) -> str:
+    result = subprocess.run(
+        ['git', 'log', commit_hash, '--pretty=%H', '-n', '2'],
+        stdout=subprocess.PIPE,
+        stderr=subprocess.PIPE,
+    )
+    return result.stdout.decode('utf-8').strip().split()[-1]
+
+
+# 将从某次commit开始至HEAD的所有commit重新签名
+def re_assign(commit_hash: str) -> None:
+    # cmd = f'git filter-branch -f --commit-filter \'git commit-tree -S "$@";\' {commit_hash}..HEAD'
+    # print(cmd)
+    # os.system(cmd)
+    env = os.environ.copy()
+    env['FILTER_BRANCH_SQUELCH_WARNING'] = "1"
+    result = subprocess.run(
+        ["git", "filter-branch", "-f", "--commit-filter", 'git commit-tree -S "$@";', f"{commit_hash}..HEAD"],
+        env=env,
+    )
+    print(result.returncode)
+    # subprocess.Popen(cmd)
+
+
+def main():
+    os.chdir('OtherSource/gitcode_knowledge')
+    # re_assign('HEAD~2')
+    # return
+    if verify_commit('HEAD'):  # HEAD的签名也能被验证
+        return
+    notVerified = 'HEAD'
+    while True:
+        next = get_parent_commit(notVerified)
+        if next == notVerified:
+            break
+        notVerified = next
+        if verify_commit(next):
+            break
+    print(notVerified)
+    re_assign(notVerified)
+
+
+if __name__ == '__main__':
+    main()

tryGoPy/d-github-reAssign.go

@@ -0,0 +1,141 @@
+/*
+ * @Author: LetMeFly
+ * @Date: 2024-12-31 15:31:56
+ * @LastEditors: LetMeFly.xyz
+ * @LastEditTime: 2025-01-01 17:58:11
+ */
+很棒，我已经完成了签名的验证。现在我想要将一个commit重新签名，其他信息不变。
+可以做到吗？
+
+
+
+git本地有两个用户，如何分别为其配置ssh公钥密钥
+
+
+
+python写一个脚本：
+
+从HEAD开始往前遍历，直到遇到可验证的签名为止。
+将HEAD开始的所有连续的不可验证的签名重新签名。
+
+
+
+
+git log --pretty=online可不可以指定显示数量
+
+
+
+
+git log --pretty=online有没有办法从某次commit开始显示
+
+
+
+只输出commit hash
+
+
+
+git某次commit的下一次commit
+
+
+
+不，比如我HEAD~1是HEAD的上一次commit
+我如何表示一个commitHash的下一次commit
+
+
+
+为何我执行`git filter-branch -f --commit-filter 'git commit-tree -S "$@";' HEAD~2..HEAD`命令的时候
+在终端中直接执行就能正常运行，而在python中调用os.system执行就会报错：
+
+```
+Proceeding with filter-branch...
+
+fatal: ambiguous argument 'commit-tree': unknown revision or path not in the working tree.
+Use '--' to separate paths from revisions, like this:
+'git <command> [<revision>...] -- [<file>...]'
+```
+
+
+
+
+执行如下代码时报错：
+
+```
+result = subprocess.run(
+        ["git", "filter-branch", "-f", "--commit-filter", """'git commit-tree -S "$@";'""", f"{commit_hash}..HEAD"],
+        check=True,
+        text=True,
+        # stdout=subprocess.PIPE,
+        # stderr=subprocess.PIPE,
+    )
+    print(result.stdout)
+```
+
+```
+Rewrite bde2a1b75e8881d2911ec557aa0ae97414b75a47 (1/2) (0 seconds passed, remaining 0 predicted)    git commit-tree: line 52: git commit-tree -S "$@";: command not found
+could not write rewritten commit
+Traceback (most recent call last):
+  File "F:\OtherApps\Program\Git\Store\Store20_LeetCode\reassign.py", line 65, in <module>
+    main()
+  File "F:\OtherApps\Program\Git\Store\Store20_LeetCode\reassign.py", line 49, in main
+    re_assign('HEAD~2')
+  File "F:\OtherApps\Program\Git\Store\Store20_LeetCode\reassign.py", line 36, in re_assign
+    result = subprocess.run(
+  File "F:\OtherApps\Program\Python\Python\lib\subprocess.py", line 528, in run
+    raise CalledProcessError(retcode, process.args,
+subprocess.CalledProcessError: Command '['git', 'filter-branch', '-f', '--commit-filter', '\'git commit-tree -S "$@";\'', 'HEAD~2..HEAD']' returned non-zero exit status 1.
+```
+
+
+
+
+
+很棒，这个问题解决了。
+但是我发现了一个新的问题，在进行上述操作时，会显示如下warning并卡住几秒。
+```
+Store\Store20_LeetCode\OtherSource\gitcode_knowledge
+WARNING: git-filter-branch has a glut of gotchas generating mangled history
+         rewrites.  Hit Ctrl-C before proceeding to abort, then use an
+         alternative filtering tool such as 'git filter-repo'
+         (https://github.com/newren/git-filter-repo/) instead.  See the
+         filter-branch manual page for more details; to squelch this warning,
+         set FILTER_BRANCH_SQUELCH_WARNING=1.
+Proceeding with filter-branch...
+```
+我有没有办法让他不显示这个提示并且不卡住？
+
+
+
+
+```
+    env = os.environ.copy()
+    env['FILTER_BRANCH_SQUELCH_WARNING'] = 1
+    result = subprocess.run(
+        ["git", "filter-branch", "-f", "--commit-filter", 'git commit-tree -S "$@";', f"{commit_hash}..HEAD"],
+        check=True,
+        text=True,
+        # stdout=subprocess.PIPE,
+        # stderr=subprocess.PIPE,
+        env=env,
+    )
+```
+报错：
+```
+  File "F:\OtherApps\Program\Git\Store\Store20_LeetCode\reassign.py", line 68, in <module>
+    main()
+  File "F:\OtherApps\Program\Git\Store\Store20_LeetCode\reassign.py", line 52, in main
+    re_assign('HEAD~2')
+  File "F:\OtherApps\Program\Git\Store\Store20_LeetCode\reassign.py", line 38, in re_assign
+    result = subprocess.run(
+  File "F:\OtherApps\Program\Python\Python\lib\subprocess.py", line 505, in run
+    with Popen(*popenargs, **kwargs) as process:
+  File "F:\OtherApps\Program\Python\Python\lib\subprocess.py", line 951, in __init__
+    self._execute_child(args, executable, preexec_fn, close_fds,
+  File "F:\OtherApps\Program\Python\Python\lib\subprocess.py", line 1420, in _execute_child
+    hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
+TypeError: environment can only contain strings
+```
+
+
+
+subprocess.CalledProcessError: Command '['git', 'filter-branch', '-f', '--commit-filter', 'git commit-tree -S "$@";', 'HEAD..HEAD']' returned non-zero exit status 2.
+Found nothing to rewrite