# Comment's meaning for a resolved issue **URL:** \ **Category:** General Discussion\ **Created:** [November 5, 2020, 12:30pm UTC](https://forums.suse.com/t/comments-meaning-for-a-resolved-issue/35356 "2020-11-05T12:30:03Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Frederic](https://avatars.discourse-cdn.com/v4/letter/f/4491bb/32.png) [@Frederic](https://forums.suse.com/u/Frederic)\ **Post date:** [November 5, 2020, 12:30pm UTC](https://forums.suse.com/t/comments-meaning-for-a-resolved-issue/35356/1 "2020-11-05T12:30:03Z")
Hello I’ve a question about a comment in a resolved issue for openssl ([https://bugzilla.suse.com/show\_bug.cgi?id=1169407](https://bugzilla.suse.com/show_bug.cgi?id=1169407 "https://bugzilla.suse.com/show\_bug.cgi?id=1169407")). In the last comment, we have this sentence : _At times this might be only a partial fix._ What does it mean ? Is this just a caution in case someone found a way to reproduce the issue ? Can we consider that the issue is fully resolved in openssl-1\_1 1.1.1d-2.23.1 ? ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [November 5, 2020, 2:07pm UTC](https://forums.suse.com/t/comments-meaning-for-a-resolved-issue/35356/2 "2020-11-05T14:07:05Z")
@Frederic are you running the d variant? If so can you upgrade to the g variant, which is recommended? Seems to me since the bug report hasn’t been re-opened, no one has reported any issues… ---
**Author:** ![Frederic](https://avatars.discourse-cdn.com/v4/letter/f/4491bb/32.png) [@Frederic](https://forums.suse.com/u/Frederic)\ **Post date:** [November 5, 2020, 4:25pm UTC](https://forums.suse.com/t/comments-meaning-for-a-resolved-issue/35356/3 "2020-11-05T16:25:32Z")
I’m working on SLES 12 SP3 LTSS/ SP5 (depending on products). For each version, I only see the d version for openssl, g is not available, am I wrong ? ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [November 5, 2020, 5:46pm UTC](https://forums.suse.com/t/comments-meaning-for-a-resolved-issue/35356/4 "2020-11-05T17:46:19Z")
@Frederic ahh yes, just checked, my bad. I see it’s there for SLES 12 SP5, don’t see it for SLES 12 SP3 LTSS (but it is the same version…), I would search the SP3 LTSS changelog for the CVE reference, it should be there. You can see this sort of information via SUSE Customer Center 😉 [https://scc.suse.com/patches](https://scc.suse.com/patches) select your product and enter the CVE reference: CVE-2020-1967 ---
**Author:** ![Frederic](https://avatars.discourse-cdn.com/v4/letter/f/4491bb/32.png) [@Frederic](https://forums.suse.com/u/Frederic)\ **Post date:** [November 6, 2020, 8:18am UTC](https://forums.suse.com/t/comments-meaning-for-a-resolved-issue/35356/5 "2020-11-06T08:18:16Z")
Thanks for the link (add it to my SuSE’s bookmarks 😉 ) So, to come back to the first question, the comment saying that it might be a partial fix is official/true or just a comment waiting for further tests ? I don’t know what to say to my developer when he see it ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [November 6, 2020, 2:07pm UTC](https://forums.suse.com/t/comments-meaning-for-a-resolved-issue/35356/6 "2020-11-06T14:07:34Z")
@Frederic it’s a comment on the bug report for sure, see [https://www.suse.com/security/cve/CVE-2020-1967/](https://www.suse.com/security/cve/CVE-2020-1967/) SLE 12 SP3 (LTSS?) says not affected… ---
**Author:** ![Frederic](https://avatars.discourse-cdn.com/v4/letter/f/4491bb/32.png) [@Frederic](https://forums.suse.com/u/Frederic)\ **Post date:** [November 6, 2020, 2:27pm UTC](https://forums.suse.com/t/comments-meaning-for-a-resolved-issue/35356/7 "2020-11-06T14:27:30Z")
The good news is that this development team has switched to SLES 12 SP5. I can say that it was just a comment in the bug report. Thanks for your time @malcolmlewis