10 Commits

Author SHA1 Message Date
sthen
29389da44c bump REVISION for switch from Python 3.8 -> 3.9 2021-11-02 00:02:15 +00:00
sthen
3cbe1c2f30 Reverse the polarity of MODPY_VERSION; default is now 3.x,
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.

This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.

Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.
2021-02-23 19:39:08 +00:00
sthen
ff3be859fa split the py2 version of py-dnspython off into net/py2-dnspython,
update the py3 version to 2.1.0, and adapt ports using it.
2021-01-16 21:21:04 +00:00
sthen
d9cfe4113e bump REVISION; python 3 default changed to 3.8 2020-07-03 21:12:24 +00:00
jasper
b1a67a0628 update to fierce-1.4.0
from purplerain@secbsd.org, thanks!
2020-05-30 12:09:31 +00:00
sthen
48b0b9660c replace simple PERMIT_PACKAGE_CDROM=Yes with PERMIT_PACKAGE=Yes 2019-07-12 20:48:23 +00:00
kmos
c45cd79fc7 Add RUN_DEPENDS to TEST_DEPENDS automatically for ports using the
lang/python port module. I've not yet come up with a port that
would not need this and one can always set MODPY_TESTDEP to "no"
to prevent the module from touching TEST_DEPENDS.

Idea from afresh1 who pointed out the cpan module already does this.

aja "I support this move."

OK sthen@
2019-05-15 12:04:34 +00:00
sthen
d7f0752227 bump all the py3 things, _SYSTEM_VERSION didn't quite work out how
we expected and it's easier|safer to do it this way than fiddle with
pkg_add now. thanks aja for update tests with a quick bulk.
2019-04-28 20:51:26 +00:00
jasper
94d53fbdd5 update to fierce-1.2.2 2018-07-10 13:30:21 +00:00
jasper
44f66d0436 import fierce-1.2.0
Fierce is a semi-lightweight scanner that helps locate non-contiguous IP
space and hostnames against specified domains. It's really meant as a
pre-cursor to nmap, unicornscan, nessus, nikto, etc, since all of those
require that you already know what IP space you are looking for. This
does not perform exploitation and does not scan the whole internet
indiscriminately. It is meant specifically to locate likely targets both
inside and outside a corporate network.

ok rpointel@
2017-11-20 17:56:08 +00:00