1Guidelines for contributing 2=========================== 3 4To report a security issue (segfault, buffer overflow, infinite loop, arbitrary 5code execution etc) please send an e-mail to security@tcpdump.org, do not use 6the bug tracker! 7 8To report a non-security problem (failure to compile, failure to capture packets 9properly, missing support for a network interface type or DLT) please check 10first that it reproduces with the latest stable release of libpcap. If it does, 11please check that the problem reproduces with the current git master branch of 12libpcap. If it does (and it is not a security-related problem, otherwise see 13above), please navigate to https://github.com/the-tcpdump-group/libpcap/issues 14and check if the problem has already been reported. If it has not, please open 15a new issue and provide the following details: 16 17* libpcap version (e.g. from tcpdump --version) 18* operating system name and version and any other details that may be relevant 19 (uname -a, compiler name and version, CPU type etc.) 20* configure flags if any were used 21* statement of the problem 22* steps to reproduce 23 24Please note that if you know exactly how to solve the problem and the solution 25would not be too intrusive, it would be best to contribute some development time 26and open a pull request instead. 27 28Still not sure how to do? Feel free to [subscribe](https://www.tcpdump.org/#mailing-lists) 29to the mailing list tcpdump-workers@lists.tcpdump.org and ask! 30