Merge lp://staging/~lsandecki/ubuntu-motd/cve-2023-2650 into lp://staging/ubuntu-motd

Proposed by Lech Sandecki
Status: Merged
Merged at revision: 96
Proposed branch: lp://staging/~lsandecki/ubuntu-motd/cve-2023-2650
Merge into: lp://staging/ubuntu-motd
Diff against target: 19 lines (+4/-4)
1 file modified
aptnews.json (+4/-4)
To merge this branch: bzr merge lp://staging/~lsandecki/ubuntu-motd/cve-2023-2650
Reviewer Review Type Date Requested Status
Steve Langasek Approve
Dean Henrichsmeyer (community) Approve
Review via email: mp+446205@code.staging.launchpad.net

Description of the change

adding a new apt-news message regarding the recently fixed OpenSSL vulnerability

To post a comment you must log in.
Revision history for this message
Dean Henrichsmeyer (dean) :
review: Approve
Revision history for this message
Steve Langasek (vorlon) :
review: Needs Fixing
97. By lech <email address hidden>

addressed the review suggestion

Revision history for this message
Steve Langasek (vorlon) wrote :

Should we be revving the start date now that the listed date is in the past?

review: Approve
Revision history for this message
Renan Rodrigo (renanrodrigo) wrote :

I would say there is no need to. The past date is fine - the client will understand that this should be active immediately.

Revision history for this message
Seth Arnold (seth-arnold) wrote :

I'm not sure either of these is really "recently fixed", 18 days and 41 days old:

30 May 2023 https://ubuntu.com/security/notices/USN-6119-1
22 June 2023 https://ubuntu.com/security/notices/USN-6188-1

These banners will be better received if they're relevant.

I expect that this will instead be read as "oh no a new openssl issue? why isn't the update available yet?" followed by a few minutes looking for more information, and then finding out that this is old news and unattended-upgrades handled it weeks ago. That's not likely to leave a pleasant impression.

Thanks

Revision history for this message
Julian Andres Klode (juliank) wrote :

The message doesn't make all that much sense because the context you see it in is when you are upgrading, so it's somewhat redundant, either it was already upgraded before or the call you see the message in is upgrading it.

There's effectively no way to see the message without getting an upgraded OpenSSL.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

In addition, the CVE mentioned is a pretty benign issue, I'm not sure why it is relevant...

Revision history for this message
Julian Andres Klode (juliank) wrote :

This message was reported as a bug inhttps://bugs.launchpad.net/bugs/2027674

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches