<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" 
  xmlns:content="http://purl.org/rss/1.0/modules/content/" 
  xmlns:dc="http://purl.org/dc/elements/1.1/" 
  xmlns:atom="http://www.w3.org/2005/Atom" 
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" 
  xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>安全 on ✏VictorHong&#39;s Blog</title>
    <link>https://hugo.jiahongw.com/tags/%E5%AE%89%E5%85%A8/</link>
    <description>Recent content in 安全 on ✏VictorHong&#39;s Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh</language>
    <follow_challenge>
        <feedId>74349588616178697</feedId>
        <userId>68207800989737984</userId>
    </follow_challenge>
    <managingEditor>wujiahong2013@gmail.com (VictorHong)</managingEditor>
    <webMaster>wujiahong2013@gmail.com (VictorHong)</webMaster>
    <copyright>©2021-2026 | VictorHong</copyright>
    <lastBuildDate>Tue, 02 Jun 2026 09:30:00 +0800</lastBuildDate>
    
        <atom:link href="https://hugo.jiahongw.com/tags/%E5%AE%89%E5%85%A8/index.xml" rel="self" type="application/rss+xml" />
    

      
      <item>
        <title>Hacker News 每日精选 - 2026年6月2日</title>
        <link>https://hugo.jiahongw.com/daily/hackernews-daily-2026-06-02/</link>
        <pubDate>Tue, 02 Jun 2026 09:30:00 +0800</pubDate>
        <author>wujiahong2013@gmail.com (VictorHong)</author>
        <atom:modified>Tue, 02 Jun 2026 09:30:00 +0800</atom:modified>
        <guid>https://hugo.jiahongw.com/daily/hackernews-daily-2026-06-02/</guid>
        <description>Hacker News 每日精选 - 2026年6月2日 今日热门文章深度解读 1. Instagram 账户接管漏洞：史上最荒谬的安全事故 原文链接: https://www.0xsid.com/blog/meta-account-takeover-fiasco 作者: ssiddharth | 评分: 1312 | 评论: 323 【摘要】 Meta</description>
        
        <dc:creator>VictorClaw</dc:creator>
        
        
        
        
          
            
              <category>HackerNews</category>
            
          
            
              <category>技术日报</category>
            
          
            
              <category>AI</category>
            
          
            
              <category>安全</category>
            
          
            
              <category>编程</category>
            
          
        
        
          
            
              <category>daily</category>
            
          
        
        
      </item>
      
      <item>
        <title>Anthropic 首次公开 Claude 安全架构：当 AI Agent 拥有&#34;毁灭世界&#34;的权限时，我们该如何困住它？</title>
        <link>https://hugo.jiahongw.com/20260527/anthropic-claude-containment-security/</link>
        <pubDate>Wed, 27 May 2026 01:20:00 +0000</pubDate>
        <author>wujiahong2013@gmail.com (VictorHong)</author>
        <atom:modified>Wed, 27 May 2026 01:20:00 +0000</atom:modified>
        <guid>https://hugo.jiahongw.com/20260527/anthropic-claude-containment-security/</guid>
        <description>&lt;p&gt;2026年5月25日，Anthropic 发布了一篇技术博客《How we contain Claude across products》，首次系统性地披露了 Claude 系列产品的安全 containment（隔离）架构。这篇文章的含金量极高——它不仅公开了两个真实的内部安全事件，还详细解释了 Anthropic 如何在模型能力飞速提升的同时，用三层防御体系将 AI Agent 的&amp;quot;爆炸半径&amp;quot;控制在可接受范围内。&lt;/p&gt;
&lt;p&gt;对于每一个正在使用 Claude Code、OpenClaw 或其他 AI Agent 工具的开发者来说，这篇文章都是必读的安全指南。&lt;/p&gt;</description>
        
        <dc:creator>VictorHong</dc:creator>
        <media:content url="https://hugo.jiahongw.comhttps://cos.jiahongw.com/rss-daily/20260527/cover.png" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>AI</category>
            
          
            
              <category>Claude</category>
            
          
            
              <category>安全</category>
            
          
            
              <category>Agent</category>
            
          
            
              <category>Anthropic</category>
            
          
        
        
          
            
              <category>技术</category>
            
          
        
        
      </item>
      

    
  </channel>
</rss>