389-devel August 2016

389-devel@lists.fedoraproject.org

12 participants
46 discussions

Please review: 397 add pbkdf2 and scrypt
by William Brown 05 Aug '16

05 Aug '16

https://fedorahosted.org/389/ticket/397 https://fedorahosted.org/389/attachment/ticket/397/0001-Ticket-397-Add-PBKD… https://fedorahosted.org/389/attachment/ticket/397/0001-Ticket-397-Implemen… Passes valgrind, and asan, no leaks etc. -- Sincerely, William Brown Software Engineer Red Hat, Brisbane

1 0

Please review: 48949 style and corrections for community contribution
by William Brown 05 Aug '16

05 Aug '16

https://fedorahosted.org/389/ticket/48949 https://fedorahosted.org/389/attachment/ticket/48949/0005-Ticket-48949-Fix-… We had a community contribution to lib389 overnight. I have reviewed and acked the 4 patches they provided. I have provided some small corrections to the content, and would like this verified by someone in the team. Thanks, -- Sincerely, William Brown Software Engineer Red Hat, Brisbane

1 0

please review: Ticket 48932 - Admin Server - Stopping admin server stops all the httpd services
by Mark Reynolds 03 Aug '16

03 Aug '16

https://fedorahosted.org/389/ticket/48932 https://fedorahosted.org/389/attachment/ticket/48932/0001-Ticket-48932-stop…

1 0

Discuss: Change default password mechanism to DEFAULT
by William Brown 03 Aug '16

03 Aug '16

Hi, I would like to propose an idea that will help improve the security of DS password storage for new installations and their future upgrades. I would like to change the default value of passwordStorageScheme to a type called DEFAULT. The implementation of DEFAULT would be an interface to the "current best practice storage mechanism of this release of directory server". This way sites that want to customise their hash types can. Sites that "install and forget" will gain a strong password storage mechanism out of the box. Additionally, we can *change* the DEFAULT mapping in releases as we have better and stronger hashes, or as we learn and get better advice on their security. This way, users who "install and forget" are continually moving forwards with their security as they upgrade versions. When user passwords are changed in their systems, they are updated to the newer hashes etc. I think this would be a trivial feature to implement and add, and I think that the net increase in security for administrators and accounts on their system is huge. Is this something we would like to pursue? -- Sincerely, William Brown Software Engineer Red Hat, Brisbane

2 2

Please review: Ticket 47976 - Add fixed CI test case
by Simon Pichugin 02 Aug '16

02 Aug '16

Hi team, I am verifying the test case and I've found out that the patch with ticket47976_test.py wasn't commited. I've fixed it a bit (moved to test/tickets dir and set export.ldif to ldif_dir). Please, review. https://fedorahosted.org/389/ticket/47976 https://fedorahosted.org/389/attachment/ticket/47976/0001-Ticket-47976-Add-… Thanks, Simon

1 0

Please review: Ticket 48882: server can hang in connection list processing
by Ludwig Krispenz 01 Aug '16

01 Aug '16

https://fedorahosted.org/389/ticket/48882 https://fedorahosted.org/389/attachment/ticket/48882/0001-Ticket-48882-serv… -- Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-devel August 2016