创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

Windows 11遥测会记录编程智能体和开发工具使用情况

AI 总结

对MissionControlAggregator.dll的逆向分析发现,Windows 11会记录位图标记,显示系统观察到了哪些编程智能体和开发工具,包括Codex、Claude、GitHub Copilot、Cursor、Python和.NET。研究者在美国地区配置的Windows 11 Home ARM64安装环境中验证,启用可选诊断数据时,相关报告会进入DiagTrack的上传队列;该选项在此测试环境中默认开启。报告不包含提示词文本或源代码,其时间戳表示收集窗口,而非各工具的使用时长。其他地区、版本或配置下的行为尚未确定。

深度见解

这项调查记录了一条实际可用的遥测路径,能够将用户运行过哪些AI编程助手和开发工具的信息加入上传微软的队列。即使报告不含提示词文本或源代码,也不记录各工具的使用时长,这类信息收集仍涉及隐私问题。

Reverse engineering Windows 11's MissionControlAggregator reveals coding-agent and developer-tool usage bits in a diagnostic ETW report.

I recently asked AI to help me look through the latest Windows binaries for undocumented features and functionality. Among the leads it turned up, one list immediately caught my attention: coding agents such as codex.exe, claude.exe, copilot.exe, and cursor.exe, alongside familiar developer tools such as python.exe, dotnet.exe, gcc.exe, and code.exe.

Why would a Windows system DLL need a list of coding agents and developer tools?

The names were in MissionControlAggregator.dll. I asked the agent to follow the references and dig into what the DLL actually does. That led from a handful of string comparisons to a running Windows component that records which coding agents and developer tools have been used, saves that information locally, and reports it to Windows Diagnostics. And unless you have opted out of the “optional” diagnostic data (which is enabled by default), the data is uploaded to Microsoft.

I shared the initial finding on X. This post includes more details about the investigation behind it.

Following the names

Opening the DLL in Binary Ninja made the first lead easy to see. These were explicit executable names embedded in a Windows component:

#Microsoft#Windows 11#Windows MissionControlAggregator#Codex#Claude#GitHub Copilot#Cursor#Python#Visual Studio Code#.NET

原文约 7 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。