anchor.diff:  which is also required by modern 64 bit Windows distributions.
   
   Deploying this driver would normally be done using the LoadMemoryDriver flow.
  +
  +
  +Building a Linux memory driver
  +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  +
  +Determine the kernel version of the system the GRR client is running on e.g.
  +----
  +3.13.0-49-generic
  +----
  +
  +Find a reprentative build machine e.g. Ubuntu and install the corresponding
  +kernel headesr:
  +----
  +sudo apt-get install linux-headers-3.13.0-49-generic
  +----
  +
  +Clone rekall and traverse into the linux driver source directory:
  +----
  +git clone https://github.com/google/rekall.git
  +cd rekall/tools/linux
  +----
  +
  +edit Makefile and set KVER to the kernel version
  +----
  +KVER ?= "3.13.0-49-generic
  +----
  +
  +Build the pmem driver:
  +----
  +make pmem
  +----
  +
  +Deploy pmem.ko as a driver.
   
   
   Deploying Executables.
  
positive.code: -------------------------
  
  Get a GRR server installed and running in a few minutes with the
  link:quickstart.adoc[quickstart install].  With more effort you can also
  link:installfromsource.adoc[install from source].
  
  Key Management
  
negative.code: Authentication to the Admin UI.
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  The AdminUI uses basic authentication by default, based on the passwords within
  the user objects stored in the data store, but we _don't expect you to use this
  in production_. There is so much diversity and customization in enterprise
  authentication shemes that there isn't a good way to provide a solution that
  works for a majority of users. But you probably already have internal webapps
  that use authentication, this is just one more. Most people have found the
  easiest approach is to sit Apache (or similar) in front of the GRR Admin UI as
  a reverse proxy and use an existing SSO plugin that already works for that
  platform. Alternatively, with more work you can handle auth inside GRR by
  writing a Webauth Manager (AdminUI.webauth_manager config option) that uses an
  SSO or SAML based authentication mechanism.
  
  
  Security Considerations
  