freeipa

0 Fork 0

Files

T

Rob Crittenden e3820682c7 Try to resolve the name passed into the password reader to a file

Rather than comparing the value passed in by Apache to a
hostname value just see if there is a file of that name in
/var/lib/ipa/passwds.

Use realpath to see if path information was passed in as one of
the options so that someone can't try to return random files from
the filesystem.

https://pagure.io/freeipa/issue/7528

Signed-off-by: Rob Crittenden <rcritten@redhat.com>
Reviewed-By: Alexander Bokovoy <abokovoy@redhat.com>

2018-09-19 11:42:49 -04:00

certmonger

Generate scripts from templates

2018-08-23 14:49:06 +02:00

html

Fix translation of "ssbrowser.html" Web page

2018-09-12 10:44:37 +02:00

migration

Clean up migration "error" and "invalid" pages from project

2018-08-27 17:10:32 +02:00

oddjob

Generate scripts from templates

2018-08-23 14:49:06 +02:00

restart_scripts

Generate scripts from templates

2018-08-23 14:49:06 +02:00

Disable authentication to endpoint for serving i18n requests

2018-07-17 15:32:28 -04:00

tools

Try to resolve the name passed into the password reader to a file

2018-09-19 11:42:49 -04:00

Add title to remove dialog of 'Trusts' entity

2018-09-18 13:51:51 +02:00

updates

Use replace instead of add to set new default ipaSELinuxUserMapOrder

2018-06-08 10:49:18 +02:00

wsgi

Add absolute_import future imports

2018-04-20 09:43:37 +02:00

Makefile.am

Encrypt httpd key stored on disk

2018-03-23 12:48:46 +01:00

README.schema

Add some basic rules for adding new schema

2010-08-27 13:40:37 -04:00

README.schema

Ground rules on adding new schema

Brand new schema, particularly when written specifically for IPA, should be
added in share/*.ldif. Any new files need to be explicitly loaded in
ipaserver/install/dsinstance.py. These simply get copied directly into
the new instance schema directory.

Existing schema (e.g. in an LDAP draft) may either be added as a separate
ldif in share or as an update in the updates directory. The advantage of
adding the schema as an update is if 389-ds ever adds the schema then the
installation won't fail due to existing schema failing to load during
bootstrap.

If the new schema requires a new container then this should be added
to install/bootstrap-template.ldif.