与「encrypt」相关的搜索结果

ClawChat, after redefining on-chain communication: * BTC-native foundation * Fully on-chain messaging * End-to-end encrypted by design * Agent-ready social layer Now it’s not just communication — it’s coordination at scale.

Apple and Google pushed to amend an online safety bill working its way through Canada's parliament to add judicial oversight to what the firms described as a potential for secret orders to break the ‌encryption of their software and devices

Have you ever closed a browser and felt your digital soul vanish? @TheARCTERMINAL fixes this by allowing ANIMA to save your entire work graph research, drafts, and context while connecting to any MCP server with client-side encryption, enabling you to bring your own infrastructure without exposing your keys. As a creator deeply embedded in the Web3 agentic economy, I see this sovereign approach to AI as a massive leap forward. We are not just talking about a fancy smart notepad; we are talking about secure, continuous AI execution. When I recently set up autonomous API calls for StrikeRobot on Base Azul, the ultimate headache was safely linking local tools to on-chain actions without risking personal credentials. ARC completely resolves this friction. It transforms your workspace into a living, encrypted vault. You own the context, and your AI handles the heavy lifting. True agentic freedom means bringing your own tools while remaining entirely trustless. Why are we still giving our workflow keys to centralized servers?

Phew, Grok Build is really thorough, pretty incredible. Relay feature for PasteLocal is done, pushing to Github now. And if you want to know what this adds, here's a bit more about it, this is a feature I really wanted in there, and honestly didn't really expect to have done this week. • Per-peer E2E encryption: clipboard data is encrypted individually for each paired device using X25519 + HKDF + AES-GCM (no plaintext ever leaves the client) • Durable persistence: relay state is now stored in an atomic state.json with proper TTL handling and compaction. Pending clips survive relay-server restarts • Safe compaction: fixed unsafe map mutation during expiration/compaction that could cause data loss or undefined behavior • Full bidirectional CLI: new commands: pastelocal relay send, inbox, fetch, and status, plus pastelocal-remote --relay --peer --send • Auto-sync: when watch.enabled + are on, meaningful clipboard changes are automatically pushed to paired devices • Improved DX: doctor checks are now only shown when relay is enabled, and the TUI shows basic relay status • Multiple review cycles: went through full implement → review → fix → re-review (effort 4), plus a final targeted regression fix round Try it out and please send any and all feedback!

🚨 node-ipc is compromised again. Three new malicious versions just dropped: 9.1.6, 9.2.3, and 12.0.1. Socket’s AI scanner flagged them as malware within three minutes of publication. The attack vector: a dormant maintainer account (atiertant) was likely taken over via an expired email domain. The attacker registered the lapsed domain, triggered an npm password reset, and gained publish rights to a package with millions of historical downloads. The payload is a credential stealer embedded in the CommonJS entrypoint (node-ipc.cjs). It activates on require(“node-ipc”), not through a postinstall script. Here’s what it does: •Fingerprints the host (OS, arch, hostname, uname) •Harvests 113-127 credential file patterns depending on platform (AWS, GCP, Azure, SSH keys, Kubernetes configs, npm tokens, .env files, shell histories, macOS Keychain databases, and more) •Dumps the entire process.env, capturing every CI secret and cloud credential in memory •Builds a gzip archive in a temp directory •Exfiltrates everything over DNS TXT queries to bt[.]node[.]js, using a bootstrap resolver at sh[.]azurestaticprovider[.]net:443 (a deliberate lookalike of Microsoft’s Azure Static Web Apps domain) The DNS exfiltration is chunked. A 500 KB archive generates roughly 29,400 TXT queries. The body is XOR-encrypted with a SHA-256 keystream, base64-encoded, alphabet-substituted, and split into 31-character chunks before hex-encoding into DNS labels. Header, data, and footer queries use xh, xd, and xf prefixes respectively. The malware forks a detached child process (env var __ntw=1) so credential theft runs silently in the background. It also exposes a __ntRun export, meaning any downstream code that calls require(“node-ipc”).__ntRun() can trigger a second collection/exfiltration cycle. ESM-only consumers using the import path are not affected by the reviewed package metadata. CommonJS consumers are. This is the same package involved in the 2022 protestware incident. It has a history. If you use node-ipc: •Do not install 9.1.6, 9.2.3, or 12.0.1 •Audit your lockfiles for these versions •If you loaded the CommonJS entrypoint, treat all environment variables, SSH keys, cloud credentials, npm tokens, and local secrets as compromised. Rotate immediately. •Hunt for DNS TXT queries to bt[.]node[.]js and sh[.]azurestaticprovider[.]net in your network logs •Check for temp files matching /nt-/.tar.gz Credit to Ian Ahl (@TekDefense) for first publicly identifying the expired-domain account takeover vector. Developing story. Full technical breakdown and IOCs on the Socket blog:

Congratulations to our 10 winners! @encrypt_wizard @alhadji_ACE @EveMipata @nhagmail30 @jaikb15 @LinhTK2024 @NguyentriDlk01 @Nafru699 @Davis_Brains @soundofdragon You'll each receive 100 USDC. Rewards will be sent by end of the week. Thanks to all who participated.

"Wait... these can't be legal." 3,000+ mile range and no monthly fees. No license needed. AES-256 encrypted. Anonymous SIM — no name, no contracts, no logs. Your carrier tracks everything. This tracks nothing. Legal. Just built differently. 60% OFF + free shipping today

运营中转站这段时间是真没赚到钱，只能说勉强cover了我自己用ai的消费。 所以目前打算把开中转站的一切全部开源，包含如何建站+营销，门槛最低，让这个行业更卷一点。 首先整个系统由3个部分组成： • 第CN2 回国专线服务器：放在海外但回国速度极快的 VPS，作为运行核心。 • sub2api：核心程序，负责把网页账号转成 API 接口。 • Cloudflare：把流量再绕一道，提升国内访问速度，同时隐藏真实服务器 IP。 你需要准备： • 一台 CN2 GIA 或 CN2 GT 线路的海外 VPS（推荐配置：2 核 CPU、2GB 内存、20GB 硬盘以上）。 普通海外 VPS 在国内晚高峰几乎不可用，而 CN2 GIA 通过专线绕开了拥堵的公网节点，国内访问延迟一般在 150ms 以内。如果你买了不是 CN2 的服务器，国内用户体验会非常糟糕。 • 一个域名（建议在 Cloudflare 或 Namecheap 上购买，便宜的 .top 或 .xyz 也行，几块钱一年）。 • 一个 Cloudflare 账号（免费）。 • 号池：初期可以用 claude code pro 账户+ 注册大量gpt账户，货比三家去找到别的号商卡商，等后期你就可以搞claude code max kiro 反代 aws bedrock（去跟sales聊，基本能搞到7.2折），但是初期只需要保障claude code pro账号稳定即可，因为你需要养号，后期转max。 完整请求路径如下： 国内用户的客户端 → 解析到 Cloudflare 的 IP → Cloudflare 边缘节点 → CN2 专线回源到你的服务器 → 宝塔面板的 Nginx 反向代理 → sub2api 程序 → 你的号池 → ChatGPT 或 Claude 网页 → 数据原路返回。 购买并初始化CN2服务商 CN2 GIA 线路的常见服务商有 BandwagonHost（搬瓦工）、RackNerd、CloudCone、Lisahost。新手推荐搬瓦工的 CN2 GIA-E 套餐，稳定但价格略贵。预算紧的可以看 Lisahost 的香港 CN2 套餐。 如果你懂命令行搭建Nginx，手动部署SSL证书，那你就自己搞，如果你不懂可以使用中国程序员流行的宝塔面板，一键搭建Nginx、一键部署SSL证书、可视化配置反向代理，全程鼠标点击操作，新手也能轻松上手。 安装完Linux + Nginx + MySQL + PHP，就可以开始设置防火墙，够买域名，添加DNS解析。 最后去命令行输入ping.api.你购买的域名，返回服务器ip就行了。 搭建sub2api: sub2api 是一个开源项目，可以把 ChatGPT 网页版、Claude 网页版的 cookie 或者 session 转换成 OpenAI 兼容的 API 接口。 打开sub2api的官方教程，安装流程安装docker，拉取并启动sub2api的容器。 你需要把号池数据放到 /www/sub2api/data 目录下，sub2api 容器会读取这个目录。具体格式参考 sub2api 项目文档。 设置Nginx反向代理 添加完之后目标url是127.0.0.1:8080因为 sub2api 容器监听的就是这个地址。Nginx 收到外部请求后，转给本机的 8080 端口，sub2api 处理完返回给 Nginx，Nginx 再发回给用户。 后面你去问claude code 如何优化Nginx的配置，AI API 调用是流式响应（SSE），需要长连接 + 不缓存才能正常工作。默认 Nginx 配置在这种场景下会出问题，按照claude的提示优化，proxy_buffering 必须关闭，如果不关闭这个，AI 的回答会"卡一阵 → 一次性吐出"，而不是逐字流式输出。客户端会感觉非常慢甚至超时。 申请HTTPS证书： OpenAI 兼容客户端基本只信任 HTTPS。HTTP 明文会暴露 API Key 给中间网络。 申请好Let's Encrypt证书之后，回到 SSL 主界面，把"强制 HTTPS"开关打开。 优化Cloudflare配置 测试HTTPS-开启cloudflare代理-Cloudflare SSL 模式必须设为 Full (strict) AI API 是动态接口，Cloudflare 的某些"优化"会破坏流式响应。 Cloudflare → 你的域名 → 速度 → 优化。 全部关掉以下选项： • Auto Minify（自动压缩 HTML/CSS/JS）：关闭。 • Rocket Loader：关闭。 • Mirage：关闭。 • Polish：关闭。 设置缓存规则： Cloudflare → 缓存 → 配置。 Caching Level 选 Bypass，或者保持 Standard 但是后面用页面规则覆盖。 更彻底的做法：Cloudflare → 规则 → 页面规则 → 创建页面规则。 URL 模式： 设置：Cache Level = Bypass 设置防火墙规 Cloudflare → 安全性 → WAF → 自定义规则 → 创建规则。 规则一：限制单个 IP 频率 字段：IP source address，操作：Rate limiting，每 10 秒最多 30 次请求，超出后挑战或屏蔽 1 小时。 规则二：屏蔽明显恶意爬虫 字段：User Agent，运算符：包含，值：python-requests 启用 Cloudflare Argo Smart Routing，每月 5 美元，能在 Cloudflare 内部用最优路径路由你的流量。对国内用户访问海外服务器有 30% 到 50% 的速度提升。预算够推荐开。 测试上线 用 curl 测试 API，或者打开 CherryStudio 或 ChatBox，填写你的api地址和key做测试 使用Prometheus/Grafana，或者直接用宝塔面板做监控，可以看到 CPU、内存、流量实时数据。如果 sub2api 容器经常吃满 CPU，考虑升级服务器配置。