<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>keys &#8211; Noise</title>
	<atom:link href="https://noise.getoto.net/tag/keys/feed/" rel="self" type="application/rss+xml" />
	<link>https://noise.getoto.net</link>
	<description>The collective thoughts of the interwebz</description>
	<lastBuildDate>Mon, 24 Nov 2025 16:47:54 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>
	<item>
		<title>IACR Nullifies Election Because of Lost Decryption Key</title>
		<link>https://noise.getoto.net/2025/11/24/iacr-nullifies-election-because-of-lost-decryption-key/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Mon, 24 Nov 2025 12:03:46 +0000</pubDate>
				<category><![CDATA[encryption]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[operational security]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[voting]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=71237</guid>

					<description><![CDATA[<p>The International Association of Cryptologic Research—the academic cryptography association that’s been putting conferences like Crypto (back when “crypto” meant “cryptography”) and Eurocrypt since the 1980s—had to <a href="https://www.iacr.org/news/item/27138">nullify</a> an online election when trustee Moti Yung lost his decryption key.</p>
<blockquote><p>For this election and in accordance with the bylaws of the IACR, the three members of the IACR 2025 Election Committee acted as independent trustees, each holding a portion of the cryptographic key material required to jointly decrypt the results. This aspect of Helios’ design ensures that no two trustees could collude to determine the outcome of an election or the contents of individual votes on their own: all trustees must provide their decryption shares...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Improvements in Brute Force Attacks</title>
		<link>https://noise.getoto.net/2025/03/17/improvements-in-brute-force-attacks/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Mon, 17 Mar 2025 15:09:57 +0000</pubDate>
				<category><![CDATA[academic papers]]></category>
		<category><![CDATA[cryptanalysis]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=70019</guid>

					<description><![CDATA[<p>New paper: “<a href="https://tosc.iacr.org/index.php/ToSC/article/view/12078/11919">GPU Assisted Brute Force Cryptanalysis of GPRS, GSM, RFID, and TETRA: Brute Force Cryptanalysis of KASUMI, SPECK, and TEA3</a>.”</p>
<blockquote><p><b>Abstract:</b> Key lengths in symmetric cryptography are determined with respect to the brute force attacks with current technology. While nowadays at least 128-bit keys are recommended, there are many standards and real-world applications that use shorter keys. In order to estimate the actual threat imposed by using those short keys, precise estimates for attacks are crucial.</p>
<p>In this work we provide optimized implementations of several widely used algorithms on GPUs, leading to interesting insights on the cost of brute force attacks on several real-word applications...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Compromising the Secure Boot Process</title>
		<link>https://noise.getoto.net/2024/07/26/compromising-the-secure-boot-process/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Fri, 26 Jul 2024 16:21:42 +0000</pubDate>
				<category><![CDATA[Cryptography]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[passwords]]></category>
		<category><![CDATA[supply chain]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[vulnerabilities]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=69197</guid>

					<description><![CDATA[<p>This <a href="https://arstechnica.com/security/2024/07/secure-boot-is-completely-compromised-on-200-models-from-5-big-device-makers/">isn’t good</a>:</p>
<blockquote><p>On Thursday, researchers from security firm Binarly revealed that Secure Boot is completely compromised on more than 200 device models sold by Acer, Dell, Gigabyte, Intel, and Supermicro. The cause: a cryptographic key underpinning Secure Boot on those models that was compromised in 2022. In a public GitHub repository committed in December of that year, someone working for multiple US-based device manufacturers published what’s known as a platform key, the cryptographic key that forms the root-of-trust anchor between the hardware device and the firmware that runs on it. The repository was located at https://github.com/raywu-aaeon/Ryzen2000_4000.git, and it’s not clear when it was taken down...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Recovering Public Keys from Signatures</title>
		<link>https://noise.getoto.net/2024/06/20/recovering-public-keys-from-signatures/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Thu, 20 Jun 2024 11:10:53 +0000</pubDate>
				<category><![CDATA[anonymity]]></category>
		<category><![CDATA[cryptanalysis]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[signatures]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=69066</guid>

					<description><![CDATA[Interesting summary of various ways to derive the public key from digitally signed files.
Normally, with a signature scheme, you have the public key and want to know whether a given signature is valid. But what if we instead have a message and a signat...]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Detect Stripe keys in S3 buckets with Amazon Macie</title>
		<link>https://noise.getoto.net/2024/02/19/detect-stripe-keys-in-s3-buckets-with-amazon-macie/</link>
		
		<dc:creator><![CDATA[Koulick Ghosh]]></dc:creator>
		<pubDate>Mon, 19 Feb 2024 18:58:35 +0000</pubDate>
				<category><![CDATA[Amazon Macie]]></category>
		<category><![CDATA[Amazon S3]]></category>
		<category><![CDATA[credentials]]></category>
		<category><![CDATA[Foundational (100)]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[PII]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[Sensitive Data Discovery]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=0d810cdc630619e00104441c1b089084</guid>

					<description><![CDATA[Many customers building applications on Amazon Web Services (AWS) use Stripe global payment services to help get their product out faster and grow revenue, especially in the internet economy. It’s critical for customers to securely and properly handle the credentials used to authenticate with Stripe services. Much like your AWS API keys, which enable access […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Digital Car Keys Are Coming</title>
		<link>https://noise.getoto.net/2023/11/28/digital-car-keys-are-coming/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Tue, 28 Nov 2023 20:19:58 +0000</pubDate>
				<category><![CDATA[cars]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[smartphones]]></category>
		<category><![CDATA[transportation]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=68141</guid>

					<description><![CDATA[Soon we will be able to unlock and start our cars from our phones. Let&#8217;s hope people are thinking about security.
]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Cryptocurrency Startup Loses Encryption Key for Electronic Wallet</title>
		<link>https://noise.getoto.net/2023/09/06/cryptocurrency-startup-loses-encryption-key-for-electronic-wallet/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Wed, 06 Sep 2023 11:05:27 +0000</pubDate>
				<category><![CDATA[cryptocurrency]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=67749</guid>

					<description><![CDATA[The cryptocurrency fintech startup Prime Trust lost the encryption key to its hardware wallet&#8212;and the recovery key&#8212;and therefore $38.9 million. It is now in bankruptcy.
I can&#8217;t understand why anyone thinks these technologies are a goo...]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Cryptographic Flaw in Libbitcoin Explorer Cryptocurrency Wallet</title>
		<link>https://noise.getoto.net/2023/08/10/cryptographic-flaw-in-libbitcoin-explorer-cryptocurrency-wallet/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Thu, 10 Aug 2023 11:12:46 +0000</pubDate>
				<category><![CDATA[cryptocurrency]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[random numbers]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=67675</guid>

					<description><![CDATA[Cryptographic flaws still matter. Here&#8217;s a flaw in the random-number generator used to create private keys. The seed has only 32 bits of entropy.
Seems like this flaw is being exploited in the wild.
EDITED TO ADD (8/14): A good explainer.
]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Microsoft Signing Key Stolen by Chinese</title>
		<link>https://noise.getoto.net/2023/08/07/microsoft-signing-key-stolen-by-chinese/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Mon, 07 Aug 2023 11:03:56 +0000</pubDate>
				<category><![CDATA[authentication]]></category>
		<category><![CDATA[backdoors]]></category>
		<category><![CDATA[china]]></category>
		<category><![CDATA[cybersecurity]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=67641</guid>

					<description><![CDATA[<p>A bunch of networks, including <a href="https://techcrunch.com/2023/07/12/chinese-hackers-us-government-microsoft-email/">US Government networks</a>, have been hacked by the Chinese. The hackers used forged authentication tokens to access user email, using a <a href="https://www.bleepingcomputer.com/news/microsoft/microsoft-still-unsure-how-hackers-stole-azure-ad-signing-key/">stolen</a> <a href="https://techcrunch.com/2023/07/17/microsoft-lost-keys-government-hacked/">Microsoft</a> Azure account consumer signing key. Congress <a href="https://www.documentcloud.org/documents/23888590-wyden_letter_to_cisa-doj-ftc_re_2023_microsoft_breach">wants</a> <a href="https://www.washingtonpost.com/politics/2023/08/03/congressional-scrutiny-microsoft-hack-picks-up-steam/">answers</a>. The phrase “<a href="https://arstechnica.com/security/2023/07/us-senator-blasts-microsoft-for-negligent-cybersecurity-practices/">negligent security practices</a>” is being tossed about—and with good reason. Master signing keys are not supposed to be left around, waiting to be stolen.</p>
<p>Actually, two things went badly wrong here. The first is that Azure accepted an expired signing key, implying a vulnerability in whatever is supposed to check key validity. The second is that this key was supposed to remain in the the system’s Hardware Security Module—and not be in software. This implies a really serious breach of good security practice. The fact that Microsoft has not been forthcoming about the details of what happened tell me that the details are really bad...</p>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Power LED Side-Channel Attack</title>
		<link>https://noise.getoto.net/2023/06/19/power-led-side-channel-attack/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Mon, 19 Jun 2023 10:52:19 +0000</pubDate>
				<category><![CDATA[cameras]]></category>
		<category><![CDATA[Cryptography]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[side-channel attacks]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=67462</guid>

					<description><![CDATA[<p>This is a clever new <a href="https://arstechnica.com/information-technology/2023/06/hackers-can-steal-cryptographic-keys-by-video-recording-connected-power-leds-60-feet-away/">side-channel attack</a>:</p>
<blockquote><p>The first attack uses an Internet-connected surveillance camera to take a high-speed video of the power LED on a smart card reader­—or of an attached peripheral device—­during cryptographic operations. This technique allowed the researchers to pull a 256-bit ECDSA key off the same government-approved smart card used in Minerva. The other allowed the researchers to recover the private SIKE key of a Samsung Galaxy S8 phone by training the camera of an iPhone 13 on the power LED of a USB speaker connected to the handset, in a similar way to how Hertzbleed pulled SIKE keys off Intel and AMD CPUs...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Leaked Signing Keys Are Being Used to Sign Malware</title>
		<link>https://noise.getoto.net/2022/12/08/leaked-signing-keys-are-being-used-to-sign-malware/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Thu, 08 Dec 2022 12:08:24 +0000</pubDate>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[leaks]]></category>
		<category><![CDATA[Malware]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=66316</guid>

					<description><![CDATA[<p>A bunch of Android OEM <a href="https://arstechnica.com/gadgets/2022/12/samsungs-android-app-signing-key-has-leaked-is-being-used-to-sign-malware/">signing keys</a> have been leaked or stolen, and they are actively being used to sign malware.</p>
<blockquote><p>Łukasz Siewierski, a member of Google’s Android Security Team, has a post on the Android Partner Vulnerability Initiative (AVPI) issue tracker detailing <a href="https://bugs.chromium.org/p/apvi/issues/detail?id=100">leaked platform certificate keys</a> that are actively being used to sign malware. The post is just a list of the keys, but running each one through <a href="https://www.apkmirror.com/">APKMirror</a> or Google’s <a href="https://www.virustotal.com/gui/home/upload">VirusTotal</a> site will put names to some of the compromised keys: <a href="https://www.apkmirror.com/?post_type=app_release&#38;searchtype=app&#38;sortby=date&#38;sort=desc&#38;s=34df0e7a9f1cf1892e45c056b4973cd81ccf148a4050d11aea4ac5a65f900a42">Samsung</a>, <a href="https://www.apkmirror.com/?post_type=app_release&#38;searchtype=app&#38;sortby=date&#38;sort=desc&#38;s=4274243d7a954ac6482866f0cc67ca1843ca94d68a0ee53f837d6740a8134421">LG</a>, and <a href="https://www.virustotal.com/gui/file/19c84a2386abde0c0dae8661b394e53bf246f6f0f9a12d84cfc7864e4a809697/details">Mediatek</a> are the heavy hitters on the list of leaked keys, along with some smaller OEMs like ...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Hacking Automobile Keyless Entry Systems</title>
		<link>https://noise.getoto.net/2022/10/17/hacking-automobile-keyless-entry-systems/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Mon, 17 Oct 2022 15:07:05 +0000</pubDate>
				<category><![CDATA[cars]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[law enforcement]]></category>
		<category><![CDATA[theft]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=65981</guid>

					<description><![CDATA[<p>Suspected members of a European car-theft ring have been <a href="https://www.europol.europa.eu/media-press/newsroom/news/31-arrested-for-stealing-cars-hacking-keyless-tech">arrested</a>:</p>
<blockquote><p>The criminals targeted vehicles with keyless entry and start systems, exploiting the technology to get into the car and drive away.</p>
<p>As a result of a coordinated action carried out on 10 October in the three countries involved, 31 suspects were arrested. A total of 22 locations were searched, and over EUR 1 098 500 in criminal assets seized.</p>
<p>The criminals targeted keyless vehicles from two French car manufacturers. A fraudulent tool—marketed as an automotive diagnostic solution, was used to replace the original software of the vehicles, allowing the doors to be opened and the ignition to be started without the actual key fob...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Relay Attack against Teslas</title>
		<link>https://noise.getoto.net/2022/09/15/relay-attack-against-teslas/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Thu, 15 Sep 2022 15:28:52 +0000</pubDate>
				<category><![CDATA[cars]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[vulnerabilities]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=65877</guid>

					<description><![CDATA[<p>Nice <a href="https://jalopnik.com/teslas-hackers-have-found-another-unauthorized-access-v-1849535920">work</a>:</p>
<blockquote><p>Radio relay attacks are technically complicated to execute, but conceptually easy to understand: attackers simply extend the range of your existing key using what is essentially a high-tech walkie-talkie. One thief stands near you while you’re in the grocery store, intercepting your key’s transmitted signal with a radio transceiver. Another stands near your car, with another transceiver, taking the signal from their friend and passing it on to the car. Since the car and the key can now talk, through the thieves’ range extenders, the car has no reason to suspect the key isn’t inside—and fires right up...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Hyundai Uses Example Keys for Encryption System</title>
		<link>https://noise.getoto.net/2022/08/22/hyundai-uses-example-keys-for-encryption-system/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Mon, 22 Aug 2022 11:38:30 +0000</pubDate>
				<category><![CDATA[aes]]></category>
		<category><![CDATA[cars]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=65794</guid>

					<description><![CDATA[<p>This is a <a href="https://www.theregister.com/2022/08/17/software_developer_cracks_hyundai_encryption/">dumb crypto mistake</a> I had not previously encountered:</p>
<blockquote><p>A developer says it was possible to run their own software on the car infotainment hardware after discovering the vehicle’s manufacturer had secured its system using keys that were not only publicly known but had been lifted from programming examples.</p>
<p>[…]</p>
<p>“Turns out the [AES] encryption key in that script is the first AES 128-bit CBC example key listed in the NIST document <a href="https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38a.pdf">SP800-38A</a> [PDF]”.</p>
<p>[…]</p>
<p>Luck held out, in a way. “Greenluigi1” found within the firmware image the RSA public key used by the updater, and searched online for a portion of that key. The search results pointed to a common public key that shows up in online tutorials like “...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>A Taxonomy of Access Control</title>
		<link>https://noise.getoto.net/2022/08/12/a-taxonomy-of-access-control/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Fri, 12 Aug 2022 11:38:10 +0000</pubDate>
				<category><![CDATA[cryptocurrency]]></category>
		<category><![CDATA[Cryptography]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[taxonomies]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=65764</guid>

					<description><![CDATA[<p>My personal definition of a brilliant idea is one that is immediately obvious once it’s explained, but no one has thought of it before. I can’t believe that no one has described this taxonomy of access control before Ittay Eyal laid it out in <a href="https://eprint.iacr.org/2021/1522.pdf">this</a> paper. The paper is about cryptocurrency wallet design, but the ideas are more general. Ittay points out that a key—or an account, or anything similar—can be in one of four states:</p>
<blockquote><p><b>safe</b> Only the user has access,<br>
<b>loss</b> No one has access,<br>
<b>leak</b> Both the user and the adversary have access, or<br>
<b>theft</b> Only the adversary has access...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Security Vulnerabilities in Honda’s Keyless Entry System</title>
		<link>https://noise.getoto.net/2022/07/12/security-vulnerabilities-in-hondas-keyless-entry-system/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Tue, 12 Jul 2022 12:23:24 +0000</pubDate>
				<category><![CDATA[cars]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[Locks]]></category>
		<category><![CDATA[reports]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=65653</guid>

					<description><![CDATA[<p>Honda vehicles from 2021 to 2022 are vulnerable to <a href="https://www.vice.com/en/article/z34xnw/hackers-say-they-can-unlock-and-start-honda-cars-remotely">this attack</a>:</p>
<blockquote><p>On Thursday, a security researcher who goes by Kevin2600 <a href="https://rollingpwn.github.io/rolling-pwn/">published a technical report</a> and videos on a vulnerability that he claims allows anyone armed with a simple hardware device to steal the code to unlock Honda vehicles. Kevin2600, who works for cybersecurity firm Star-V Lab, dubbed the attack RollingPWN.</p>
<p>[…]</p>
<p>In a phone call, Kevin2600 explained that the attack relies on a weakness that allows someone using a software defined radio—<a href="https://greatscottgadgets.com/hackrf/">such as HackRF</a>—to capture the code that the car owner uses to open the car, and then replay it so that the hacker can open the car as well. In some cases, he said, the attack can be performed from 30 meters (approximately 98 feet) away...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Hertzbleed: A New Side-Channel Attack</title>
		<link>https://noise.getoto.net/2022/06/20/hartzbleed-a-new-side-channel-attack/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Mon, 20 Jun 2022 11:23:53 +0000</pubDate>
				<category><![CDATA[Cryptography]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[side-channel attacks]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=65567</guid>

					<description><![CDATA[<p>Hertzbleed is a new side-channel attack that works against a variety of microprocressors. Deducing cryptographic keys by analyzing power consumption has long been an attack, but it’s not generally viable because measuring power consumption is often hard. This <a href="https://arstechnica.com/information-technology/2022/06/researchers-exploit-new-intel-and-amd-cpu-flaw-to-steal-encryption-keys/">new attack</a> measures power consumption by measuring time, making it easier to exploit.</p>
<blockquote><p>The team discovered that dynamic voltage and frequency scaling (DVFS)—a power and thermal management feature added to every modern CPU—allows attackers to deduce the changes in power consumption by monitoring the time it takes for a server to respond to specific carefully made queries. The discovery greatly reduces what’s required. With an understanding of how the DVFS feature works, power side-channel attacks become much simpler timing attacks that can be done remotely...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Hacking Tesla’s Remote Key Cards</title>
		<link>https://noise.getoto.net/2022/06/14/hacking-teslas-remote-key-cards/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Tue, 14 Jun 2022 12:19:10 +0000</pubDate>
				<category><![CDATA[cars]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[vulnerabilities]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=65513</guid>

					<description><![CDATA[<p>Interesting <a href="https://arstechnica.com/information-technology/2022/06/hackers-out-to-steal-a-tesla-can-create-their-very-own-personal-key/">vulnerability</a> in Tesla’s NFC key cards:</p>
<blockquote><p>Martin Herfurt, a security researcher in Austria, quickly noticed something odd about the new feature: Not only did it allow the car to automatically start within 130 seconds of being unlocked with the NFC card, but it also put the car in a state to accept entirely new keys—with no authentication required and zero indication given by the in-car display.</p>
<p>“The authorization given in the 130-second interval is too general… [it’s] not only for drive,” Herfurt said in an online interview. “This timer has been introduced by Tesla…in order to make the use of the NFC card as a primary means of using the car more convenient. What should happen is that the car can be started and driven without the user having to use the key card a second time. The problem: within the 130-second period, not only the driving of the car is authorized, but also the [enrolling] of a new key.”...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Breaking RSA through Insufficiently Random Primes</title>
		<link>https://noise.getoto.net/2022/03/16/breaking-rsa-through-insufficiently-random-primes/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Wed, 16 Mar 2022 16:35:57 +0000</pubDate>
				<category><![CDATA[cryptanalysis]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[pgp]]></category>
		<category><![CDATA[random numbers]]></category>
		<category><![CDATA[rsa]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=65230</guid>

					<description><![CDATA[<p>Basically, the SafeZone library <a href="https://arstechnica.com/information-technology/2022/03/researcher-uses-600-year-old-algorithm-to-crack-crypto-keys-found-in-the-wild/">doesn’t sufficiently randomize</a> the two prime numbers it used to generate RSA keys. They’re too close to each other, which makes them vulnerable to recovery.</p>
<p>There aren’t many weak keys out there, but there are some:</p>
<blockquote><p>So far, Böck has identified only a handful of keys in the wild that are vulnerable to the factorization attack. Some of the keys are from printers from two manufacturers, Canon and Fujifilm (originally branded as Fuji Xerox). Printer users can use the keys to generate a Certificate Signing Request. The creation date for the all the weak keys was 2020 or later. The weak Canon keys are tracked as CVE-2022-26351...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>DiceKeys</title>
		<link>https://noise.getoto.net/2020/08/24/dicekeys/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Mon, 24 Aug 2020 11:23:40 +0000</pubDate>
				<category><![CDATA[Cryptography]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[passwords]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=30052491fce6ac68980e2bc3a3ffc85d</guid>

					<description><![CDATA[DiceKeys is a physical mechanism for creating and storing a 192-bit key. The idea is that you roll a special set of twenty-five dice, put them into a plastic jig, and then use an app to convert those dice into a key. You can then use that key for a variety of purposes, and regenerate it from the dice if...]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/

Object Caching 33/327 objects using Memcached
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Memcached

Served from: noise.getoto.net @ 2025-12-06 04:00:31 by W3 Total Cache
-->