FreeIPA-devel May 2018

freeipa-devel@lists.fedorahosted.org

10 participants
147 discussions

[freeipa PR#1606][opened] Uninstalling IPA requires on being in a existent working directory
by amitkumar50 02 May '18

02 May '18

URL: https://github.com/freeipa/freeipa/pull/1606 Author: amitkumar50 Title: #1606: Uninstalling IPA requires on being in a existent working directory Action: opened PR body: """ Presently freeipa tests current working directory with os.getcwd() which throws exception when called on non-existant directory. Solution can be to call os.chdir("/root") and set self.cwd variable accordingly. Tests done: //console-1 `# mkdir test-delete` `# cd test-delete` `# rm -rf /root/test-delete //From console-2` `# ipa-server-install --uninstall` ..successful.. `# cd /root` `# ipa-server-install` ..successful.. Still need to address installation of ipa-server from deleted dir. Can handle in seperate PR. Resolves: https://pagure.io/freeipa/issue/7416 """ To pull the PR as Git branch: git remote add ghfreeipa https://github.com/freeipa/freeipa git fetch ghfreeipa pull/1606/head:pr1606 git checkout pr1606

2 3

[freeipa PR#1897][opened] Use temporary pid file for chronyd -q task
by Tiboris 02 May '18

02 May '18

URL: https://github.com/freeipa/freeipa/pull/1897 Author: Tiboris Title: #1897: Use temporary pid file for chronyd -q task Action: opened PR body: """ chrony is causing an SELinux denial because of chronyd was not spawned using systemd and the command creates a pidfile for unconfined proccess in /var/run with SELinux label: `unconfined_u:object_r:var_run_t:s0` Following chronyd daemon enablement with systemd will fail due to mismatched SELinux labels on chronyd pidfile. chronyd pidfile should be labeled with the following label: `system_u:object_r:chronyd_var_run_t:s0` This also changes bindcmdaddress to not touch /var/run/chrony. """ To pull the PR as Git branch: git remote add ghfreeipa https://github.com/freeipa/freeipa git fetch ghfreeipa pull/1897/head:pr1897 git checkout pr1897

2 1

[freeipa PR#1805][opened] Handle whitespace, add separator to regex in set_directive_lines
by rcritten 02 May '18

02 May '18

URL: https://github.com/freeipa/freeipa/pull/1805 Author: rcritten Title: #1805: Handle whitespace, add separator to regex in set_directive_lines Action: opened PR body: """ We added the separator to the regex in set_directive_lines to avoid grabbing just a prefix. This doesn't allow for whitespace around the separator. For the Apache case we expected that the separator would be just spaces but it can also use tabs (like Ubuntu 18). Add a special case so that passing in a space separator is treated as whitespace (tab or space). https://pagure.io/freeipa/issue/7490 Signed-off-by: Rob Crittenden <rcritten(a)redhat.com> """ To pull the PR as Git branch: git remote add ghfreeipa https://github.com/freeipa/freeipa git fetch ghfreeipa pull/1805/head:pr1805 git checkout pr1805

2 1

[freeipa PR#1895][opened] [Backport][ipa-4-6] Validate the Directory Manager password before starting restore
by tiran 02 May '18

02 May '18

URL: https://github.com/freeipa/freeipa/pull/1895 Author: tiran Title: #1895: [Backport][ipa-4-6] Validate the Directory Manager password before starting restore Action: opened PR body: """ This PR was opened automatically because PR #1892 was pushed to master and backport to ipa-4-6 is required. """ To pull the PR as Git branch: git remote add ghfreeipa https://github.com/freeipa/freeipa git fetch ghfreeipa pull/1895/head:pr1895 git checkout pr1895

1 1

[freeipa PR#1892][opened] Validate the Directory Manager password before starting restore
by rcritten 02 May '18

02 May '18

URL: https://github.com/freeipa/freeipa/pull/1892 Author: rcritten Title: #1892: Validate the Directory Manager password before starting restore Action: opened PR body: """ The password was only indirectly validated when trying to disable replication agreements for the restoration. https://pagure.io/freeipa/issue/7136 Signed-off-by: Rob Crittenden <rcritten(a)redhat.com> """ To pull the PR as Git branch: git remote add ghfreeipa https://github.com/freeipa/freeipa git fetch ghfreeipa pull/1892/head:pr1892 git checkout pr1892

2 1

[freeipa PR#1894][opened] install: fix reported external CA configuration
by frasertweedale 02 May '18

02 May '18

URL: https://github.com/freeipa/freeipa/pull/1894 Author: frasertweedale Title: #1894: install: fix reported external CA configuration Action: opened PR body: """ The installer reports the CA configuration that will be used, including whether the CA is self-signed or externally-signed. Installation with external CA takes two steps. The first step correctly reports the externally signed configuration (like the above), but the second step reports a self-signed configuration. The CA *is* externally signed, but the configuration gets reported incorrectly at step 2. This could confuse the administrator. Fix the message. Fixes: https://pagure.io/freeipa/issue/7523 """ To pull the PR as Git branch: git remote add ghfreeipa https://github.com/freeipa/freeipa git fetch ghfreeipa pull/1894/head:pr1894 git checkout pr1894

2 1

[freeipa PR#1888][opened] Load certificate files as binary data
by tiran 02 May '18

02 May '18

URL: https://github.com/freeipa/freeipa/pull/1888 Author: tiran Title: #1888: Load certificate files as binary data Action: opened PR body: """ In Python 3, cryptography requires certificate data to be binary. Even PEM encoded files are treated as binary content. certmap-match and cert-find were loading certificates as text files. A new BinaryFile type loads files as binary content. Fixes: https://pagure.io/freeipa/issue/7520 Signed-off-by: Christian Heimes <cheimes(a)redhat.com> Reviewed-By: Stanislav Laznicka <slaznick(a)redhat.com> Reviewed-By: Florence Blanc-Renaud <frenaud(a)redhat.com> """ To pull the PR as Git branch: git remote add ghfreeipa https://github.com/freeipa/freeipa git fetch ghfreeipa pull/1888/head:pr1888 git checkout pr1888

1 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

FreeIPA-devel May 2018