<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>#AIEncryption on Home</title>
    <link>https://yakinin.com/en/tags/%23aiencryption/</link>
    <description>Recent content in #AIEncryption on Home</description>
    <generator>Hugo -- 0.148.2</generator>
    <language>en</language>
    <lastBuildDate>Tue, 19 Aug 2025 21:52:52 +0000</lastBuildDate>
    <atom:link href="https://yakinin.com/en/tags/%23aiencryption/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OpenAI&#39;s Priorities: Fix the Leaks Before Encrypting the AI</title>
      <link>https://yakinin.com/en/posts/20250819-openai-security-priorities/</link>
      <pubDate>Tue, 19 Aug 2025 21:52:52 +0000</pubDate>
      <guid>https://yakinin.com/en/posts/20250819-openai-security-priorities/</guid>
      <description>&lt;p&gt;OpenAI&amp;rsquo;s proposal to encrypt AI is a commendable headline, but it sidesteps a more fundamental issue. Before we debate the complex philosophy of encrypting artificial intelligence, we should ask a simpler, more urgent question: have they patched the basic vulnerabilities in their existing systems?&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s easy to forget, but OpenAI has a history of security lapses, most notably the incident that leaked private user chat histories across the internet. This wasn&amp;rsquo;t a failure of advanced cryptography; it was a foundational security bug. They created a vulnerability and, as a result, exposed their clients&amp;rsquo; private conversations.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
