Bug 32683 - Cleanup ldap-group-to-file.py; possible recursion bug
Cleanup ldap-group-to-file.py; possible recursion bug
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: PAM
UCS 3.2
Other Linux
: P5 enhancement (vote)
: UCS 3.x
Assigned To: UCS maintainers
:
Depends on: 32581
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-24 17:14 CEST by Philipp Hahn
Modified: 2018-04-13 13:42 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Cleanup
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2013-09-24 17:14:03 CEST
+++ This bug was initially created as a clone of Bug #32581 +++
1. Comparing oranges while adding apples? 
> if member[0] not in recursion_list:
>     recursion_list.append(g[0])

2. code cleanup: see attachment 5465 [details]
  1. Use /dev/null instead of PIPE
  2. Don't use deprecated string module
  3. Split into smaller functions
  4. Log to STDERR
  5. Really prevent recursively double resolving the same group
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:40:51 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 2 Stefan Gohmann univentionstaff 2017-08-08 07:11:27 CEST
This issue has been filed against UCS 3.2.

UCS 3.2 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.