https://pulp.plan.io/https://pulp.plan.io/favicon.ico2017-09-15T14:49:31ZPulpPulp - Issue #3015: Sensitive data is visible in task results in case of download failureshttps://pulp.plan.io/issues/3015?journal_id=218952017-09-15T14:49:31Zttereshcttereshc@redhat.com
<ul><li><strong>Triaged</strong> changed from <i>No</i> to <i>Yes</i></li><li><strong>Sprint Candidate</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Pulp - Issue #3015: Sensitive data is visible in task results in case of download failureshttps://pulp.plan.io/issues/3015?journal_id=219412017-09-20T20:11:25Zjortel@redhat.comjortel@redhat.com
<ul></ul><p>I don't see how the paths to the SSL certificates or the username would be a security problem. The password should be masked. Masking is seems better than removing all together because knowing it contained a value would be helpful when troubleshooting.</p> Pulp - Issue #3015: Sensitive data is visible in task results in case of download failureshttps://pulp.plan.io/issues/3015?journal_id=219572017-09-21T14:21:49Zjortel@redhat.comjortel@redhat.com
<ul></ul><p>I have a patch for this.</p> Pulp - Issue #3015: Sensitive data is visible in task results in case of download failureshttps://pulp.plan.io/issues/3015?journal_id=219612017-09-21T14:28:29Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Sprint/Milestone</strong> set to <i>45</i></li></ul> Pulp - Issue #3015: Sensitive data is visible in task results in case of download failureshttps://pulp.plan.io/issues/3015?journal_id=220342017-09-25T14:47:43Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>jortel@redhat.com</i></li></ul> Pulp - Issue #3015: Sensitive data is visible in task results in case of download failureshttps://pulp.plan.io/issues/3015?journal_id=220482017-09-25T20:08:11Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>POST</i></li></ul><p><a href="https://github.com/pulp/pulp/pull/3172" class="external">https://github.com/pulp/pulp/pull/3172</a></p> Pulp - Issue #3015: Sensitive data is visible in task results in case of download failureshttps://pulp.plan.io/issues/3015?journal_id=220542017-09-26T13:47:15Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li></ul><p>Applied in changeset <a class="changeset" title="Mask logged password. closes #3015" href="https://pulp.plan.io/projects/pulp/repository/pulp/revisions/b7cee910e9078d13c9f5e956ef62291685d16da5">pulp|b7cee910e9078d13c9f5e956ef62291685d16da5</a>.</p> Pulp - Issue #3015: Sensitive data is visible in task results in case of download failureshttps://pulp.plan.io/issues/3015?journal_id=262192018-03-08T23:24:32Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint</strong> set to <i>Sprint 26</i></li></ul> Pulp - Issue #3015: Sensitive data is visible in task results in case of download failureshttps://pulp.plan.io/issues/3015?journal_id=262332018-03-08T23:24:54Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint/Milestone</strong> deleted (<del><i>45</i></del>)</li></ul> Pulp - Issue #3015: Sensitive data is visible in task results in case of download failureshttps://pulp.plan.io/issues/3015?journal_id=415102019-04-25T16:45:59Zdaviddavis
<ul><li><strong>Sprint/Milestone</strong> set to <i>3.0.0</i></li></ul> Pulp - Issue #3015: Sensitive data is visible in task results in case of download failureshttps://pulp.plan.io/issues/3015?journal_id=428282019-04-26T20:37:50Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> deleted (<del><i>Pulp 3</i></del>)</li></ul> Pulp - Issue #3015: Sensitive data is visible in task results in case of download failureshttps://pulp.plan.io/issues/3015?journal_id=507272019-12-13T17:25:19Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul>