Received: from wolfsden.cz (wolfsden.cz [37.205.8.62]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 28976782CB7 for <~alpine/devel@lists.alpinelinux.org>; Wed, 7 Apr 2021 11:47:22 +0000 (UTC) Received: by wolfsden.cz (Postfix, from userid 110) id DADBE4AEF9A; Wed, 7 Apr 2021 11:47:20 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on wolfsden X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_ALL,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 Received: from localhost (unknown [128.0.188.242]) by wolfsden.cz (Postfix) with ESMTPSA id 5CE664AE545; Wed, 7 Apr 2021 11:47:20 +0000 (UTC) Date: Wed, 7 Apr 2021 13:47:19 +0200 From: Wolf To: Ariadne Conill Cc: ~alpine/devel@lists.alpinelinux.org Subject: Re: [3.15] System change proposal: Use netbsd-curses instead of GNU ncurses Message-ID: <20210407114719.qcup2wefxby523ez@wolfsden.cz> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qftaqd2jsb4z2i27" Content-Disposition: inline In-Reply-To: --qftaqd2jsb4z2i27 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, On 2021-04-06 12:17:33 -0600, Ariadne Conill wrote: > * Both libraries implement the POSIX curses API. >=20 > This means, 99% of applications won't need patching and should be basical= ly > compatible. (Incomplete) list of differences at [0] seems to contain only hard-to-debug, easy-to-miss type of things. > new_item This will just introduce memory bloat since every string in items will now be present twice. > post_menu Will just not work (and return error no one will likely check) instead of truncating (which might be fine for most software). > getnstr Not sure what the implications here are, but sounds like buffer overflow. All these things by themselves are fairly reasonable, however if software assumes ncurses behaviour, I'm afraid they will be hard to notice since none of them should lead to hard crash, but instead just to worse/suboptimal behavior. Is there a plan to go over whole aports to make sure none of the programs uses these functions the wrong way for openbsd-curses? What about new packages? I'm not sure it is possible to have some kind of linter for this. W. [0] https://wiki.netbsd.org/curses_in_netbsd/ --=20 There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors. --qftaqd2jsb4z2i27 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEE7BIrb0FxyZaks1p7hTP5S2N55TgFAmBtm8cACgkQhTP5S2N5 5TjIog//YsDxhUsWLI7lkXYzJ2D0cblXN87VVAjit2jFilKzu5+rRucdldHPxs7I i12RHZErbcOsagH/vF+yc0l+jwaHf2SCj5ydMw5NKzCAw25wTPdzsAoTWHTgqZ1H iJPFgQV/x2JzxTzhDBZS9meSUgBJzQEd+XKgdS3R3NmYXkAzgEh/4gOTTk4csKub HusmyfyWfU7sH/T/CvfiFOWm/8eV1Y3cn1yRqAyq8BGrZQdqYJs5bCDAowdiioX1 zQuGb/yeixjre2lXV+wiGz2boTkkliG4KqtXnwrC/YsB6GEJacr6QgZw34rQMhWz 2Ycm2axoXXZeFlmp5Cv1CmzOtfaTOVK+sF4J0qHv5X1tM3yJEER8j/hhmns3ylxr radCcvUMaqwRsVLTLfVDr/HwFrCC097j0fU7BnsVAXXGJFtjDHLBUzR4G8poqjGi GiACCcXDw2WFN6yAPcJkm+5CfnnBOwd7UVt33IKjoWFpT553WMtzB4Ok5y2SXJ+0 Lf0+agJMLUIK+4ToEd54Pb36e4CDwSAbQKaOhJBkFTHkYX4KQpklGP93k+Zfbj47 Yab0ECSAEnclqIO14xcboW1c3oho3AGK+ocCD4UYwaWXltujnOxMhy0O3fIiYqOI EKwYLfBFRJHb+MFCn8+hTKcrtXUwWM+QAFKhVuaqfTkUyQJ3V3s= =b0F4 -----END PGP SIGNATURE----- --qftaqd2jsb4z2i27--