Congratulations!

[Valid Atom 1.0] This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://www.schneier.com/blog/index.xml

  1. <?xml version="1.0" encoding="UTF-8"?><feed
  2. xmlns="http://www.w3.org/2005/Atom"
  3. xmlns:thr="http://purl.org/syndication/thread/1.0"
  4. xml:lang="en-US"
  5. xmlns:georss="http://www.georss.org/georss"
  6. xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
  7. >
  8. <title type="text">Schneier on Security</title>
  9. <subtitle type="text"></subtitle>
  10.  
  11. <updated>2024-05-06T02:25:17Z</updated>
  12.  
  13. <link rel="alternate" type="text/html" href="https://www.schneier.com" />
  14. <id>https://www.schneier.com/feed/atom/</id>
  15. <link rel="self" type="application/atom+xml" href="https://www.schneier.com/feed/atom/" />
  16.  
  17. <icon>https://www.schneier.com/wp-content/uploads/2020/06/cropped-favicon-1-32x32.png</icon>
  18. <entry>
  19. <author>
  20. <name>Bruce Schneier</name>
  21. </author>
  22.  
  23. <title type="html"><![CDATA[New Lawsuit Attempting to Make Adversarial Interoperability Legal]]></title>
  24. <link rel="alternate" type="text/html" href="https://www.schneier.com/blog/archives/2024/05/new-lawsuit-attempting-to-make-adversarial-interoperability-legal.html" />
  25.  
  26. <id>https://www.schneier.com/?p=68871</id>
  27. <updated>2024-05-06T02:25:17Z</updated>
  28. <published>2024-05-06T11:03:08Z</published>
  29. <category scheme="https://www.schneier.com" term="Uncategorized" /><category scheme="https://www.schneier.com" term="copyright" /><category scheme="https://www.schneier.com" term="courts" />
  30. <summary type="html"><![CDATA[<p>Lots of complicated details here: too many for me to summarize well. It involves an obscure Section 230 provision&#8212;and an even more obscure typo. Read <a href="https://www.techdirt.com/2024/05/02/was-there-a-trojan-horse-hidden-in-section-230-all-along-that-could-enable-adversarial-interoperability/">this</a>.</p>
  31. ]]></summary>
  32.  
  33. <content type="html" xml:base="https://www.schneier.com/blog/archives/2024/05/new-lawsuit-attempting-to-make-adversarial-interoperability-legal.html"><![CDATA[<p>Lots of complicated details here: too many for me to summarize well. It involves an obscure Section 230 provision&#8212;and an even more obscure typo. Read <a href="https://www.techdirt.com/2024/05/02/was-there-a-trojan-horse-hidden-in-section-230-all-along-that-could-enable-adversarial-interoperability/">this</a>.</p>
  34. ]]></content>
  35. <link rel="replies" type="text/html" href="https://www.schneier.com/blog/archives/2024/05/new-lawsuit-attempting-to-make-adversarial-interoperability-legal.html#comments" thr:count="1" />
  36. <link rel="replies" type="application/atom+xml" href="https://www.schneier.com/blog/archives/2024/05/new-lawsuit-attempting-to-make-adversarial-interoperability-legal.html/feed/atom/" thr:count="1" />
  37. <thr:total>1</thr:total>
  38. </entry>
  39. <entry>
  40. <author>
  41. <name>Bruce Schneier</name>
  42. </author>
  43.  
  44. <title type="html"><![CDATA[Friday Squid Blogging: Squid Purses]]></title>
  45. <link rel="alternate" type="text/html" href="https://www.schneier.com/blog/archives/2024/05/friday-squid-blogging-squid-purses.html" />
  46.  
  47. <id>https://www.schneier.com/?p=68847</id>
  48. <updated>2024-04-30T16:57:41Z</updated>
  49. <published>2024-05-03T21:05:57Z</published>
  50. <category scheme="https://www.schneier.com" term="Uncategorized" /><category scheme="https://www.schneier.com" term="squid" />
  51. <summary type="html"><![CDATA[<p>Squid-shaped <a href="https://laughingsquid.com/sea-creature-bags-purses/">purses</a> for sale.</p>
  52. <p>As usual, you can also use this squid post to talk about the security stories in the news that I haven’t covered.</p>
  53. <p>Read my blog posting guidelines <a href="https://www.schneier.com/blog/archives/2017/03/commenting_poli.html">here</a>.</p>
  54. ]]></summary>
  55.  
  56. <content type="html" xml:base="https://www.schneier.com/blog/archives/2024/05/friday-squid-blogging-squid-purses.html"><![CDATA[<p>Squid-shaped <a href="https://laughingsquid.com/sea-creature-bags-purses/">purses</a> for sale.</p>
  57. <p>As usual, you can also use this squid post to talk about the security stories in the news that I haven’t covered.</p>
  58. <p>Read my blog posting guidelines <a href="https://www.schneier.com/blog/archives/2017/03/commenting_poli.html">here</a>.</p>
  59. ]]></content>
  60. <link rel="replies" type="text/html" href="https://www.schneier.com/blog/archives/2024/05/friday-squid-blogging-squid-purses.html#comments" thr:count="77" />
  61. <link rel="replies" type="application/atom+xml" href="https://www.schneier.com/blog/archives/2024/05/friday-squid-blogging-squid-purses.html/feed/atom/" thr:count="77" />
  62. <thr:total>77</thr:total>
  63. </entry>
  64. <entry>
  65. <author>
  66. <name>Bruce Schneier</name>
  67. </author>
  68.  
  69. <title type="html"><![CDATA[My TED Talks]]></title>
  70. <link rel="alternate" type="text/html" href="https://www.schneier.com/blog/archives/2024/05/my-ted-talks.html" />
  71.  
  72. <id>https://www.schneier.com/?p=68864</id>
  73. <updated>2024-05-03T18:13:24Z</updated>
  74. <published>2024-05-03T18:13:24Z</published>
  75. <category scheme="https://www.schneier.com" term="Uncategorized" /><category scheme="https://www.schneier.com" term="Schneier news" /><category scheme="https://www.schneier.com" term="TED" /><category scheme="https://www.schneier.com" term="videos" />
  76. <summary type="html"><![CDATA[<p>I have spoken at several TED conferences over the years.</p>
  77. <ul>
  78. <li>TEDxPSU 2010: &#8220;<a href="https://www.ted.com/talks/bruce_schneier_the_security_mirage?language=en">Reconceptualizing Security</a>&#8221;
  79. <li>TEDxCambridge 2013: &#8220;<a href="https://www.youtube.com/watch?v=h0d_QDgl3gI">The Battle for Power on the Internet</a>&#8221;
  80. <li>TEDMed 2016: &#8220;<a href="https://www.tedmed.com/talks/show?id=627334">Who Controls Your Medical Data</a>?&#8221;</ul>
  81. <p>I&#8217;m putting this here because I want all three links in one place.</p>
  82. ]]></summary>
  83.  
  84. <content type="html" xml:base="https://www.schneier.com/blog/archives/2024/05/my-ted-talks.html"><![CDATA[<p>I have spoken at several TED conferences over the years.</p>
  85. <ul>
  86. <li>TEDxPSU 2010: &#8220;<a href="https://www.ted.com/talks/bruce_schneier_the_security_mirage?language=en">Reconceptualizing Security</a>&#8221;
  87. <li>TEDxCambridge 2013: &#8220;<a href="https://www.youtube.com/watch?v=h0d_QDgl3gI">The Battle for Power on the Internet</a>&#8221;
  88. <li>TEDMed 2016: &#8220;<a href="https://www.tedmed.com/talks/show?id=627334">Who Controls Your Medical Data</a>?&#8221;</ul>
  89. <p>I&#8217;m putting this here because I want all three links in one place.</p>
  90. ]]></content>
  91. <link rel="replies" type="text/html" href="https://www.schneier.com/blog/archives/2024/05/my-ted-talks.html#comments" thr:count="1" />
  92. <link rel="replies" type="application/atom+xml" href="https://www.schneier.com/blog/archives/2024/05/my-ted-talks.html/feed/atom/" thr:count="1" />
  93. <thr:total>1</thr:total>
  94. </entry>
  95. <entry>
  96. <author>
  97. <name>Bruce Schneier</name>
  98. </author>
  99.  
  100. <title type="html"><![CDATA[Rare Interviews with Enigma Cryptanalyst Marian Rejewski]]></title>
  101. <link rel="alternate" type="text/html" href="https://www.schneier.com/blog/archives/2024/05/rare-interviews-with-enigma-cryptanalyst-marian-rejewski.html" />
  102.  
  103. <id>https://www.schneier.com/?p=68858</id>
  104. <updated>2024-05-02T16:12:36Z</updated>
  105. <published>2024-05-03T11:10:08Z</published>
  106. <category scheme="https://www.schneier.com" term="Uncategorized" /><category scheme="https://www.schneier.com" term="cryptanalysis" /><category scheme="https://www.schneier.com" term="Enigma" /><category scheme="https://www.schneier.com" term="history of cryptography" /><category scheme="https://www.schneier.com" term="war" />
  107. <summary type="html"><![CDATA[<p>The Polish Embassy has <a href="https://www.flyingpenguin.com/?p=56989">posted</a> a series of short interview segments with Marian Rejewski, the first person to crack the Enigma.</p>
  108. <p>Details from his <a href="https://www.flyingpenguin.com/?p=49767">biography</a>.</p>
  109. ]]></summary>
  110.  
  111. <content type="html" xml:base="https://www.schneier.com/blog/archives/2024/05/rare-interviews-with-enigma-cryptanalyst-marian-rejewski.html"><![CDATA[<p>The Polish Embassy has <a href="https://www.flyingpenguin.com/?p=56989">posted</a> a series of short interview segments with Marian Rejewski, the first person to crack the Enigma.</p>
  112. <p>Details from his <a href="https://www.flyingpenguin.com/?p=49767">biography</a>.</p>
  113. ]]></content>
  114. <link rel="replies" type="text/html" href="https://www.schneier.com/blog/archives/2024/05/rare-interviews-with-enigma-cryptanalyst-marian-rejewski.html#comments" thr:count="6" />
  115. <link rel="replies" type="application/atom+xml" href="https://www.schneier.com/blog/archives/2024/05/rare-interviews-with-enigma-cryptanalyst-marian-rejewski.html/feed/atom/" thr:count="6" />
  116. <thr:total>6</thr:total>
  117. </entry>
  118. <entry>
  119. <author>
  120. <name>Bruce Schneier</name>
  121. </author>
  122.  
  123. <title type="html"><![CDATA[The UK Bans Default Passwords]]></title>
  124. <link rel="alternate" type="text/html" href="https://www.schneier.com/blog/archives/2024/05/the-uk-bans-default-passwords.html" />
  125.  
  126. <id>https://www.schneier.com/?p=68854</id>
  127. <updated>2024-05-02T04:01:17Z</updated>
  128. <published>2024-05-02T11:05:03Z</published>
  129. <category scheme="https://www.schneier.com" term="Uncategorized" /><category scheme="https://www.schneier.com" term="botnets" /><category scheme="https://www.schneier.com" term="Internet of Things" /><category scheme="https://www.schneier.com" term="passwords" /><category scheme="https://www.schneier.com" term="UK" />
  130. <summary type="html"><![CDATA[<p>The UK is the first country to <a href="https://therecord.media/united-kingdom-bans-defalt-passwords-iot-devices">ban default passwords</a> on IoT devices.</p>
  131. <blockquote><p>On Monday, the United Kingdom became the first country in the world to ban default guessable usernames and passwords from these IoT devices. Unique passwords installed by default are still permitted.</p>
  132. <p>The <a href="https://www.legislation.gov.uk/ukpga/2022/46/contents/enacted">Product Security and Telecommunications Infrastructure Act 2022</a> (PSTI) introduces new minimum-security standards for manufacturers, and demands that these companies are open with consumers about how long their products will receive security updates for.</p></blockquote>
  133. <p>The UK may be the first country, but as far as I know, California is the first jurisdiction. It ...</p>]]></summary>
  134.  
  135. <content type="html" xml:base="https://www.schneier.com/blog/archives/2024/05/the-uk-bans-default-passwords.html"><![CDATA[<p>The UK is the first country to <a href="https://therecord.media/united-kingdom-bans-defalt-passwords-iot-devices">ban default passwords</a> on IoT devices.</p>
  136. <blockquote><p>On Monday, the United Kingdom became the first country in the world to ban default guessable usernames and passwords from these IoT devices. Unique passwords installed by default are still permitted.</p>
  137. <p>The <a href="https://www.legislation.gov.uk/ukpga/2022/46/contents/enacted">Product Security and Telecommunications Infrastructure Act 2022</a> (PSTI) introduces new minimum-security standards for manufacturers, and demands that these companies are open with consumers about how long their products will receive security updates for.</p></blockquote>
  138. <p>The UK may be the first country, but as far as I know, California is the first jurisdiction. It <a href="https://techcrunch.com/2018/10/05/california-passes-law-that-bans-default-passwords-in-connected-devices/">banned default passwords</a> in 2018, the law taking effect in 2020.</p>
  139. <p>This sort of thing benefits all of us everywhere. IoT manufacturers aren&#8217;t making two devices, one for California and one for the rest of the US. And they&#8217;re not going to make one for the UK and another for the rest of Europe, either. They&#8217;ll remove the default passwords and sell those devices everywhere.</p>
  140. <p>Another <a href="https://arstechnica.com/gadgets/2024/04/connected-devices-with-awful-default-passwords-now-illegal-in-uk/">news article</a>.</p>
  141. ]]></content>
  142. <link rel="replies" type="text/html" href="https://www.schneier.com/blog/archives/2024/05/the-uk-bans-default-passwords.html#comments" thr:count="18" />
  143. <link rel="replies" type="application/atom+xml" href="https://www.schneier.com/blog/archives/2024/05/the-uk-bans-default-passwords.html/feed/atom/" thr:count="18" />
  144. <thr:total>18</thr:total>
  145. </entry>
  146. <entry>
  147. <author>
  148. <name>Bruce Schneier</name>
  149. </author>
  150.  
  151. <title type="html"><![CDATA[AI Voice Scam]]></title>
  152. <link rel="alternate" type="text/html" href="https://www.schneier.com/blog/archives/2024/05/ai-voice-scam.html" />
  153.  
  154. <id>https://www.schneier.com/?p=68851</id>
  155. <updated>2024-04-30T17:02:21Z</updated>
  156. <published>2024-05-01T11:09:23Z</published>
  157. <category scheme="https://www.schneier.com" term="Uncategorized" /><category scheme="https://www.schneier.com" term="artificial intelligence" /><category scheme="https://www.schneier.com" term="scams" /><category scheme="https://www.schneier.com" term="social engineering" />
  158. <summary type="html"><![CDATA[<p>Scammers <a href="https://www.theguardian.com/technology/2024/apr/28/bbc-presenters-likeness-used-in-advert-after-firm-tricked-by-ai-generated-voice">tricked</a> a company into believing they were dealing with a BBC presenter. They faked her voice, and accepted money intended for her.</p>
  159. ]]></summary>
  160.  
  161. <content type="html" xml:base="https://www.schneier.com/blog/archives/2024/05/ai-voice-scam.html"><![CDATA[<p>Scammers <a href="https://www.theguardian.com/technology/2024/apr/28/bbc-presenters-likeness-used-in-advert-after-firm-tricked-by-ai-generated-voice">tricked</a> a company into believing they were dealing with a BBC presenter. They faked her voice, and accepted money intended for her.</p>
  162. ]]></content>
  163. <link rel="replies" type="text/html" href="https://www.schneier.com/blog/archives/2024/05/ai-voice-scam.html#comments" thr:count="25" />
  164. <link rel="replies" type="application/atom+xml" href="https://www.schneier.com/blog/archives/2024/05/ai-voice-scam.html/feed/atom/" thr:count="25" />
  165. <thr:total>25</thr:total>
  166. </entry>
  167. <entry>
  168. <author>
  169. <name>Bruce Schneier</name>
  170. </author>
  171.  
  172. <title type="html"><![CDATA[WhatsApp in India]]></title>
  173. <link rel="alternate" type="text/html" href="https://www.schneier.com/blog/archives/2024/04/whatsapp-in-india.html" />
  174.  
  175. <id>https://www.schneier.com/?p=68844</id>
  176. <updated>2024-04-29T16:02:06Z</updated>
  177. <published>2024-04-30T11:00:28Z</published>
  178. <category scheme="https://www.schneier.com" term="Uncategorized" /><category scheme="https://www.schneier.com" term="encryption" /><category scheme="https://www.schneier.com" term="India" /><category scheme="https://www.schneier.com" term="Meta" /><category scheme="https://www.schneier.com" term="privacy" /><category scheme="https://www.schneier.com" term="WhatsApp" />
  179. <summary type="html"><![CDATA[<p>Meta has threatened to <a href="https://thewire.in/law/disappearing-messages-whatsapp-says-will-leave-india-is-forced-to-break-encryption">pull WhatsApp</a> out of India if the courts try to force it to break its end-to-end encryption.</p>
  180. ]]></summary>
  181.  
  182. <content type="html" xml:base="https://www.schneier.com/blog/archives/2024/04/whatsapp-in-india.html"><![CDATA[<p>Meta has threatened to <a href="https://thewire.in/law/disappearing-messages-whatsapp-says-will-leave-india-is-forced-to-break-encryption">pull WhatsApp</a> out of India if the courts try to force it to break its end-to-end encryption.</p>
  183. ]]></content>
  184. <link rel="replies" type="text/html" href="https://www.schneier.com/blog/archives/2024/04/whatsapp-in-india.html#comments" thr:count="32" />
  185. <link rel="replies" type="application/atom+xml" href="https://www.schneier.com/blog/archives/2024/04/whatsapp-in-india.html/feed/atom/" thr:count="32" />
  186. <thr:total>32</thr:total>
  187. </entry>
  188. <entry>
  189. <author>
  190. <name>Bruce Schneier</name>
  191. </author>
  192.  
  193. <title type="html"><![CDATA[Whale Song Code]]></title>
  194. <link rel="alternate" type="text/html" href="https://www.schneier.com/blog/archives/2024/04/whale-song-code.html" />
  195.  
  196. <id>https://www.schneier.com/?p=68841</id>
  197. <updated>2024-04-29T03:12:29Z</updated>
  198. <published>2024-04-29T11:07:42Z</published>
  199. <category scheme="https://www.schneier.com" term="Uncategorized" /><category scheme="https://www.schneier.com" term="espionage" /><category scheme="https://www.schneier.com" term="history of cryptography" /><category scheme="https://www.schneier.com" term="military" />
  200. <summary type="html"><![CDATA[<p>During the Cold War, the US Navy tried to make a <a href="https://www.twz.com/8778/the-u-s-navy-tried-to-turn-whale-songs-into-secret-code">secret code</a> out of whale song.</p>
  201. <blockquote><p>The basic plan was to develop coded messages from recordings of whales, dolphins, sea lions, and seals. The submarine would broadcast the noises and a computer&#8212;the Combo Signal Recognizer (CSR)&#8212;would detect the specific patterns and decode them on the other end. In theory, this idea was relatively simple. As work progressed, the Navy found a number of complicated problems to overcome, the bulk of which centered on the authenticity of the code itself.</p>
  202. <p>The message structure couldn&#8217;t just substitute the moaning of a whale or a crying seal for As and Bs or even whole words. In addition, the sounds Navy technicians recorded between 1959 and 1965 all had natural background noise. With the technology available, it would have been hard to scrub that out. Repeated blasts of the same sounds with identical extra noise would stand out to even untrained sonar operators...</p></blockquote>]]></summary>
  203.  
  204. <content type="html" xml:base="https://www.schneier.com/blog/archives/2024/04/whale-song-code.html"><![CDATA[<p>During the Cold War, the US Navy tried to make a <a href="https://www.twz.com/8778/the-u-s-navy-tried-to-turn-whale-songs-into-secret-code">secret code</a> out of whale song.</p>
  205. <blockquote><p>The basic plan was to develop coded messages from recordings of whales, dolphins, sea lions, and seals. The submarine would broadcast the noises and a computer&#8212;the Combo Signal Recognizer (CSR)&#8212;would detect the specific patterns and decode them on the other end. In theory, this idea was relatively simple. As work progressed, the Navy found a number of complicated problems to overcome, the bulk of which centered on the authenticity of the code itself.</p>
  206. <p>The message structure couldn&#8217;t just substitute the moaning of a whale or a crying seal for As and Bs or even whole words. In addition, the sounds Navy technicians recorded between 1959 and 1965 all had natural background noise. With the technology available, it would have been hard to scrub that out. Repeated blasts of the same sounds with identical extra noise would stand out to even untrained sonar operators.</p></blockquote>
  207. <p>In the end, it didn&#8217;t work.</p>
  208. ]]></content>
  209. <link rel="replies" type="text/html" href="https://www.schneier.com/blog/archives/2024/04/whale-song-code.html#comments" thr:count="12" />
  210. <link rel="replies" type="application/atom+xml" href="https://www.schneier.com/blog/archives/2024/04/whale-song-code.html/feed/atom/" thr:count="12" />
  211. <thr:total>12</thr:total>
  212. </entry>
  213. <entry>
  214. <author>
  215. <name>Bruce Schneier</name>
  216. </author>
  217.  
  218. <title type="html"><![CDATA[Friday Squid Blogging: Searching for the Colossal Squid]]></title>
  219. <link rel="alternate" type="text/html" href="https://www.schneier.com/blog/archives/2024/04/friday-squid-blogging-searching-for-the-colossal-squid.html" />
  220.  
  221. <id>https://www.schneier.com/?p=68819</id>
  222. <updated>2024-04-19T14:58:23Z</updated>
  223. <published>2024-04-26T21:07:33Z</published>
  224. <category scheme="https://www.schneier.com" term="Uncategorized" /><category scheme="https://www.schneier.com" term="squid" />
  225. <summary type="html"><![CDATA[<p>A cruise ship is <a href="https://www.businessinsider.com/cruise-ship-scientists-tourists-colossal-squid-antarctica-2024-4">searching</a> for the colossal squid.</p>
  226. <p>As usual, you can also use this squid post to talk about the security stories in the news that I haven’t covered.</p>
  227. <p>Read my blog posting guidelines <a href="https://www.schneier.com/blog/archives/2017/03/commenting_poli.html">here</a>.</p>
  228. ]]></summary>
  229.  
  230. <content type="html" xml:base="https://www.schneier.com/blog/archives/2024/04/friday-squid-blogging-searching-for-the-colossal-squid.html"><![CDATA[<p>A cruise ship is <a href="https://www.businessinsider.com/cruise-ship-scientists-tourists-colossal-squid-antarctica-2024-4">searching</a> for the colossal squid.</p>
  231. <p>As usual, you can also use this squid post to talk about the security stories in the news that I haven’t covered.</p>
  232. <p>Read my blog posting guidelines <a href="https://www.schneier.com/blog/archives/2017/03/commenting_poli.html">here</a>.</p>
  233. ]]></content>
  234. <link rel="replies" type="text/html" href="https://www.schneier.com/blog/archives/2024/04/friday-squid-blogging-searching-for-the-colossal-squid.html#comments" thr:count="112" />
  235. <link rel="replies" type="application/atom+xml" href="https://www.schneier.com/blog/archives/2024/04/friday-squid-blogging-searching-for-the-colossal-squid.html/feed/atom/" thr:count="112" />
  236. <thr:total>112</thr:total>
  237. </entry>
  238. <entry>
  239. <author>
  240. <name>Bruce Schneier</name>
  241. </author>
  242.  
  243. <title type="html"><![CDATA[Long Article on GM Spying on Its Cars’ Drivers]]></title>
  244. <link rel="alternate" type="text/html" href="https://www.schneier.com/blog/archives/2024/04/long-article-on-gm-spying-on-its-cars-drivers.html" />
  245.  
  246. <id>https://www.schneier.com/?p=68836</id>
  247. <updated>2024-04-25T03:48:29Z</updated>
  248. <published>2024-04-26T11:01:09Z</published>
  249. <category scheme="https://www.schneier.com" term="Uncategorized" /><category scheme="https://www.schneier.com" term="cars" /><category scheme="https://www.schneier.com" term="insurance" /><category scheme="https://www.schneier.com" term="privacy" /><category scheme="https://www.schneier.com" term="surveillance" />
  250. <summary type="html"><![CDATA[<p>Kashmir Hill has a <a href="https://www.nytimes.com/2024/04/23/technology/general-motors-spying-driver-data-consent.html?unlocked_article_code=1.m00.gIzH.YdQ-yszzdzq6&#038;utm_source=substack&#038;utm_medium=email">really good article</a> on how GM tricked its drivers into letting it spy on them&#8212;and then sold that data to insurance companies.</p>
  251. ]]></summary>
  252.  
  253. <content type="html" xml:base="https://www.schneier.com/blog/archives/2024/04/long-article-on-gm-spying-on-its-cars-drivers.html"><![CDATA[<p>Kashmir Hill has a <a href="https://www.nytimes.com/2024/04/23/technology/general-motors-spying-driver-data-consent.html?unlocked_article_code=1.m00.gIzH.YdQ-yszzdzq6&#038;utm_source=substack&#038;utm_medium=email">really good article</a> on how GM tricked its drivers into letting it spy on them&#8212;and then sold that data to insurance companies.</p>
  254. ]]></content>
  255. <link rel="replies" type="text/html" href="https://www.schneier.com/blog/archives/2024/04/long-article-on-gm-spying-on-its-cars-drivers.html#comments" thr:count="17" />
  256. <link rel="replies" type="application/atom+xml" href="https://www.schneier.com/blog/archives/2024/04/long-article-on-gm-spying-on-its-cars-drivers.html/feed/atom/" thr:count="17" />
  257. <thr:total>17</thr:total>
  258. </entry>
  259. </feed>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid Atom 1.0" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.schneier.com/blog/index.xml

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda