freeipa/ipa-client
Jakub Hrozek 7493d781df Change FreeIPA license to GPLv3+
The changes include:
 * Change license blobs in source files to mention GPLv3+ not GPLv2 only
 * Add GPLv3+ license text
 * Package COPYING not LICENSE as the license blobs (even the old ones)
   mention COPYING specifically, it is also more common, I think

 https://fedorahosted.org/freeipa/ticket/239
2010-12-20 17:19:53 -05:00
..
firefox Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
ipa-install Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
ipaclient Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
man Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
AUTHORS Fix build from autoconf patch import. 0001-01-01 00:00:00 +00:00
config.c Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
configure.ac build tweaks - use automake's foreign mode, avoid creating empty files to satisfy gnu mode - run autoreconf -f to ensure that everything matches 2010-11-29 11:39:55 -05:00
ipa-client-common.c Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
ipa-client-common.h Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
ipa-client.spec.in Fix versioning for configure.ac and ipa-python/setup.py 2008-08-11 18:31:05 -04:00
ipa-getkeytab.c Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
ipa-join.c Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
ipa-rmkeytab.c Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
Makefile.am ipa-client code cleanup 2010-11-22 16:01:35 -05:00
NEWS Fix build from autoconf patch import. 0001-01-01 00:00:00 +00:00
README Add a copy of the LICENSE and populate some README's 2008-01-23 10:30:18 -05:00
version.m4.in Fix versioning for configure.ac and ipa-python/setup.py 2008-08-11 18:31:05 -04:00

Code to be installed on any client that wants to be in an IPA domain.

Mostly consists of a tool for Linux systems that will help configure the
client so it will work properly in a kerberized environment.

It also includes several ways to configure Firefox to do single sign-on.

The two methods on the client side are:

1. globalsetup.sh. This modifies the global Firefox installation so that
   any profiles created will be pre-configured.

2. usersetup.sh. This will update a user's existing profile.

The downside of #1 is that an rpm -V will return a failure. It will also
need to be run with every update of Firefox.

One a profile contains the proper preferences it will be unaffected by
upgrades to Firefox. 

The downside of #2 is that every user would need to run this each time they
create a new profile.

There is a third, server-side method. See ipa-server/README for details.