The Tcpdump Group git mirrors - libpcap/blob - CONTRIBUTING.md

   1 Guidelines for contributing
   2 ===========================
   3
   4 To report a security issue (segfault, buffer overflow, infinite loop, arbitrary
   5 code execution etc), please send an e-mail to security@tcpdump.org, do not use
   6 the bug tracker!
   7
   8 To report a non-security problem (failure to compile, failure to capture packets
   9 properly, missing support for a network interface type or DLT), please check
  10 first that it reproduces with the latest stable release of libpcap. If it does,
  11 please check that the problem reproduces with the current git master branch of
  12 libpcap. If it does (and it is not a security-related problem, otherwise see
  13 above), please navigate to the
  14 [bug tracker](https://github.com/the-tcpdump-group/libpcap/issues)
  15 and check if the problem has already been reported. If it has not, please open
  16 a new issue and provide the following details:
  17
  18 * libpcap version (e.g. from `tcpdump --version`, `pcap-config --version` or
  19   `git describe`)
  20 * operating system name and version and any other details that may be relevant
  21   (`uname -a`, compiler name and version, CPU type etc.)
  22 * `configure` or `cmake` flags if any were used
  23 * statement of the problem
  24 * steps to reproduce
  25
  26 Please note that if you know exactly how to solve the problem and the solution
  27 would not be too intrusive, it would be best to contribute some development time
  28 and open a pull request instead.
  29
  30 If the proposed changes concern the BPF compiler code, please try to make sure
  31 the code is sufficiently covered with filter tests beforehand and `make check`
  32 passes on all CI-supported platforms as a minimum (this is done automatically
  33 for a pull request).  Then with the changes applied the tests should prove that
  34 the resulting filter program has not changed where it is not expected to change,
  35 and has changed in the expected ways where it is supposed to change, also that
  36 the effect of the filter program has not (or has) changed as well.
  37
  38 Still not sure how to do? Feel free to [subscribe](https://www.tcpdump.org/#mailing-lists)
  39 to the mailing list tcpdump-workers@lists.tcpdump.org and ask!