Derzeit ist das an UDM-CLI übergebene Passwort in der Prozessliste sichtbar, wenn eines angegeben wurde. $ ps axww | grep udm /usr/bin/python2.4 /usr/sbin/udm users/user list --binddn cn=qamaster,cn=dc,cn=computers,dc=univention,dc=qa --bindpw F0NNsopR (Unvollständige) Liste der mögliche Lösungen: - UDM entfernt Passwort aus Prozessliste (ldapsearch macht dies auch) - UDM bekommt Passwort per Datei übergeben
(In reply to Sönke Schwardt-Krummrich from comment #0) > - UDM entfernt Passwort aus Prozessliste (ldapsearch macht dies auch) This is not actually a solution, see Bug #20611
This issue has been filed against UCS 2.4. UCS 2.4 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". In this case please provide detailed information on how this issue is affecting you.
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.
We have added --bindpwdfile which is used in join script. You don't have to use --bindpw anymore.
(In reply to Felix Botner from comment #4) > We have added > > --bindpwdfile > > which is used in join script. You don't have to use --bindpw anymore. Yes, but we also have to check, weather we don't use --bindpw(d) anymore in the product. That's the case for joinscripts. Leftovers: > base/univention-system-setup/usr/lib/univention-system-setup/scripts/10_basis/18root_password: univention-directory-manager users/user modify --binddn "$binddn" --bindpwd "$bindpwd" > base/univention-system-setup/umc/python/setup/netconf/modules/LdapDns.py: self.call([self.executable, "--binddn", self.binddn, "--bindpwd", self.bindpwd > doc/app-center/lifecycle.rst: --bindpwd "$BINDPWD" Missing: * some scripts for the system (re-)configuration. * appcenter documentation for ISVs → Should we just close this or do anything about these leftovers?
IMHO, there should be a test in ucslint to ensure that this option is not used anymore in our products.
TODO: - Fix "leftovers" - update documentation - add check to ucslint
We already have that ucslint check: 0001-24: Invalid joinscript api …
Leftovers have been fixed and documentation has been updated. Packages: ``` Package: univention-system-setup Version: 15.3.1 Package: univention-directory-manager-rest Version: 12.3.1 Package: univention-directory-manager-modules Version: 17.3.3 Package: ucs-test Version: 12.3.20 ``` ``` 1278cc41d1d3 | chore(univention-system-setup): update system-setup, umc deprecate --bindpwd in favor of --bindpwdfile 8b3d5a2e5f51 | chore(univention-system-setup): update system-setup, umc deprecate --bindpwd in favor of --bindpwdfile 73ce2ff50730 | chore(umc): deprecate --bindpwd in favor of --bindpwdfile 73ce2ff50730 | chore(umc): deprecate --bindpwd in favor of --bindpwdfile e8f4f6298341 | test(ucs-test): update test, umc deprecate --bindpwd in favor of --bindpwdfile 7685c681c8ea | doc: update doc, umc deprecate --bindpwd in favor of --bindpwdfile ```
<https://errata.software-univention.de/#/?erratum=5.2x258> <https://errata.software-univention.de/#/?erratum=5.2x259> <https://errata.software-univention.de/#/?erratum=5.2x260>