[Bug 219053] update net/spoofer to 1.2.0

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219053

            Bug ID: 219053
           Summary: update net/spoofer to 1.2.0
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: mjl at luckie.org.nz

Created attachment 182289
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182289&action=edit
update spoofer to 1.2.0

Update the spoofer system from 1.0.5 to 1.2.0.  Changelog from

https://www.caida.org/projects/spoofer/downloads/changelog.txt

spoofer-1.2.0 (2017-03-30)
-------------
* Added ingress testing, i.e. testing whether spoofed packets from an outside
  network can reach the Spoofer client.
* Added IPv6 traceroute probing.
* Some settings that were requested in the binary installer are now requested
  in the UI, but only if they're not already set from a previous installation.
* Windows binary installer defaults to installing in the same directory as a
  previous installation, if there was one (affects only users who installed
  in a custom location).
* If Windows or OSX binary installer fails, it will restore the previously
  installed version of spoofer if it is >= 1.2.0.
* spoofer-scheduler: added options --save-settings, --restore-settings,
  --delete-settings, and --delete-data
* Fixed crash when both traceroute and scamper are missing (affects only
  source builds, since binary releases include scamper)
* Fixed: on some platforms, spoofer prober 1.1.0 would report "ERROR:
  pcap_sendpacket: send: Invalid argument" and then not run the tests.
* The scheduler will automatically kill the prober in the unlikely event that
  the prober hangs.

spoofer-1.1.0 (2016-12-16)
-------------
* Prober works much faster by probing multiple targets in parallel.
* Prober uses scamper instead of traceroute if possible; binary Spoofer
  releases include a bundled scamper binary.
* Improved display:
  - displays total progress, not just progress within current stage
  - GUI progress area is fixed size, so other elements don't jump around
  - GUI result history is updated in real time while a test is running;
    new data is highlighted briefly when first displayed
* Installer for Windows configures Windows Firewall.
* Added --dump-settings option to scheduler.
* Fixed a fatal problem in layer 2 probing on platforms with unusual
  interfaces (due to undocumented pcap behavior).
* Better detection of an HTTP server or proxy intercepting connection to
  spoofer server.
* Other minor fixes.

spoofer-1.0.8 (2016-10-31)
-------------
* Fixed a build error on some platforms when building from source.  If you
  have a binary release of 1.0.7 or have successfully built 1.0.7 from source,
  there is no need to upgrade.

spoofer-1.0.7 (2016-10-28)
-------------
* Fixed probe payload formatting issue in version 1.0.6 that occasionally
  caused a test result to be "unknown" instead of "blocked".
* Improved handling of socket errors on Windows.
* Improved handling of installation errors on MacOS.

spoofer-1.0.6 (2016-10-14)
-------------
* Fixed problem with stale lock files on OSX that prevented the scheduler from
  starting, which manifested in the UI as 'Critical: There is no scheduler
  running using settings in "..." ("schedulerSocketName" is not set).'
* Fixed:  prober could run earlier than expected if proberInterval ("Wait to
  run a test after a successful run on the same network") was set to 50 days
  or more.
* Portability fixes for building from source:
  - Builds automatically on platforms that have qtchooser installed
    (previously required QT_SELECT or QMAKE to be set correctly).
  - Builds automatically on systems with libprotobuf but not libprotobuf-lite
    (previously required --with-protobuf-heavy option).
  - Fixed build error on platforms without libpcap.
* Fixed race condition in writing settings when multiple schedulers were
  started simultaneously.
* Other minor fixes.

-- 
You are receiving this mail because:
You are the assignee for the bug.