[popfile-commit] engine/POPFile Configuration.pm,1.61,1.62

[Manni H. <man...@us...>]

Update of /cvsroot/popfile/engine/POPFile
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23155/POPFile

Modified Files:
	Configuration.pm 
Log Message:
Add two global configuration variables, crypt_strength and crypt_device, and use them in calls to Crypt::Random::makerandom_octet.

They default to 0 and '', respectively.

Advanced users can set crypt_strength to 1, but the average user should be happier with 0. The super-advanced user can even specify his own random device.

Index: Configuration.pm
===================================================================
RCS file: /cvsroot/popfile/engine/POPFile/Configuration.pm,v
retrieving revision 1.61
retrieving revision 1.62
diff -C2 -d -r1.61 -r1.62
*** Configuration.pm	3 Sep 2007 12:42:59 -0000	1.61
--- Configuration.pm	2 Dec 2007 17:27:47 -0000	1.62
***************
*** 125,128 ****
--- 125,144 ----
      $self->global_config_( 'single_user', 1 );
  
+     # The Strength value used in calls to Crypt::Random::makerandom_octet
+     # The default is weak (0), but should work on all systems without
+     # blocking POPFile. Set this to 1 if your syste provides enough
+     # entropy and you need extra-random randomness.
+ 
+     $self->global_config_( 'crypt_strength', 0 );
+ 
+     # The random number device that should be used in calls to
+     # Crypt::Random::makerandom_octet. Depending on the Strength
+     # value Crypt::Random uses either /dev/random (Strength 1)
+     # or /dev/urandom (Strength 0). If you have another
+     # device that can produce random numbers, you can configure
+     # it with this variable.
+ 
+     $self->global_config_( 'crypt_device', '' );
+ 
      # Register for the TICKD message which is sent hourly by the
      # Logger module.   We use this to hourly save the configuration file