OpenPKG CVS Repository
  http://cvs.openpkg.org/
  ____________________________________________________________________________

  Server: cvs.openpkg.org                  Name:   Thomas Lotterer
  Root:   /e/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-re                       Date:   19-Apr-2004 09:52:56
  Branch: HEAD                             Handle: 2004041908525600

  Modified files:
    openpkg-re              news.txt

  Log:
    flush typofixing and improved explanation around UUIDs

  Summary:
    Revision    Changes     Path
    1.42        +19 -15     openpkg-re/news.txt
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-re/news.txt
  ============================================================================
  $ cvs diff -u -r1.41 -r1.42 news.txt
  --- openpkg-re/news.txt       23 Mar 2004 15:56:34 -0000      1.41
  +++ openpkg-re/news.txt       19 Apr 2004 07:52:56 -0000      1.42
  @@ -2,7 +2,7 @@
     General Note
     ============
   
  -  o $Revision: 1.41 $. The most recent update of this file can be
  +  o $Revision: 1.42 $. The most recent update of this file can be
       downloaded from http://cvs.openpkg.org/openpkg-re/news.txt
   
     o This file news.txt file talks about new features and major
  @@ -198,10 +198,11 @@
       multicast address, as descibed below.
   
       UUID_INSTANCE is based on instance related information like prefix
  -    and user ids. All installations having exactly the same paramters
  +    and user ids. All installations having exactly the same parameters
       will have the same UUID. This ID is updated during installation,
       on every system startup (rc.openpkg %start) and daily (rc.openpkg
  -    %daily). Can be used to detect if a 
  +    %daily). Can be used to identify groups of instance twins across
  +    hosts.
   
       UUID_PLATFORM is based on host name and network information. All
       installations having exactly the same paramters will have the same
  @@ -214,7 +215,7 @@
       
       - which data is used to create the UUID
       - where it is send to
  -    - how much information can be recovered by the recipient
  +    - how much privacy is exposed to the recipient
   
       We provide a way for the user to reproduce how the UUIDs are
       generated. Full transparency here.
  @@ -231,8 +232,13 @@
   
       The UUID needs of OpenPKG triggered the creation of OSSP uuid which
       is included in the bootstrap. To reproduce how the UUIDs were
  -    generated and to see which information can be decoded. The user
  -    might run one of two alternatives:
  +    generated and to see which information is used to create the input
  +    based UUIDs the user might run one of two alternative commands
  +    listed below. It should be pointed out that the algorithm to create
  +    a UUID from input is a message digest (MD5) function which inhibits
  +    extraction of the original information from the UUID. The most
  +    sophisticated application of a message digest is to use it for
  +    equal/not equal comparison with another UUID.
   
       $ %{l_prefix}/etc/rc openpkg info
       $ %{l_prefix}/bin/openpkg uuid info
  @@ -267,15 +273,13 @@
           UUID_PLATFORM:         61a4580d-b45c-388f-a9b9-9887780a8b2d
   
       It should be pointed out that time based UUID Registry can never be
  -    reproduced completely. That's what UUIDs were invented for. However,
  -    you can manually reset to zero and update with multicast to hide the
  -    node address. This change is visible. The input based UUIDs Instance
  -    and Platform can be reproduced completely. However, the algorithm to
  -    create a UUID from input is a message digest (MD5) function which
  -    does not allow to extract the original information from the UUID. At
  -    best it can be used to compare with another UUID created with known
  -    input. More details can be learned by running the following UUID
  -    related commands with the --verbose option.
  +    reproduced completely. That's what UUIDs were originally invented
  +    for and works as designed. It is possible to reset it to zero and
  +    update with multicast to hide the node address. The input based
  +    UUIDs Instance and Platform can be reproduced completely. More
  +    details regarding extraction of information can be learned by
  +    running the following UUID related commands with the --verbose
  +    option.
   
       - reset UUID by zeroing out data. Useful before update or to prepare
         a machine before cloning the hard disk drive.
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [EMAIL PROTECTED]

Reply via email to