by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
the TCPA chip described in IBM Global Security Analysis Lab's
article "Take Control of TCPA" in the August 2003 issue of Linux
Journal.
For this package to be useful, you need a computer with a TCPA
chip, and support for the chip in your kernel. An unofficial NetBSD
TCPA driver and instructions can be found here:
http://www.citi.umich.edu/u/rwash/projects/trusted/netbsd.html
I don't have a TCPA chip with which to verify the functionality of
this package.
Thanks to Soren Jacobsen for bringing me up to speed on modern
pkgsrc conventions, and to Rick Wash for his recent presentation
at my local ACM chapter on TCPA and "Trusted Computing".
