open-src/xserver/xvnc/vncserver-urandom.patch
changeset 851 d428083dbbdd
parent 822 2a89ea3c59be
--- a/open-src/xserver/xvnc/vncserver-urandom.patch	Wed Dec 02 21:38:00 2009 -0800
+++ b/open-src/xserver/xvnc/vncserver-urandom.patch	Sat Dec 05 22:13:03 2009 -0800
@@ -1,6 +1,20 @@
---- unix/vncserver	2009-11-05 20:00:59.601018622 -0800
-+++ unix/vncserver	2009-11-05 20:16:46.059095655 -0800
-@@ -196,16 +196,25 @@
+From 8df3a7a2c49db4509aedd5f3cf1e3340cd9d7b82 Mon Sep 17 00:00:00 2001
+From: Alan Coopersmith <[email protected]>
+Date: Fri, 6 Nov 2009 16:36:45 -0800
+Subject: [PATCH] Use /dev/urandom for xauth cookie generation
+
+The previous comment about only Linux having it is a bit outdated,
+it's common on most modern Unix-like systems now, and we can easily
+fall back to the old method on systems without it.
+---
+ unix/vncserver |   25 +++++++++++++++++--------
+ 1 files changed, 17 insertions(+), 8 deletions(-)
+
+diff --git a/unix/vncserver b/unix/vncserver
+index 90ef0d2..28764cb 100755
+--- a/unix/vncserver
++++ b/unix/vncserver
+@@ -189,16 +189,25 @@ $vncPort = 5900 + $displayNumber;
  $desktopLog = "$vncUserDir/$host:$displayNumber.log";
  unlink($desktopLog);
  
@@ -34,3 +48,6 @@
  system("xauth -f $xauthorityFile add $host:$displayNumber . $cookie");
  system("xauth -f $xauthorityFile add $host/unix:$displayNumber . $cookie"); 
  
+-- 
+1.5.6.5
+