From: Mike Brady <mikebrady@eircom.net>
Date: Sat, 3 Nov 2018 12:54:58 +0000 (+0000)
Subject: Update RELEASENOTES.md
X-Git-Tag: 3.3RC0~182
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=48ab075a1348d3fe47a92f3a134fefbe6acfd282;p=thirdparty%2Fshairport-sync.git

Update RELEASENOTES.md
---

diff --git a/RELEASENOTES.md b/RELEASENOTES.md
index 23d26aab..927b7f65 100644
--- a/RELEASENOTES.md
+++ b/RELEASENOTES.md
@@ -1,4 +1,9 @@
 
+Version 3.3d21
+====
+**Enhancements**
+* Use `/dev/urandom` rather than `/dev/random` as a source of some kind of randomness for the crtptographic nonce used in AirPlay password exchange, as `/dev/random` blocks occasionally. Please see [here](https://unix.stackexchange.com/questions/324209/when-to-use-dev-random-vs-dev-urandom) for a discussion of the merits of both. The effect of `/dev/random`'s blocking on Shairport Sync was to make the source of randomness somewhat less random. (By the way, you should never use an important password as an AirPlay password for Shairport Sync -- it is stored in Shairport Sync's configuration file in plain text.)
+
 Version 3.3d20
 ====
 **Enhancements**