|Summary:||CVE-2018-10871 389-ds-base: replication and the Retro Changelog plugin store plaintext password by default [fedora-all]|
|Product:||[Fedora] Fedora||Reporter:||Cedric Buissart <cbuissar>|
|Component:||389-ds-base||Assignee:||thierry bordaz <tbordaz>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||31||CC:||rmeggins, tbordaz, vashirov|
|Target Milestone:||---||Keywords:||Security, SecurityTracking|
|Fixed In Version:||Doc Type:||Release Note|
|Doc Text:||Story Points:||---|
|Last Closed:||2020-02-10 14:40:22 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:||1639647|
Comment 1 Cedric Buissart 2018-06-18 08:49:50 UTC
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1591480,1592226 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
Comment 3 Ben Cotton 2019-05-02 20:38:26 UTC
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Comment 4 thierry bordaz 2019-07-16 13:58:55 UTC
Fix upstream -> POST
Comment 5 Ben Cotton 2019-08-13 17:04:43 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
Comment 6 Ben Cotton 2019-08-13 19:01:53 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
Comment 7 Viktor Ashirov 2020-02-10 14:40:22 UTC
This was fixed in 1.4.1, closing.