Go to file
2008-05-22 11:40:31 -04:00
contrib/RHEL4 Become version 1.0.0 2008-04-16 14:29:17 -07:00
ipa-admintools Catch name resolution errors coming from the socket module. 2008-05-13 12:00:21 -04:00
ipa-client Change file mode of log files to 600. 2008-05-20 22:43:03 -04:00
ipa-python Enforce the maximum username length set by IPA Policy 2008-05-14 09:48:21 -04:00
ipa-radius-admintools Second half of the redoing how the version is managed. 2008-05-07 18:26:03 -04:00
ipa-radius-server Second half of the redoing how the version is managed. 2008-05-07 18:26:03 -04:00
ipa-server Only ask the user to install bind. 2008-05-22 11:40:31 -04:00
.hgtags Added tag milestone_6 for changeset 84bc1acacd93 0001-01-01 00:00:00 +00:00
LICENSE Add a copy of the LICENSE and populate some README's 2008-01-23 10:30:18 -05:00
Makefile Convert mercurial command to git equivalent for creating an archive. 2008-05-09 11:09:49 -04:00
README Add a copy of the LICENSE and populate some README's 2008-01-23 10:30:18 -05:00
VERSION Redo the way versioning works in freeIPA. 2008-05-05 13:53:57 -04:00

                               IPA Server

  What is it?
  -----------

  For efficiency, compliance and risk mitigation, organizations need to
  centrally manage and correlate vital security information including:

    * Identity (machine, user, virtual machines, groups, authentication
      credentials)
    * Policy (configuration settings, access control information)
    * Audit (events, logs, analysis thereof) 

  Since these are not new problems. there exist many approaches and
  products focused on addressing them. However, these tend to have the
  following weaknesses:

    * Focus on solving identity management across the enterprise has meant
      less focus on policy and audit.
    * Vendor focus on Web identity management problems has meant less well
      developed solutions for central management of the Linux and Unix
      world's vital security info. Organizations are forced to maintain
      a hodgepodge of internal and proprietary solutions at high TCO.
    * Proprietary security products don't easily provide access to the
      vital security information they collect or manage. This makes it
      difficult to synchronize and analyze effectively. 

  The Latest Version
  ------------------

  Details of the latest version can be found on the IPA server project
  page under <http://www.freeipa.org/>.

  Documentation
  -------------

  The most up-to-date documentation can be found at
  <http://freeipa.org/page/Documentation/>.

  Licensing
  ---------

  Please see the file called LICENSE.

  Contacts
  --------

     * If you want to be informed about new code releases, bug fixes,
       security fixes, general news and information about the IPA server
       subscribe to the freeipa-announce mailing list at
       <https://www.redhat.com/mailman/listinfo/freeipa-interest/>.

     * If you have a bug report please submit it at:
       <https://bugzilla.redhat.com>

     * If you want to participate in actively developing IPA please
       subscribe to the freeipa-devel mailing list at
       <https://www.redhat.com/mailman/listinfo/freeipa-devel/> or join
       us in IRC at irc://irc.freenode.net/freeipa