On Thu, Feb 27, 2020 at 10:30:13PM +0100, Theo Buehler wrote:
> This depends on the net/py-tlslite-ng port that I sent a few hours ago:
> https://marc.info/?l=openbsd-ports&m=158281798026590&w=2
> As mentioned there, I intend to use this port for TLSv1.3 server
> development and libssl regression testing.
> This works fine for me as it is. The manual hackery in the
> {pre,post}-install target might have better solutions though...
> The symlink is created so the site-packages/tlsfuzzer/utils directory is
> picked up and byte-compiled by whichever magic it is that is responsible
> for this. The scripts dir is installed and byte-compiled manually in
> the post-install target. I'm also not sure whether ${LOCALBASE}/share
> is the ideal location.
> All 571 tests pass with 27 warnings.
> $ cat pkg/DESCR
> Fuzzer and test suite for TLS implementations (SSLv2-TLSv1.3). Provides
> ready-to-use scripts testing for many vulnerabilities (ROBOT, DROWN, etc.)
> and general standards conformity (RFC 5246, RFC 7627, RFC 7905, etc.)
> Early alpha version - no API stability guarantees.
This does fail 13 tests on sparc64, but they are all that same
NotImplementedError that was making tests fail on py-tlslite-ng.
ok kmos for import once py-tlslite-ng is in.
--Kurt
