RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
changes:
- New and improved nemesis
- New in nemesis 1.4: nemesis-ethernet and nemesis-ip
- Windows support (link-layer injection only)
- Useful man pages
- Single binary
- Improved cross-platform support via GNU autotools
- Easier to use
- Nemesis will attempt to fill in as many details as possible
in a packet, thus requiring fewer or even no command line switches.
- Each protocol builder attempts to build a proper packet by default.
- Organized code base
- The network header structures in libnet proved useful so nemesis
now uses them where appropriate.
- Code is re-used wherever possible resulting in a much more concise
code base.
- Full payload functionality
- Payloads can now contain NULLs within them and full-size packets
are available on all supported platforms except Windows.
- IP and TCP options support
- All nemesis injectors (excluding ARP and Ethernet) now support IP
options via -O <IP options file>.
- All nemesis injectors using TCP as a transport protocol now
support TCP options via -o <TCP options file>.
- Improved IP and TCP functionality
- Full IP fragmentation support via new -F command line semantics.
- ECN support in TCP with the addition of -fE (ECE) and -fC (CWR).
verision of libnet <= 1.0.1b. This will prevent the case where the user
has installed the libnet 1.1.x branch and then tries to install an application
that is not compatible with the 1.1.x tree.
Over time the list of these applications that require the 1.0.x branch
will be reduced as they are updated to later versions that support the
libnet 1.1.x branch.
This addresses PR# 29056 opened by diro (at) nixsys.bz, thanks for the PR !
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
nemesis is a command-line UNIX network packet injection suite.
supported protocols: TCP, UDP, ICMP, ARP/RARP, IGMP, DNS,
RIP, and OSPF
"Nemesis attacks directed through fragrouter could be a most
powerful combination for the system auditor to find security
problems that could then be reported to the vendor(s), etc."
- Curt Wilson in Global Incident Analysis Center Detects Report
(SANS Institute - Nov 2000)
Provided in PR 14021 by xs@nitric.net.
Munged slightly by me to use buildlink functionality, and to use the
correct link time invocations for ELF binaries.
