A place to cache linked articles (think custom and personal wayback machine)
Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.

index.html 19KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223
  1. <!doctype html><!-- This is a valid HTML5 document. -->
  2. <!-- Screen readers, SEO, extensions and so on. -->
  3. <html lang="en">
  4. <!-- Has to be within the first 1024 bytes, hence before the `title` element
  5. See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
  6. <meta charset="utf-8">
  7. <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
  8. <!-- The viewport meta is quite crowded and we are responsible for that.
  9. See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
  10. <meta name="viewport" content="width=device-width,initial-scale=1">
  11. <!-- Required to make a valid HTML5 document. -->
  12. <title>Microsoft's new Windows 11 Recall is a privacy nightmare (archive) — David Larlet</title>
  13. <meta name="description" content="Publication mise en cache pour en conserver une trace.">
  14. <!-- That good ol' feed, subscribe :). -->
  15. <link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
  16. <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
  17. <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
  18. <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
  19. <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
  20. <link rel="manifest" href="/static/david/icons2/site.webmanifest">
  21. <link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
  22. <link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
  23. <meta name="msapplication-TileColor" content="#f7f7f7">
  24. <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
  25. <meta name="theme-color" content="#f7f7f7" media="(prefers-color-scheme: light)">
  26. <meta name="theme-color" content="#272727" media="(prefers-color-scheme: dark)">
  27. <!-- Is that even respected? Retrospectively? What a shAItshow…
  28. https://neil-clarke.com/block-the-bots-that-feed-ai-models-by-scraping-your-website/ -->
  29. <meta name="robots" content="noai, noimageai">
  30. <!-- Documented, feel free to shoot an email. -->
  31. <link rel="stylesheet" href="/static/david/css/style_2021-01-20.css">
  32. <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
  33. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
  34. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
  35. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
  36. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
  37. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
  38. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
  39. <script>
  40. function toggleTheme(themeName) {
  41. document.documentElement.classList.toggle(
  42. 'forced-dark',
  43. themeName === 'dark'
  44. )
  45. document.documentElement.classList.toggle(
  46. 'forced-light',
  47. themeName === 'light'
  48. )
  49. }
  50. const selectedTheme = localStorage.getItem('theme')
  51. if (selectedTheme !== 'undefined') {
  52. toggleTheme(selectedTheme)
  53. }
  54. </script>
  55. <meta name="robots" content="noindex, nofollow">
  56. <meta content="origin-when-cross-origin" name="referrer">
  57. <!-- Canonical URL for SEO purposes -->
  58. <link rel="canonical" href="https://www.bleepingcomputer.com/news/microsoft/microsofts-new-windows-11-recall-is-a-privacy-nightmare/">
  59. <body class="remarkdown h1-underline h2-underline h3-underline em-underscore hr-center ul-star pre-tick" data-instant-intensity="viewport-all">
  60. <article>
  61. <header>
  62. <h1>Microsoft's new Windows 11 Recall is a privacy nightmare</h1>
  63. </header>
  64. <nav>
  65. <p class="center">
  66. <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
  67. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-home"></use>
  68. </svg> Accueil</a> •
  69. <a href="https://www.bleepingcomputer.com/news/microsoft/microsofts-new-windows-11-recall-is-a-privacy-nightmare/" title="Lien vers le contenu original">Source originale</a>
  70. <br>
  71. Mis en cache le 2024-05-24
  72. </p>
  73. </nav>
  74. <hr>
  75. <p><img alt="Windows 11 Recall" src="https://www.bleepstatic.com/content/hl-images/2024/05/20/windows-11-recall.jpg"></p>
  76. <p>Microsoft's announcement of the new AI-powered Windows 11 Recall feature has sparked a lot of concern, with many thinking that it has created massive privacy risks and a new attack vector that threat actors can exploit to steal data.</p>
  77. <p>Revealed during a Monday AI event, the feature is designed to help "recall" information you have looked at in the past, making it easily accessible via a simple search.</p>
  78. <p>While it's currently only available on Copilot+ PCs running Snapdragon X ARM processors, Microsoft says they are working with Intel and AMD to create compatible CPUs.</p>
  79. <p>Recall works by taking a screenshot of your active window every few seconds, recording everything you do in Windows for up to three months by default.</p>
  80. <p>These snapshots will be analyzed by the on-device Neural Processing Unit (NPU) and an AI model to extract data from the screenshot. The data will be saved in a semantic index, allowing Windows users to browse through the snapshot history or search using human language queries.</p>
  81. <div>
  82. <figure class="image"><img alt="Windows 11 Recall" src="https://www.bleepstatic.com/images/news/Microsoft/windows-11/r/recall/windows-11-recal.jpg"><figcaption><strong>Windows 11 Recall</strong></figcaption></figure></div>
  83. <p>Microsoft says that all of this data is encrypted using BitLocker tied to the user's Windows account and is not shared with other users on the same device.</p>
  84. <p>While this sounds fun and interesting, it immediately raised concerns about obvious privacy risks and whether Microsoft plans on gobbling up all of this data.</p>
  85. <p>However, Microsoft says Recall has been designed so that all of the data is saved directly on the user's device in an encrypted format, providing users with complete control over the feature, including if it's enabled and what apps it can take screenshots of.</p>
  86. <div class="fan_quote">
  87. <p>"Recall is a key part of what makes Copilot+ PCs special, and Microsoft built privacy into Recall's design from the ground up. On Copilot+ PCs powered by a Snapdragon® X Series processor, you will see the Recall taskbar icon after you first activate your device. You can use that icon to open Recall's settings and make choices about what snapshots Recall collects and stores on your device. You can limit which snapshots Recall collects; for example, you can select specific apps or websites visited in a supported browser to filter out of your snapshots. In addition, you can pause snapshots on demand from the Recall icon in the system tray, clear some or all snapshots that have been stored, or delete all the snapshots from your device."</p><p>
  88. ❖ Microsoft</p></div>
  89. <p>Microsoft also says it will not create screenshots of Microsoft Edge's InPrivate windows (and other Chromium-based browsers) or content protected by DRM. However, they have not confirmed whether other browser's private modes, like Firefox, will be supported.</p>
  90. <p>In a Monday press event, Yusuf Mehdi, Corporate Vice President &amp; Consumer Chief Marketing Officer, assured journalists that Microsoft is taking a very conservative approach with Recall.</p>
  91. <p>"We're going to keep your Recall index private and local and secure on just the device," said Mehdi.</p>
  92. <p>"We won't use any of that information to train any AI model, and we put you completely in control with the ability to edit and delete anything that is captured."</p>
  93. <p>Furthermore, Microsoft also reiterated to BleepingComputer that data for Recall will only be available locally and not be stored in the cloud, with the company once again restating that "data is not accessed by Microsoft."</p>
  94. <p>Microsoft has also started to share more technical details, such as <a href="https://learn.microsoft.com/en-us/windows/client-management/manage-recall#configure-policies-for-recall" target="_blank" rel="nofollow noopener">group policies</a> that can be used to disable Recall company-wide and how end users can <a href="https://support.microsoft.com/en-us/windows/privacy-and-control-over-your-recall-experience-d404f672-7647-41e5-886c-a3c59680af15" target="_blank" rel="nofollow noopener">disable the feature</a>.</p>
  95. <h2>Cybersecurity experts and regular users still concerned</h2>
  96. <p>Microsoft's promises have not done much to reassure the cybersecurity community or its customers, with <a data-sk="tooltip_parent" data-stringify-link="https://x.com/BleepinComputer/status/1792631130983706926" delay="150" href="https://x.com/BleepinComputer/status/1792631130983706926" rel="noopener noreferrer" target="_blank">our tweet</a> regarding this new feature receiving over 90 comments, all negative.</p>
  97. <p><a href="https://twitter.com/SchizoDuckie/status/1792640796333650342" target="_blank" rel="nofollow noopener"><img alt="Schizoduckie tweet" src="https://www.bleepstatic.com/images/news/Microsoft/windows-11/r/recall/security-concerns/schizo-tweet.jpg"></a></p>
  98. <p>So, why are most cybersecurity experts, researchers, and analysts so worried about this feature?</p>
  99. <p>First and foremost, large companies have a history of exploiting users' data for their own profit, making it <a data-sk="tooltip_parent" data-stringify-link="https://x.com/MegaMarian12350/status/1792642295814082659" delay="150" href="https://x.com/MegaMarian12350/status/1792642295814082659" rel="noopener noreferrer" target="_blank">hard for users to trust Microsoft</a> when they say they won't access the Recall data.</p>
  100. <p>Users are not alone, as the United Kingdom's data protection agency, the Information Commissioner's Office (ICO), is also contacting Microsoft to ensure that users' data will be properly safeguarded and not used by the company.</p>
  101. <p>"We expect organisations to be transparent with users about how their data is being used and only process personal data to the extent that it is necessary to achieve a specific purpose. Industry must consider data protection from the outset and rigorously assess and mitigate risks to peoples' rights and freedoms before bringing products to market," reads a <a href="https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2024/05/statement-in-response-to-microsoft-recall-feature/" target="_blank" rel="nofollow noopener">press statement</a> from the ICO.</p>
  102. <p>"We are making enquiries with Microsoft to understand the safeguards in place to protect user privacy."</p>
  103. <p>Even if we accept that Microsoft will not access Recall data, there are still massive security and privacy implications with this product.</p>
  104. <p>Microsoft admits that the feature performs no content moderation, meaning it will gobble up anything it sees, including passwords in a password manager or your account numbers on your banking website.</p>
  105. <p>Or if you are in Word, writing a confidential agreement, a screenshot of that content will be created, too. If you have a single PC and share it with others, then you may want to be careful about what pictures or videos you look at, as, guess what, those will be recorded as well.</p>
  106. <p>Yes, you can block apps from being screenshotted by this feature, but most people will just let it run without mucking around with the feature's settings.</p>
  107. <p>All of this information is now stored in Windows 11's semantic index and easily searchable by anyone with access to your PC, whether authorized or not.</p>
  108. <p>That's just the tip of the iceberg, though.</p>
  109. <p>If a threat actor or malware compromised your device, all of this data will already be decrypted by Bitlocker, making it accessible to the hacker. </p>
  110. <p>For example, a threat actor or malware could simply steal a Recall database and upload it to their own servers for analysis. This information could then be used to extort users or potentially breach user's accounts if credentials were exposed.</p>
  111. <p>Cybersecurity expert Kevin Beaumont, known to be an outspoken critic of Microsoft at times, also expressed concern about how this feature creates a massive attack surface, likening it to a keylogger "baked into Windows."</p>
  112. <p>"If you look at what has happened historically with infostealer malware — malicious software snuck onto PCs — it has pivoted to automatically steal browser passwords stored locally," Beaumont explained in a <a href="https://doublepulsar.com/how-the-new-microsoft-recall-feature-fundamentally-undermines-windows-security-aa072829f218" target="_blank" rel="nofollow noopener">new blog post</a>.</p>
  113. <p>"In other words, if a malicious threat actor gains access to a system, they already steal important databases stored locally. They can just extend this to steal information recorded by Copilot's Recall feature."</p>
  114. <p>And it's not only information-stealing malware, as enterprise-targeting malware like TrickBot had previously included modules that would<a href="https://www.bleepingcomputer.com/news/security/trickbot-now-steals-windows-active-directory-credentials/" target="_blank"> steal a domain's Active Directory database</a> for offline cracking of credentials. There is nothing to stop malware from taking a similar approach and stealing the Recall databases as well.</p>
  115. <p>Microsoft has always taken the stance with vulnerabilities and attacks that once a device is compromised, all bets are off, and security boundaries are thrown out the window.</p>
  116. <p>Basically, you got infected or fell for a social engineering attack, so it's your fault all these bad things will happen to you.</p>
  117. <p>However, as Microsoft is one of, if not <strong>the</strong>, largest caretakers of consumer data and computing security, it seems irresponsible to introduce additional risk into an already risky environment.</p>
  118. <p>While we can go on and on expressing how this feature is a massive privacy risk, I will instead leave you with this quote from <a href="https://blogs.microsoft.com/blog/2024/05/03/prioritizing-security-above-all-else/" target="_blank" rel="nofollow noopener">Microsoft's recent pledge</a> to prioritize security above all else.</p>
  119. <p>"If you're faced with the tradeoff between security and another priority, your answer is clear: <strong>Do security</strong>. In some cases, this will mean prioritizing security above other things we do, such as releasing new features or providing ongoing support for legacy systems," Microsoft's CEO Satya Nadella said in an email to Microsoft employees.</p>
  120. <p>"This is key to advancing both our platform quality and capability such that we can protect the digital estates of our customers and build a safer world for all."</p>
  121. <p><em>Update 5/22/24: This article previously said Microsoft is working with Intel and AMD to make all Windows 11 devices compatible, when they are instead working with them to make compatible CPUs.</em></p>
  122. </article>
  123. <hr>
  124. <footer>
  125. <p>
  126. <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
  127. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-home"></use>
  128. </svg> Accueil</a> •
  129. <a href="/david/log/" title="Accès au flux RSS"><svg class="icon icon-rss2">
  130. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-rss2"></use>
  131. </svg> Suivre</a> •
  132. <a href="http://larlet.com" title="Go to my English profile" data-instant><svg class="icon icon-user-tie">
  133. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-user-tie"></use>
  134. </svg> Pro</a> •
  135. <a href="mailto:david%40larlet.fr" title="Envoyer un courriel"><svg class="icon icon-mail">
  136. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-mail"></use>
  137. </svg> Email</a> •
  138. <abbr class="nowrap" title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340"><svg class="icon icon-hammer2">
  139. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-hammer2"></use>
  140. </svg> Légal</abbr>
  141. </p>
  142. <template id="theme-selector">
  143. <form>
  144. <fieldset>
  145. <legend><svg class="icon icon-brightness-contrast">
  146. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-brightness-contrast"></use>
  147. </svg> Thème</legend>
  148. <label>
  149. <input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
  150. </label>
  151. <label>
  152. <input type="radio" value="dark" name="chosen-color-scheme"> Foncé
  153. </label>
  154. <label>
  155. <input type="radio" value="light" name="chosen-color-scheme"> Clair
  156. </label>
  157. </fieldset>
  158. </form>
  159. </template>
  160. </footer>
  161. <script src="/static/david/js/instantpage-5.1.0.min.js" type="module"></script>
  162. <script>
  163. function loadThemeForm(templateName) {
  164. const themeSelectorTemplate = document.querySelector(templateName)
  165. const form = themeSelectorTemplate.content.firstElementChild
  166. themeSelectorTemplate.replaceWith(form)
  167. form.addEventListener('change', (e) => {
  168. const chosenColorScheme = e.target.value
  169. localStorage.setItem('theme', chosenColorScheme)
  170. toggleTheme(chosenColorScheme)
  171. })
  172. const selectedTheme = localStorage.getItem('theme')
  173. if (selectedTheme && selectedTheme !== 'undefined') {
  174. form.querySelector(`[value="${selectedTheme}"]`).checked = true
  175. }
  176. }
  177. const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
  178. window.addEventListener('load', () => {
  179. let hasDarkRules = false
  180. for (const styleSheet of Array.from(document.styleSheets)) {
  181. let mediaRules = []
  182. for (const cssRule of styleSheet.cssRules) {
  183. if (cssRule.type !== CSSRule.MEDIA_RULE) {
  184. continue
  185. }
  186. // WARNING: Safari does not have/supports `conditionText`.
  187. if (cssRule.conditionText) {
  188. if (cssRule.conditionText !== prefersColorSchemeDark) {
  189. continue
  190. }
  191. } else {
  192. if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
  193. continue
  194. }
  195. }
  196. mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
  197. }
  198. // WARNING: do not try to insert a Rule to a styleSheet you are
  199. // currently iterating on, otherwise the browser will be stuck
  200. // in a infinite loop…
  201. for (const mediaRule of mediaRules) {
  202. styleSheet.insertRule(mediaRule.cssText)
  203. hasDarkRules = true
  204. }
  205. }
  206. if (hasDarkRules) {
  207. loadThemeForm('#theme-selector')
  208. }
  209. })
  210. </script>
  211. </body>
  212. </html>