 |
ShorekeeperV2EX member #549373, joined on 2021-06-26 09:07:35 +08:00 |
 |
Per Shorekeeper's settings, the topics list is hidden |
Deals info, including closed deals, is not hidden
Shorekeeper's recent replies
Nov 23, 2025 Replied to a topic by wKong753900 › 浏览器 › 有没哪款浏览器像 Chrome 一样方便开发调试，但又内存暂用低的？ |
Nov 19, 2025 Replied to a topic by guoguobaba › 程序员 › github 上犯了个低级错误，怎么补救 |
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository#fully-removing-the-data-from-github
Contact us through the GitHub Support portal, and provide the following information:
The owner and repository name in question (e.g. YOUR-USERNAME/YOUR-REPOSITORY).
The number of affected pull requests, found in the previous step. This is used by Support to verify you understand how much will be affected.
The First Changed Commit(s) reported by git-filter-repo (Look for NOTE: First Changed Commit(s) in its output.)
If NOTE: There were LFS Objects Orphaned by this rewrite appears in the git-filter-repo output (right after the First Changed Commit), then mention you had LFS Objects Orphaned and upload the named file to the ticket as well.
If you have successfully cleaned up all references other than PRs, and no forks have references to the sensitive data, Support will then:
Dereference or delete any affected PRs on GitHub.
Run a garbage collection on the server to expunge the sensitive data from storage.
Remove cached views.
If LFS Objects are involved, delete and/or purge the orphaned LFS objects.
Important
GitHub Support won't remove non-sensitive data, and will only assist in the removal of sensitive data in cases where we determine that the risk can't be mitigated by rotating affected credentials.
Contact us through the GitHub Support portal, and provide the following information:
The owner and repository name in question (e.g. YOUR-USERNAME/YOUR-REPOSITORY).
The number of affected pull requests, found in the previous step. This is used by Support to verify you understand how much will be affected.
The First Changed Commit(s) reported by git-filter-repo (Look for NOTE: First Changed Commit(s) in its output.)
If NOTE: There were LFS Objects Orphaned by this rewrite appears in the git-filter-repo output (right after the First Changed Commit), then mention you had LFS Objects Orphaned and upload the named file to the ticket as well.
If you have successfully cleaned up all references other than PRs, and no forks have references to the sensitive data, Support will then:
Dereference or delete any affected PRs on GitHub.
Run a garbage collection on the server to expunge the sensitive data from storage.
Remove cached views.
If LFS Objects are involved, delete and/or purge the orphaned LFS objects.
Important
GitHub Support won't remove non-sensitive data, and will only assist in the removal of sensitive data in cases where we determine that the risk can't be mitigated by rotating affected credentials.
Oct 9, 2025 Replied to a topic by Eagleyes › Windows › Windows 10 停止支持，大家准备好了吗？ |
最佳实践是 Windows 11
次选 Windows 10 ESU 原位到 2028
再次选重装 Windows 11 IoT Enterprise LTSC 2024
次选 Windows 10 ESU 原位到 2028
再次选重装 Windows 11 IoT Enterprise LTSC 2024
Oct 6, 2025 Replied to a topic by lcj2class › 分享创造 › httpbin-worker: 另一个 httpbin.org 复制品 |
Aug 28, 2025 Replied to a topic by iHaooo › 生活 › 你们能接受自己另一半有抑郁症吗？ |
这里几乎没有医生，期待随机网友能对一个疾病做出准确的、有参考价值的描述是不可能的。
https://www.msdmanuals.cn/professional/psychiatric-disorders/mood-disorders/depressive-disorders
https://www.msdmanuals.cn/professional/psychiatric-disorders/mood-disorders/depressive-disorders
Aug 20, 2025 Replied to a topic by mxdyeah › 宽带症候群 › 深夜 GFW 疑似大规模干扰 443 端口连接 |
本报告记录了我们对这一短暂但广泛的封禁事件的测量与分析。主要发现如下：
1. 无条件的 `RST+ACK` 注入仅发生在 TCP 443 端口，未见于其他常见端口（如 22 、80 、8443 ）。
2. 该无条件注入同时扰乱了出入境中国双方向的连接，但触发机制**不对称**：从中国境内向境外发起的连接，客户端的 `SYN` 包与服务器的 `SYN+ACK` 包各自触发三个 `RST+ACK`包；从境外向中国境内发起的连接，只有服务器返回的 `SYN+ACK` 会触发 `RST+ACK`，客户端发送的 `SYN` 不会触发注入。
3. 负责注入的设备指纹与已知 GFW 设备不匹配，因此**此次事件要么由新的 GFW 设备造成，要么是由已知设备以一种新的或误配置的状态运行造成的**。
aHR0cHM6Ly9nZncucmVwb3J0L2Jsb2cvZ2Z3X3VuY29uZGl0aW9uYWxfcnN0XzIwMjUwODIwL3poLw==
1. 无条件的 `RST+ACK` 注入仅发生在 TCP 443 端口，未见于其他常见端口（如 22 、80 、8443 ）。
2. 该无条件注入同时扰乱了出入境中国双方向的连接，但触发机制**不对称**：从中国境内向境外发起的连接，客户端的 `SYN` 包与服务器的 `SYN+ACK` 包各自触发三个 `RST+ACK`包；从境外向中国境内发起的连接，只有服务器返回的 `SYN+ACK` 会触发 `RST+ACK`，客户端发送的 `SYN` 不会触发注入。
3. 负责注入的设备指纹与已知 GFW 设备不匹配，因此**此次事件要么由新的 GFW 设备造成，要么是由已知设备以一种新的或误配置的状态运行造成的**。
aHR0cHM6Ly9nZncucmVwb3J0L2Jsb2cvZ2Z3X3VuY29uZGl0aW9uYWxfcnN0XzIwMjUwODIwL3poLw==
Select Language