freeipa.git - FreeIPA project

	Commit message (Collapse)	Author	Age	Files	Lines
*	Change FreeIPA license to GPLv3+	Jakub Hrozek	2010-12-20	1	-5/+5
\| \| \| \| \| \| \| \| \| \|	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
*	Use Realm as certs subject base name	Simo Sorce	2010-11-18	1	-2/+3
\| \| \| \|	Also use the realm name as nickname for the CA certificate
*	Use consistent, specific nickname for the IPA CA certificate.	Rob Crittenden	2010-10-01	1	-1/+2
\| \| \| \| \| \|	Also fix some imports for sha. We have a compat module for it, use it. ticket 181
*	Drop our own PKCS#10 ASN.1 decoder and use the one from python-nss	Rob Crittenden	2010-07-29	1	-17/+11
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This patch: - bumps up the minimum version of python-nss - will initialize NSS with nodb if a CSR is loaded and it isn't already init'd - will shutdown NSS if initialized in the RPC subsystem so we use right db - updated and added a few more tests Relying more on NSS introduces a bit of a problem. For NSS to work you need to have initialized a database (either a real one or no_db). But once you've initialized one and want to use another you have to close down the first one. I've added some code to nsslib.py to do just that. This could potentially have some bad side-effects at some point, it works ok now.
*	Use newer API in ipalib/x509 and add missing import.	Rob Crittenden	2010-07-15	1	-6/+1
\| \| \| \|	The import was only used when running the in-tree lite-server
*	localize doc strings	John Dennis	2010-03-08	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \|	A number of doc strings were not localized, wrap them in _(). Some messages were not localized, wrap them in _() Fix a couple of failing tests: The method name in RPC should not be unicode. The doc attribute must use the .msg attribute for comparison. Also clean up imports of _() The import should come from ipalib or ipalib.text, not ugettext from request.
*	fix error message to be i18n translator friendly	John Dennis	2010-02-03	1	-1/+2
\| \| \| \| \| \| \| \|	This error message was producing a warning from xgettext because there were multiple substations in the string. In some languages it may be necessary to reorder the substitutions for a proper translation, this is only possible if the substitutions use named values.
*	Be more careful when base64-decoding certificates	Rob Crittenden	2010-02-02	1	-1/+0
\| \| \| \| \|	Only decode certs that have a BEGIN/END block, otherwise assume it is in DER format.
*	User-defined certificate subjects	Rob Crittenden	2010-01-20	1	-1/+28
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Let the user, upon installation, set the certificate subject base for the dogtag CA. Certificate requests will automatically be given this subject base, regardless of what is in the CSR. The selfsign plugin does not currently support this dynamic name re-assignment and will reject any incoming requests that don't conform to the subject base. The certificate subject base is stored in cn=ipaconfig but it does NOT dynamically update the configuration, for dogtag at least. The file /var/lib/pki-ca/profiles/ca/caIPAserviceCert.cfg would need to be updated and pki-cad restarted.
*	rebase dogtag clean-up patch	John Dennis	2009-12-09	1	-13/+89
\|
*	Use pyasn1-based PKCS#10 and X509v3 parsers instead of pyOpenSSL.	Rob Crittenden	2009-11-30	1	-5/+14
\| \| \| \| \| \| \| \| \|	The pyOpenSSL PKCS#10 parser doesn't support attributes so we can't identify requests with subject alt names. Subject alt names are only allowed if: - the host for the alt name exists in IPA - if binding as host principal, the host is in the services managedBy attr
*	Use the same variable name in the response as the dogtag plugin	Rob Crittenden	2009-09-24	1	-1/+1
\|
*	Add external CA signing and abstract out the RA backend	Rob Crittenden	2009-09-15	1	-0/+126
	External CA signing is a 2-step process. You first have to run the IPA installer which will generate a CSR. You pass this CSR to your external CA and get back a cert. You then pass this cert and the CA cert and re-run the installer. The CSR is always written to /root/ipa.csr. A run would look like: # ipa-server-install --ca --external-ca -p password -a password -r EXAMPLE.COM -u dirsrv -n example.com --hostname=ipa.example.com -U [ sign cert request ] # ipa-server-install --ca --external-ca -p password -a password --external_cert_file=/tmp/rob.crt --external_ca_file=/tmp/cacert.crt -U -p password -a password -r EXAMPLE.COM -u dirsrv -n example.com --hostname=ipa.example.com This also abstracts out the RA backend plugin so the self-signed CA we create can be used in a running server. This means that the cert plugin can request certs (and nothing else). This should let us do online replica creation. To handle the self-signed CA the simple ca_serialno file now contains additional data so we don't have overlapping serial numbers in replicas. This isn't used yet. Currently the cert plugin will not work on self-signed replicas. One very important change for self-signed CAs is that the CA is no longer held in the DS database. It is now in the Apache database. Lots of general fixes were also made in ipaserver.install.certs including: - better handling when multiple CA certificates are in a single file - A temporary directory for request certs is not always created when the class is instantiated (you have to call setup_cert_request())