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
Actually v3 is the newest protocol version, v2 is the insecure one, v1 even older an unused.
*** Bug 54797 has been marked as a duplicate of this bug. ***
Fixed in # Bug54797 Currently I tagged it TM:5.1-0, but I think we can even do it as en erratu5.0-2: UDN v3 was implemented and shipped with 4.4-0 and also back-ported as erratum4.3-3 The issue is targeted for UCS 5.0-x, where only UCS-4.4-8 or newer is supported; UCS-4.3 is long EoL. All Appbox images have been updated to get the newer UDL supporting v3. Therefore all UDL will use v3 by default and v2 support in UDN is no longer needed.
(In reply to Mirac Erdemiroglu from comment #4) > Fixed in # Bug54797 No. This bug is about removing version 1 and 2 from the protocol implementation. In theory it can still be used.