<?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>random numbers &#8211; Noise</title>
	<atom:link href="https://noise.getoto.net/tag/random-numbers/feed/" rel="self" type="application/rss+xml" />
	<link>https://noise.getoto.net</link>
	<description>The collective thoughts of the interwebz</description>
	<lastBuildDate>Tue, 10 Oct 2023 21:54:09 +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>Coin Flips Are Biased</title>
		<link>https://noise.getoto.net/2023/10/16/coin-flips-are-biased/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Mon, 16 Oct 2023 11:06:00 +0000</pubDate>
				<category><![CDATA[academic papers]]></category>
		<category><![CDATA[gambling]]></category>
		<category><![CDATA[random numbers]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=67939</guid>

					<description><![CDATA[<p>Experimental <a href="https://arxiv.org/abs/2310.04153">result</a>:</p>
<blockquote><p>Many people have flipped coins but few have stopped to ponder the statistical and physical intricacies of the process. In a preregistered study we collected 350,757 coin flips to test the counterintuitive prediction from a physics model of human coin tossing developed by Persi Diaconis. The model asserts that when people flip an ordinary coin, it tends to land on the same side it started—Diaconis estimated the probability of a same-side outcome to be about 51%.</p></blockquote>
<p>And the final paragraph:</p>
<blockquote><p>Could future coin tossers use the same-side bias to their advantage? The magnitude of the observed bias can be illustrated using a betting scenario. If you bet a dollar on the outcome of a coin toss (i.e., paying 1 dollar to enter, and winning either 0 or 2 dollars depending on the outcome) and repeat the bet 1,000 times, knowing the starting position of the coin toss would earn you 19 dollars on average. This is more than the casino advantage for 6 deck blackjack against an optimal-strategy player, where the casino would make 5 dollars on a comparable bet, but less than the casino advantage for single-zero roulette, where the casino would make 27 dollars on average. These considerations lead us to suggest that when coin flips are used for high-stakes decision-making, the starting position of the coin is best concealed...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Bounty to Recover NIST’s Elliptic Curve Seeds</title>
		<link>https://noise.getoto.net/2023/10/12/bounty-to-recover-nists-elliptic-curve-seeds/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Thu, 12 Oct 2023 11:09:38 +0000</pubDate>
				<category><![CDATA[backdoors]]></category>
		<category><![CDATA[contests]]></category>
		<category><![CDATA[Cryptography]]></category>
		<category><![CDATA[nist]]></category>
		<category><![CDATA[random numbers]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=67930</guid>

					<description><![CDATA[<p><a href="https://words.filippo.io/dispatches/seeds-bounty/">This</a> is a fun challenge:</p>
<blockquote><p>The NIST elliptic curves that power much of modern cryptography were generated in the late ’90s by hashing seeds provided by the NSA. How were the seeds generated? Rumor has it that they are in turn hashes of English sentences, but the person who picked them, Dr. Jerry Solinas, passed away in early 2023 leaving behind a cryptographic mystery, some conspiracy theories, and an historical password cracking challenge.</p></blockquote>
<p>So there’s a $12K prize to recover the hash seeds.</p>
<p>Some <a href="https://news.ycombinator.com/item?id=37784499">backstory</a>:</p>
<blockquote><p>Some of the backstory here (it’s the funniest fucking backstory ever): it’s lately been circulating—though I think this may have been somewhat common knowledge among practitioners, though definitely not to me—that the “random” seeds for the NIST P-curves, generated in the 1990s by Jerry Solinas at NSA, were simply SHA1 hashes of some variation of the string “Give Jerry a raise”...</p></blockquote>]]></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>On the Randomness of Automatic Card Shufflers</title>
		<link>https://noise.getoto.net/2022/10/24/on-the-randomness-of-automatic-card-shufflers/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Mon, 24 Oct 2022 11:37:55 +0000</pubDate>
				<category><![CDATA[gambling]]></category>
		<category><![CDATA[loopholes]]></category>
		<category><![CDATA[random numbers]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=65996</guid>

					<description><![CDATA[<p>Many years ago, Matt Blaze and I talked about getting our hands on a casino-grade automatic shuffler and looking for vulnerabilities. We never did it—I remember that we didn’t even try very hard—but <a href="https://www.bbc.com/future/article/20221019-how-a-magician-mathematician-revealed-a-casino-loophole">this article</a> shows that we probably would have found non-random properties:</p>
<blockquote><p>…the executives had recently discovered that one of their machines had been hacked by a gang of hustlers. The gang used a hidden video camera to record the workings of the card shuffler through a glass window. The images, transmitted to an accomplice outside in the casino parking lot, were played back in slow motion to figure out the sequence of cards in the deck, which was then communicated back to the gamblers inside. The casino lost millions of dollars before the gang were finally caught...</p></blockquote>]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Linux Improves Its Random Number Generator</title>
		<link>https://noise.getoto.net/2022/03/24/linux-improves-its-random-number-generator/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Thu, 24 Mar 2022 11:38:47 +0000</pubDate>
				<category><![CDATA[linux]]></category>
		<category><![CDATA[random numbers]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=65268</guid>

					<description><![CDATA[In kernel version 5.17, both /dev/random and /dev/urandom have been replaced with a new &#8212; identical &#8212; algorithm based on the BLAKE2 hash function, which is an excellent security improvement.
]]></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>More Detail on the Juniper Hack and the NSA PRNG Backdoor</title>
		<link>https://noise.getoto.net/2021/09/09/more-detail-on-the-juniper-hack-and-the-nsa-prng-backdoor/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Thu, 09 Sep 2021 11:13:10 +0000</pubDate>
				<category><![CDATA[backdoors]]></category>
		<category><![CDATA[china]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[Juniper]]></category>
		<category><![CDATA[NSA]]></category>
		<category><![CDATA[random numbers]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=63652</guid>

					<description><![CDATA[We knew the basics of this story, but it&#8217;s good to have more detail.
Here&#8217;s me in 2015 about this Juniper hack. Here&#8217;s me in 2007 on the NSA backdoor.
]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Vulnerability in the Kaspersky Password Manager</title>
		<link>https://noise.getoto.net/2021/07/06/vulnerability-in-the-kaspersky-password-manager/</link>
		
		<dc:creator><![CDATA[Bruce Schneier]]></dc:creator>
		<pubDate>Tue, 06 Jul 2021 14:27:47 +0000</pubDate>
				<category><![CDATA[Password Safe]]></category>
		<category><![CDATA[passwords]]></category>
		<category><![CDATA[random numbers]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[vulnerabilities]]></category>
		<guid isPermaLink="false">https://www.schneier.com/?p=63427</guid>

					<description><![CDATA[<p>A vulnerability (just patched) in the random number generator used in the Kaspersky Password Manager resulted in <a href="https://donjon.ledger.com/kaspersky-password-manager/">easily guessable</a> passwords:</p>
<blockquote><p>The password generator included in Kaspersky Password Manager had several problems. The most critical one is that it used a PRNG not suited for cryptographic purposes. Its single source of entropy was the current time. All the passwords it created could be bruteforced in seconds. This article explains how to securely generate passwords, why Kaspersky Password Manager failed, and how to exploit this flaw. It also provides a proof of concept to test if your version is vulnerable...</p></blockquote>]]></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 36/146 objects using Memcached
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Memcached

Served from: noise.getoto.net @ 2025-12-13 21:24:25 by W3 Total Cache
-->