freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-26 17:01:14 -06:00

History

Rob Crittenden b49942fe96 Close all fds when running another program. This fixes the SELinux AVCs. Put installation log files into /var/log. 430024		2008-03-03 16:14:48 -05:00
..
firefox	Set the license uniformly to GPLv2 only.	2008-02-04 15:15:52 -05:00
ipa-install	Close all fds when running another program. This fixes the SELinux AVCs.	2008-03-03 16:14:48 -05:00
ipaclient	Set the license uniformly to GPLv2 only.	2008-02-04 15:15:52 -05:00
man	Compress man pages after installation	2008-02-25 16:34:00 -05:00
.hgignore	Autotool ipa-client - patch from William Jon McCann <mccann@jhu.edu>	0001-01-01 00:00:00 +00:00
AUTHORS	Fix build from autoconf patch import.	0001-01-01 00:00:00 +00:00
autogen.sh	Correct PACKAGE in ipa-client/autogen.sh.	0001-01-01 00:00:00 +00:00
configure.ac	Move ipa-getkeytab man page into proper subdir	2008-02-25 14:56:09 -05:00
ipa-client.spec	Move ipa-getkeytab man page into proper subdir	2008-02-25 14:56:09 -05:00
ipa-client.spec.in	Move ipa-getkeytab man page into proper subdir	2008-02-25 14:56:09 -05:00
ipa-getkeytab.c	Add switch to be able to provide a comma separate list of encryption types	2008-02-06 19:01:22 -05:00
Makefile.am	Move ipa-getkeytab man page into proper subdir	2008-02-25 14:56:09 -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

README

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.