proomt

Search

Search posts, papers, and topics

All posts

Hacker News front pageferstar6 min readpostmortemintermediate

Inside ZCode: Silently uploading your Git history to the cloud

Read on ferstar.orgHN 336·113 comments

Summary

ZCode (Zhipu’s AI coding desktop) silently archives your entire workspace—including full .git history, LFS cache, and config—encrypts it with a server‑supplied RSA public key, and uploads the ciphertext directly to Aliyun OSS. The upload runs unconditionally for any logged‑in user, cannot be disabled via UI, and the decryption key lives only on the server, giving Zhipu full read access to your co…

  • ZCode captures a full snapshot of the active project (≈90 % .git data) before each LLM prompt and on task completion.
  • The snapshot is encrypted locally with AES‑256‑CTR; the symmetric key is wrapped with an RSA‑OAEP public key fetched from the server, so only the server can decrypt it.
  • Upload bypasses ZCode’s own servers and posts the encrypted tar.gz directly to Aliyun OSS using a signed form, then the OSS calls back to the backend.
  • User‑visible settings ("Optimize Experience", "Repo Snapshot Indexing") do **not** stop the capture or upload; they only affect downstream indexing/training.

Developers using AI‑assisted coding tools often trust that only the code they explicitly submit is sent to the model. Silent, full‑repository snapshots expose proprietary IP, historical secrets, and unreleased features to the vendor, violating confidentiality expectations and potentially breaching…

8/10
devopsllmobservabilitysecurityaiprivacy

Related reading

  1. Reinventing issue tracking: Local-first and Git-native

    A devlog describing how Manganin’s issue tracker stores issues in a dedicated Git repo as plain files, after rejecting earlier approaches that tried to embed issue data in the code tree or Git refs. The author explains the pitfalls of using refs for issue storage, shows the low‑level Git commands needed for that approach, and then outlines the final design: a hidden sister repository where each i…

    Lobstersmanganin.dev6 minHN1lobste.rs27

  3. GitHub Actions leaking secrets when Miri output is cached

    Miri writes all environment variables to the target/ directory, and when that directory is cached in GitHub Actions, secrets can be exposed to PRs. A short‑term patch now limits Miri to only preserve CARGO_* vars (excluding tokens) and OUT_DIR; until the fix lands, disable target caching or scope secrets away from Miri steps and clear existing caches.

    Rust Blogrust-lang.org3 min

  4. App Hardening: One Obfuscation Pipeline Across Every Port

    Codename One adds a cloud‑side hardening step that runs on the merged JAR before it is split into Android, iOS, JavaScript, and desktop binaries. It can rename symbols, encrypt string literals, and insert opaque‑predicate control‑flow guards at configurable levels (off → standard → aggressive → paranoid). The transforms are selective per platform to avoid breaking optimizers, and a mapping is kep…

    CodeName Onecodenameone.com6 min

  6. Agora: Git as Shared Memory for Collective AutoResearch

    Agora treats a Git repository as a shared, append‑only memory for autonomous research agents, recording each claim as an immutable commit in a DAG. In a 12‑day run with 13 language‑model workers it generated 1,703 reproducible contributions and closed 62 % of the gap to a trained GPT‑2‑124M, demonstrating that shared research state can accelerate discovery.

    Hugging Face Daily Papersarxiv.org2 minpaper