You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maka.apache.org by as...@apache.org on 2026/08/20 13:21:10 UTC

(maka) branch docs/3273-crypto-export-inventory updated: docs: drop the speculative follow-up from the determination section

This is an automated email from the ASF dual-hosted git repository.

Astro-Han pushed a commit to branch docs/3273-crypto-export-inventory
in repository https://gitbox.apache.org/repos/asf/maka.git


The following commit(s) were added to refs/heads/docs/3273-crypto-export-inventory by this push:
     new d53b69209 docs: drop the speculative follow-up from the determination section
d53b69209 is described below

commit d53b69209b2dd08464787c7f467f15c25b0eb9fd
Author: AstroHan <le...@outlook.com>
AuthorDate: Thu Aug 20 21:21:05 2026 +0800

    docs: drop the speculative follow-up from the determination section
    
    The determination is settled, so the section recording it should read as
    a conclusion rather than as a list of things to reopen. Remove the
    paragraph asking a future reader to re-raise the bundled-Git question
    with the mentors, and the open item tracking its removal, which is a
    licensing matter rather than an export one.
    
    The inventory itself is unchanged. dugite and its cryptographic payload
    stay in the dependency table, where they are a fact about the tree rather
    than a prompt to act.
    
    Refs #3273
    
    Generated-by: Claude Code (claude-opus-5)
---
 docs/crypto-export-inventory.md | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/docs/crypto-export-inventory.md b/docs/crypto-export-inventory.md
index 444877e9b..49c30670f 100644
--- a/docs/crypto-export-inventory.md
+++ b/docs/crypto-export-inventory.md
@@ -154,12 +154,10 @@ This guidance was given privately. **Exit criteria 4 and 5 of #3273 need it reco
 - Maka's own source does perform AES-256-GCM encryption (§A) and generate an RSA-2048 CA (§B1), both past the 5D002 thresholds. The determination turns on who implemented the cryptography, not on whether Maka invokes it.
 - Every algorithm found is a published standard. §772.1 also reaches proprietary or unpublished *protocols*, and three constructions touch that boundary: `@jackwener/opencli`'s vendor-private API signing with hardcoded key material (§J), Tencent's undocumented QQ Bot bind-task protocol (§A2), and Maka's own Managed Secret envelope construction (§A1, published in this source). The guidance above treats none of these as disqualifying.
 
-**One fact that should not be lost if this is revisited.** `dugite` (§J) currently bundles a complete Git distribution — including OpenSSL native libraries and the .NET cryptography stack — into the desktop convenience binary. That is the pattern behind Impala's OpenSSL manufacturer entry, and it is the one respect in which Maka is not merely a consumer of runtime-supplied cryptography. **It is expected to be removed independently**, because Git is GPLv2 and ASF policy states that "Apach [...]
-
 **Not required, therefore:** the BIS notification email, the exports-matrix `.yaml` entry, and the ASF README crypto notice. No such notice exists today in `README.md`, `README.zh-CN.md`, `NOTICE`, `LICENSE`, or `DISCLAIMER-WIP`, and on this determination none is needed.
 
-**Still open, and unaffected by the above:** whether `dugite` is removed before the first release (release management and licensing, not export control), and whether a closed manufacturer set would ever be needed — if it is, it must be generated per artifact from a frozen install and the actual packaged output, not taken from §J.
+If a closed manufacturer set is ever needed, it must be generated per artifact from a frozen install and the actual packaged output, not taken from §J.
 
 ---
 
-*Produced with AI assistance (Claude, via Claude Code). Two rounds of adversarial review by Claude Fable and OpenAI Codex found, and this revision corrects: an unsupported legal conclusion, an unsupported "all standard cryptography" claim, a missing TLS interception path, two missing shipped dependencies (`dugite`, `@jackwener/opencli`), a missing credential vault, two missing lockfiles, a SHA-1 omission, a stale snapshot, and a mislabelled PowerShell call. That two rounds still missed s [...]
+*Produced with AI assistance (Claude, via Claude Code). Two rounds of adversarial review by Claude Fable and OpenAI Codex found, and this revision corrects: an unsupported legal conclusion, an unsupported "all standard cryptography" claim, a missing TLS interception path, two missing shipped dependencies (`dugite`, `@jackwener/opencli`), a missing credential vault, two missing lockfiles, a SHA-1 omission, a stale snapshot, and a mislabelled PowerShell call. That two rounds still missed s [...]


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org