Before accepting your pull requests we need you or your organization to sign our contribution agreement.
-We do this to keep the ownership of Suricata in one hand: the Open Information Security Foundation. See https://suricata-ids.org/about/open-source/ and https://suricata-ids.org/about/contribution-agreement/
+We do this to keep the ownership of Suricata in one hand: the Open Information Security Foundation. See https://suricata.io/features/open-source/ and https://suricata.io/our-story/contribution-agreement/
Contribution Process
--------------------
Questions
---------
-If you have questions about contributing, please contact us via https://suricata-ids.org/support/
+If you have questions about contributing, please contact us via https://suricata.io/community/
Make sure these boxes are signed before submitting your Pull Request -- thank you.
- [ ] I have read the contributing guide lines at https://redmine.openinfosecfoundation.org/projects/suricata/wiki/Contributing
-- [ ] I have signed the Open Information Security Foundation contribution agreement at https://suricata-ids.org/about/contribution-agreement/
+- [ ] I have signed the Open Information Security Foundation contribution agreement at https://suricata.io/our-story/contribution-agreement/
- [ ] I have updated the user guide (in doc/userguide/) to reflect the changes made (if applicable)
Link to [redmine](https://redmine.openinfosecfoundation.org/projects/suricata/issues) ticket:
__Q: do you require signing of a contributor license agreement?__
-A: Yes, we do this to keep the ownership of Suricata in one hand: the Open Information Security Foundation. See http://suricata-ids.org/about/open-source/ and http://suricata-ids.org/about/contribution-agreement/
+A: Yes, we do this to keep the ownership of Suricata in one hand: the Open Information Security Foundation. See https://suricata.io/features/open-source/ and https://suricata.io/our-story/contribution-agreement/
Team:
-https://suricata-ids.org/about/team/
+https://suricata.io/our-story/team/
All contributors:
https://www.ohloh.net/p/suricata-engine/contributors/summary
-https://suricata-ids.org/news/
+https://suricata.io/news/
Plenty, and you're welcome to help!
-https://suricata-ids.org/participate/
+https://suricata.io/join-our-community/
detect thread. For each output script, a single state is used. Keep in
mind that a rule reload temporary doubles the states requirement.
-.. _deprecation policy: https://suricata-ids.org/about/deprecation-policy/
+.. _deprecation policy: https://suricata.io/our-story/deprecation-policy/
* Suricata Home Page
- https://suricata-ids.org/
+ https://suricata.io/
* Suricata Support Page
- https://suricata-ids.org/support/
+ https://suricata.io/community/
* Suricata Home Page
- https://suricata-ids.org/
+ https://suricata.io/
* Suricata Support Page
- https://suricata-ids.org/support/
+ https://suricata.io/community/
* Suricata Home Page
- https://suricata-ids.org/
+ https://suricata.io/
* Suricata Support Page
- https://suricata-ids.org/support/
+ https://suricata.io/community/
* Suricata Home Page
- https://suricata-ids.org/
+ https://suricata.io/
* Suricata Support Page
- https://suricata-ids.org/support/
+ https://suricata.io/community/
inner one has different VLAN tags it will still end up in the same queue in
**cluster_qm** mode. This was observed with the i40e driver up to 2.8.20 and
the firmare version up to 7.00, feel free to report if newer versions have
-fixed this (see https://suricata-ids.org/support/).
+fixed this (see https://suricata.io/community/).
If you want to use **tshark** to get an overview of the traffic direction use
drops are seen and the hardware should be capable to deal with such traffic
loads you should deep dive if there is any specific traffic issue (see above)
or report the performance issue so it can be investigated (see
-https://suricata-ids.org/support/).
+https://suricata.io/community/).
Suricata also provides several specific traffic related signatures in the rules
folder that could be enabled for testing to spot specific traffic issues. Those
Example::
- alert http any any -> any any (content:"suricata-ids.org"; \
+ alert http any any -> any any (content:"suricata.io"; \
http_host; bypass; sid:10001; rev:1;)
- ``file-log``, the non-EVE JSON file log. Use EVE.files instead.
- ``drop-log``, the non-EVE JSON drop log.
-See https://suricata-ids.org/about/deprecation-policy/
+See https://suricata.io/our-story/deprecation-policy/
version=version,
author='OISF Developers, Eric Leblond',
author_email='oisf-devel@lists.openinfosecfoundation.org, eric@regit.org',
- url='https://www.suricata-ids.org/',
+ url='https://www.suricata.io/',
packages=[
"suricata",
"suricata.config",