Bug 30507 – Potential ReferenceError in AD Connector

Bug 30507 - Potential ReferenceError in AD Connector


Summary:	Potential ReferenceError in AD Connector

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	AD Connector
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal with 1 vote (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-02-20 11:15 CET by Lukas Walter
Modified:	2019-01-03 07:20 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
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
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Lukas Walter

2013-02-20 11:15:21 CET

univention-ad-connector/modules/univention/connector/__init__.py, 884 - 892
in class ucs, method poll_ucs():


for listener_file in files:
    sync_successfull = False
    filename = os.path.join(self.listener_dir, listener_file)
    if os.path.isfile(filename):
        if not filename in self.rejected_files:
            try:
                f=file(filename,'r')
            except IOError: # file not found so there's nothing to sync
                if self.dn_list.get(dn):
                                    ^^
                             This variable does not exist

Comment 1 Lukas Walter

2013-02-20 17:14:48 CET

I guess "dn,new,old,old_dn=cPickle.load(f)", a few lines below, is meant to be called earlier.

Comment 2 Stefan Gohmann

2019-01-03 07:20:02 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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