Bug 54837 – Remove UDN/UDL protocol version 1 and 2

Bug 54837 - Remove UDN/UDL protocol version 1 and 2


Summary:	Remove UDN/UDL protocol version 1 and 2

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Notifier (univention-directory-notifier)
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 5.0-2-errata
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:	https://git.knut.univention.de/univen...
Keywords:

Depends on:	48642
Blocks:	54797 55863
	Show dependency tree / graph

Reported:	2022-06-08 16:10 CEST by Philipp Hahn
Modified:	2023-03-08 08:17 CET (History)
CC List:	4 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	5: Blocking further progress on the daily work
User Pain:	0.286
Enterprise Customer affected?:	Yes
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2022051921000634, 2022062221000162
Bug group (optional):	API change, Cleanup, Debt Technical
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 Philipp Hahn

2022-06-08 16:10:13 CEST

UDN/UDL protocol version 2 was introduced with UCS 4.4-0 (Bug #48642) and backported as 4.3-3+427 (Bug #48427).

So all supported UCS versions support v2 and v1 can be removed.

Supporting v1 leads so all kind of bugs like Bug #54797
- /var/lib/univention-ldap/notify/transaction* can be removed as all data is stored in and accessed from LDAP
- code can be removed from univention-directory-notifier
- code can be removed from univention-directory-listener
- univention-translog can be simplified
- references should be removed from docs/developer-reference/
- check SDB articles for references
- ...

See Bug #41687

Comment 1 Philipp Hahn

2022-07-06 10:02:15 CEST

Actually v3 is the newest protocol version, v2 is the insecure one, v1 even older an unused.

Comment 2 Philipp Hahn

2022-07-06 10:03:14 CEST

*** Bug 54797 has been marked as a duplicate of this bug. ***