慣性聚合 高效追讀感興趣之博客、新聞、科技資訊
閱原文 以慣性聚合開啟

推薦訂閱源

Google DeepMind News
Google DeepMind News
人人都是产品经理
人人都是产品经理
M
MIT News - Artificial intelligence
博客园 - 叶小钗
MyScale Blog
MyScale Blog
V
Visual Studio Blog
月光博客
月光博客
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
量子位
I
InfoQ
有赞技术团队
有赞技术团队
阮一峰的网络日志
阮一峰的网络日志
Jina AI
Jina AI
V
V2EX
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
Blog — PlanetScale
Blog — PlanetScale
Last Week in AI
Last Week in AI
雷峰网
雷峰网
Stack Overflow Blog
Stack Overflow Blog
博客园 - Franky

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python)
FHE提示隐私:您的演示仍存在元数据泄露
AI x Crypto · 2026-05-25 · via DEV Community

AI与密码系统揭示:此文乃借助AI为编辑之助所撰。其意、其事、其码、其源、其结,皆经人手审之。

AI与密码系统揭示:此文为技术之释,非投资之谋。AI与密码系统不荐购、不荐售、不荐持任何密码资产。

FHE提示隐私

一私推断之示,诚言FHE,犹可泄用户之流程。提示正文或于离客户端前已加密,然服务器犹可察用户之调用。/risk-score 每日清晨,以四千字节之密文,并附医模型之标识。FHE提示隐私之法,隐选明文于选算之中;然FHE提示隐私,不自动隐请求之形、路由、时序、日志、模型之择,亦不隐后释为输出之文。

开发者之误,乃将"供者不能读示"视作"会话为私"。此言略去隐私存于周遭系统之部分。欲审FHE示密之理,当自加密之域始,渐行向外,直至每一观察者、日志及揭示之步皆有名目。

FHE prompt privacy boundary

加密之域

FHE示密之始,唯有一狭胜:计算可于加密之数据上施行。FHE.org之开发者之道谓全同态加密者,乃于加密之数据上运行计算,而无需先解密之。此诚实能,非虚饰也。然文所述之界,较之流行语为狭:FHE提示隐私,则护加密计算所入之域,依所陈之钥、参数及电路焉。

是也。此界域之别,盖因AI之示语非独物也。一请或含系统之令,所取之文,用户之辞,工具之元,租户之讯,模型之择,安危之旗,计费之签。若惟user_text若已加密,则其主张为"此计算内用户文辞受护",非"AI请求私密"。FHE提示隐私可信,当加密字段列被书录。

系统边界

FHE提示隐私存于系统,非存于字句。Zama之fhEVM概览之框架,以FHE技术赋能区块链应用,融加密运算于执行架构;Zama之中继与预言机文档,则分述用户交互之中继、网关往来、解密支持及预言机行止。此等文档非AI提示之产品手册,然实为广论之明证:密码学,仅隐私路径中一隅耳。

实用之审问,非曰「系统用否FHE?」实用之审问,乃曰「何�件可见何事?」中继者或可见客端交互之迹,网关或可见请求数之流,模型服务或可见端点之择,日志之层或存租户与计费之境,而显路或化选定之出为明文。FHE提示隐私护X,非护Y:能护密算内明文之质,非护密算周遭诸事之实。

隐私边界表

表面 FHE提示隐藏隐私? 检视何物
电路内之原始提示字段 是,依所陈之钥与威胁模型 客户端加密点,钥之归属,电路输入
系统提示与检索之语境 唯若彼域亦得加密 地脉图与序列化格式
请询时序与频次 勿也 分批,迟滞,速率限制之日志
端点、模型或电路之择 常无之 路名,型号标识,公参数
输入长度或密文大小 常隐约可见 填充、分桶、压缩之态
账户、租户及账单之签 无访问日志、发票、分析之迹
解密或释出后之输出 否,既释则不再 揭示政策与遮蔽之则
提示注入之态 指令层序,检索之策,器用之权

元数据之驭

FHE提示隐私,宜先以枯燥元数据验之,方得庆加密推论之成。FHE.org 亦警示元数据泄露围绕加密之计算,及也伯克利技术报告论基于同态加密之私密推理 明确视IP地址、请求频次、输入长度为非某设计之隐私目标。此乃多数演示所略过之处。提示或晦涩难辨,而流程犹可分类。

此乃吾所操之玩具,未尝启FHE提示隐私之设,而先施之。此具不译任何密文。此具询之,静观者能否于请求数形中,聚诸务于量桶、端点、时序、模型标章之别。

FHE metadata leak harness

from collections import Counter

requests = [
    {"task": "medical_triage", "prompt_bytes": 312, "ciphertext_bytes": 4096, "endpoint": "/classify", "hour": 9},
    {"task": "legal_summary", "prompt_bytes": 11840, "ciphertext_bytes": 12288, "endpoint": "/summarize", "hour": 18},
    {"task": "wallet_warning", "prompt_bytes": 720, "ciphertext_bytes": 4096, "endpoint": "/risk-score", "hour": 9},
    {"task": "batch_scoring", "prompt_bytes": 64000, "ciphertext_bytes": 65536, "endpoint": "/batch", "hour": 2},
]

def bucket(row):
    size = row["ciphertext_bytes"]
    if size <= 4096:
        size_bucket = "small"
    elif size <= 16384:
        size_bucket = "medium"
    else:
        size_bucket = "large"
    return (size_bucket, row["endpoint"], row["hour"])

fingerprints = Counter(bucket(row) for row in requests)
for row in requests:
    print(row["task"], bucket(row), "cluster_count=", fingerprints[bucket(row)])

全屏模式 退出全屏模式

其出非为攻破密术,乃产评之微嗅。若/risk-score 专用于钱袋警示,观者无需提示以推知其务。若法理摘要恒于营业之后以中密文至,则长短与时为标。FHE提示隐私,隐其文,非隐系统现流程之迹。

填充预算

FHE 提示隐私,常需余量与分批之计,非独加密之库也。凡请求数据,皆补齐至同量,可减漏长之弊,然补余增费滞。请求数之批,可淆频次之迹,然批易应答之态。端点更名,可隐任务之标,然路由犹存。FHE 提示隐私,一旦众知元数据为隐私余量之属,遂成工程权衡之务。

要害之修正,在避伪绝对。设计不必隐匿所有元数据方为有用。医疗分诊之器、钱包风险分类之器、私人检索之系,可有不同之隐私预算。文中所言,当明何元数据得存可见,及其余残露为何于所使用者可容.

显露之策

FHE 提示隐私亦需揭示之策,盖因结果终须待有人可依而行之方显其用。Zama 之传讯者/神谕者之记述,足为警示,盖加密之流程中,犹可包含助人取解密之值或为用户再加密之务。于人工智能之推论中,模型之评分、标签、摘要或答案返于用户或契约时,亦现此基本之弊。私密之计算或为实然,然释出之步骤犹泄其机要。

分类之例,简明如是。若隐语询机密之状,而发语显之。high_risk_condition=true,虽计算之时提示体尚加密,然输出已泄机密之事。FHE提示隐私必先界定输出之类别、删节、聚合及审计日志,方得称其隐私。揭示之策非文书也;揭示之策,乃多许私推之诺复显其形.

模型之身

FHE 提示隐私应命名模型或电路身份,盖因"私密推理"非单一之计算。Zama 具体机器学习 载记一工器链,用以保私隐之机器学习,以 FHE 为之。然其他 FHE 之系统,或用异法,或异编译器,或异参数之择,或异所支之运算。一开发者检视 FHE Prompt Privacy,当问何模型之器、何预处理之径、何量化之阶、何电路、何公参数,皆在所保之计算中。

是故,此身份之问非为考据。若系统于小分类器上证明或执行加密推论,则不应以同界度之于一任意大型语言模型之工作流,其中包含检索、工具与长文境。FHE提示隐私之理,当于所护之计算详述其名。所护之断言,当若“此加密分类器于此电路下评估此诸域”,非若“吾辈之AI乃私密”。

感应词注入

FHE 提示隐私,不能防备提示注入。加密可令操作者于运算时不得窥探部分明文,然加密非能教模型何为可信之指令。若模型与工具政策容许,则加密检索包内之敌对文书仍可令模型漠视先前指令。FHE 提示隐私,护部分内容之机密,非护指令之完整。

此界尤关人工智能与加密货币之系统。助记钱包、释明交易或审阅契约之器,虽用私钥输入,犹需严控权限、模拟交易、白名单及拒行之规。若模型可被诱使调用危器,则加密提示亦无济于事。FHE提示隐私,当与提示注入之防并列,非可替代之。

记录契约

FHE 提示隐私应具记录契约。记录乃隐私之所在,悄然消亡。系统可加密提示内容,犹存端点名、账户标签、模型ID、密文长度、时间戳、错误信息、重试次数及输出片段。若分析能重构用户流程,则隐私之主张弱于密码学之承诺。

良契简明,其言无歧义。述何项永禁不录,何项分桶存储,何项迅朽而消,何项需以计费,何项可显于吏者。契亦当言明,调试可暂增其录。FHE提示隐私,非生产可用,必待其录入威胁模型始可。

{
  "encrypted_fields": ["user_prompt", "retrieved_private_notes"],
  "visible_fields": ["endpoint_family", "tenant_plan", "ciphertext_size_bucket"],
  "never_log": ["raw_prompt", "raw_output", "exact_ciphertext_length"],
  "retention": {
    "routing_metadata": "7 days",
    "billing_events": "30 days",
    "debug_payloads": "disabled by default"
  },
  "reveal_policy": "return only the minimum answer class needed by the caller"
}

全屏模式 退出全屏模式

审卡

FHE提示隐私仅当边界可检视时方可发布。开发者应能指向加密字段、模型或电路身份、元数据预算、揭示政策、提示注入控制及日志合同。无此诸物,"FHE提示隐私"不过为未审系统所裹之诱人辞藻。

信 demo 之先,当用此评鉴之卡:

善答 恶答
所谓加密者,究竟为何? 命字之域,序列之式 "提启"
孰可见乎? 时序、路径、巨细、模式、日志、账目,皆列明之 "无足轻重"
長度何以處之? 填充或尺寸桶之選,有成本之權衡 無答
孰可請解密或輸出釋放? 角色與政策之名 「系統自處之」
誘導提示何以處之? 分離指令與工具政策 「FHE保護提示」
何者被记录? 保留与删改之规 默认应用日志

FHE提示隐私,当诉求狭时,乃强器也。可减露原提示于算力司之需,此诚可贵。所持之界,直截而明:FHE提示隐私,惟于选定之计算时,可隐选定之内容,非蔽其周遭之全AI流程也。