Alejandro Colomar efbbcade43 Use safer allocation macros
Use of these macros, apart from the benefits mentioned in the commit
that adds the macros, has some other good side effects:

-  Consistency in getting the size of the object from sizeof(type),
   instead of a mix of sizeof(type) sometimes and sizeof(*p) other
   times.

-  More readable code: no casts, and no sizeof(), so also shorter lines
   that we don't need to cut.

-  Consistency in using array allocation calls for allocations of arrays
   of objects, even when the object size is 1.

Cc: Valentin V. Bartenev <vbartenev@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
2023-02-23 20:28:43 -06:00
..
2021-12-06 01:41:17 +09:00
2022-05-15 17:36:08 -05:00
2022-05-15 17:36:08 -05:00
2021-12-06 01:41:17 +09:00
2023-02-23 20:28:43 -06:00
2021-12-27 09:27:44 -06:00
2021-12-27 09:27:44 -06:00
2021-12-06 01:41:17 +09:00
2021-12-06 01:41:17 +09:00
2017-10-22 21:28:58 +00:00
2021-08-18 18:07:50 +00:00

This testsuite is NOT SECURE: it will temporarily change your passwords file
with known passwords.
You should run it on a chroot, or on a secured dedicated system.



To test a Debian system:
	$ mkdir sid-chroot
	$ sudo debootstrap sid sid-chroot/ http://deb.debian.org/debian/
edit or copy a sources.list
	$ sudo cp /etc/apt/sources.list sid-chroot/etc/apt/
edit or copy a resolv.conf
	$ sudo cp /etc/resolv.conf sid-chroot/etc/
	$ su - root -c "chroot sid-chroot/ /bin/bash"
	# mount -t proc proc /proc
	# mount -t devpts devpts /dev/pts
	# aptitude update
	# aptitude install expect
	# cd /dev ; mknod --mode=666 /dev/ptmx c 5 2