Package: nano Version: 2.6.1-1 Severity: normal Tags: upstream Dear Maintainer,
when creating a lock file, nano silently assumes process IDs are not
bigger than 16 bit, bigger values are truncated (src/file.c:232). When
reading a lock file, this results in the wrong pid being computed
(l.354) and subsequently displayed.
As far as I can tell, this is purely visual as nano does not provide a
mechanism to kill the other instance. Still a user could decide to do
so, things might go downhill from there.
FWIW, enabling a bigger PID range is a simple as poking a value
somewhere in /proc, and people do this.
Please change nano to support 32bit PID values, luckily there's enough
space in the lockfile for this.
Christoph
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.15 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
Versions of packages nano depends on:
ii libc6 2.23-1
ii libncursesw5 6.0+20160319-2+b1
ii libtinfo5 6.0+20160319-2+b1
ii zlib1g 1:1.2.8.dfsg-2+b1
nano recommends no packages.
Versions of packages nano suggests:
pn spell <none>
-- no debconf information
signature.asc
Description: Digital signature
