Skip to content

armgit / andee

Public Imported from GitHub
0

Andee lives on your phone or Mac and uses any app like you do—no integrations, no root, any model; memory and passwords never leave your device | Andee 住进你的手机或 Mac,像你一样操作任何 App——无需集成、无需 Root、支持任意模型,记忆和密码绝不离开设备。

docs(readme): keep the signing key out of git

booboosuideda68299e10
diff --git a/README.md b/README.md
index b2d2d28..1740f82 100644
--- a/README.md
+++ b/README.md
@@ -365,6 +365,16 @@ The debug build is signed with the standard Android debug certificate and instal
the APK is **per-ABI** (`splits` in `app/build.gradle`), so pick the one that matches the device —
`arm64-v8a` for anything bought in the last several years.
+**Keep your signing key out of git — including this repository's forks.** Android lets an APK replace
+an installed one only when the signatures match, and that is the only thing standing between your users
+and a fake "update". Whoever holds the key can ship an APK that installs over theirs and inherits
+everything: the accessibility service stays enabled, the `WRITE_SECURE_SETTINGS` grant stays, and the
+vault, notebook and conversation are its to read. A leaked key cannot be taken back without every user
+uninstalling. Keep it in your build machine's secret storage and point `signingConfig` at it through
+environment variables. A side effect worth knowing: the debug keystore is generated per machine, so an
+APK built on one machine cannot be installed over one built on another (`INSTALL_FAILED_UPDATE_INCOMPATIBLE`)
+— uninstall first, or give local builds a different `applicationId`; do not share the key to get around it.
+
**If the build does not work, the answer is almost always the JDK.** Full from-scratch setup — the
JDK traps, the Android SDK two different ways (including a command-line-only path for CI), and a table
of every error you are likely to hit — is in **[Provisioning](#provisioning)** below. Permissions are
diff --git a/README.zh-CN.md b/README.zh-CN.md
index d59531e..7d741cc 100644
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -312,6 +312,14 @@ Google),再填该服务商的密钥。这是两个独立的服务,条款
可以直接装。两种包都是**按 ABI 拆开的**(见 `app/build.gradle` 里的 `splits`),拿和设备对得上
的那个——近几年买的机器基本都是 `arm64-v8a`。
+**签名文件不要进 git,fork 也一样。** Android 只允许签名相同的 APK 覆盖安装,这是用户和一个
+冒牌「更新」之间唯一的一道门。谁拿到签名,谁就能做出一个能直接装在用户机器上的 APK,并且继承
+一切:无障碍服务仍然开着,`WRITE_SECURE_SETTINGS` 授权还在,密码本、笔记本和对话记录都归它读。
+签名一旦泄露就收不回来,除非所有用户卸载重装。签名放在打包机的私密存储里,`signingConfig` 通过
+环境变量指向它。顺带一提:debug 签名是每台机器各自生成的,所以一台机器打的包不能覆盖另一台机器
+装的包(`INSTALL_FAILED_UPDATE_INCOMPATIBLE`)——先卸载,或者给本地构建换一个 `applicationId`,
+别为了绕过它去共享签名。
+
#### 遇到问题
装机流程、以及从零配 SDK 的完整说明(含纯命令行 / CI 路径)在本文下面的