Provide screen.xterm-256color and rxvt-unicode-256color terminfo entries in ncurses-base

Bug #1772872 reported by Matthias Klose
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ncurses (Ubuntu)
Fix Released
Undecided
Unassigned
Bionic
Fix Released
Undecided
Unassigned

Bug Description

The gnome standard terminal emulator (gnome-terminal) sets TERM=xterm-256color, and screen sets it to screen.xterm-256color, resulting in an usuable TERM setting, because the terminfo settings are not available by default. This patch includes the screen.xterm-256color and rxvt-unicode-256color settings in ncurses-base, resulting in working screen settings out-of-the-box.

Regression potential: The size of ncurses-base is increased by 3500 bytes (unpacked). The debian-installer packages might need adjustment for the additional size.

Acceptance criteria: The package builds, and provides the new terminfo entries in ncurses-base (note that no Breaks/Replaces are needed, because these are installed in a different path).

Also backport the fix for security issue CVE-2018-10754, fixing a segfault, adding a null-pointer check in _nc_parse_entry to handle an error when a use-name is invalid syntax.

CVE References

Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Matthias, or anyone else affected,

Accepted ncurses into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ncurses/6.1-1ubuntu1.18.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in ncurses (Ubuntu Bionic):
status: New → Fix Committed
tags: added: verification-needed verification-needed-bionic
Changed in ncurses (Ubuntu):
status: New → Fix Released
Revision history for this message
Matthias Klose (doko) wrote :

packages are built and ncurses-base includes the two new entries.

tags: added: verification-done verification-done-bionic
removed: verification-needed verification-needed-bionic
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for ncurses has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ncurses - 6.1-1ubuntu1.18.04

---------------
ncurses (6.1-1ubuntu1.18.04) bionic-proposed; urgency=medium

  * SRU: LP: #1772872: Backport changes from 6.1+20180210-4:
  * Move screen.xterm-256color and rxvt-unicode-256color terminfo entries
    from ncurses-term to ncurses-base (Closes: #898666, #898948).
  * Cherry-pick a fix from the 20180414 patchlevel: add a null-pointer
    check in _nc_parse_entry to handle an error when a use-name is invalid
    syntax (report by Chung-Yi Lin, CVE-2018-10754).

 -- Matthias Klose <email address hidden> Wed, 23 May 2018 10:08:27 +0200

Changed in ncurses (Ubuntu Bionic):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.