A common protocol structure is to have a header containing a length field, followed by data of length bytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.

I do not know the best way to address this, but quick and easy way to support

In this ticket we will keep track of existing translations of the documentation in languages other than English. If you have translated the documentation in a missing language, please do share the link here:

• Original/English
• Spanish/Español by Colectivo Disonancia (not fully updated)

For

Hi & welcome to Scapy's github ! This page lists issues that you can try to fix if you want to start contributing to Scapy.

This list includes wishes and things added by the maintainers based on the issues that we get, but also issues marked with TODO or XXX that already exist in Scapy's code base (layers). If you want to contribute to the project you might just take care one of the bugs.

It has been a pleasure for me to contribute to all of you 2 versions of this tool.

I've been working on other open source projects that I'm about to release for you, so I haven't finished trape version 3.0.

But, I invite you and the entire community that has used this project, to collaborate with some lines of code, implementing your own ideas and improving trape, turning it into a project o

Matched on: ::
Name: Internet Protocol (IP) Address Version 6
Link:  https://www.shodan.io/host/::

This shouldn't match.

Someone should map publicly available EVTX samples to Sigma rules. This would enable us to automatically test the correctness of generated queries.

Known security-related EVTX repositories:

• https://github.com/sbousseaden/EVTX-ATTACK-SAMPLES
• https://github.com/Cyb3rWard0g/mordor

Feel free to extend the list.

Mapping should be:

Sigma rule -> Repository/EVTX ( -> expected matched

We need Vagrant docs, you can find it here https://github.com/NullArray/AutoSploit/tree/dev-beta/Vagrant

The https://github.com/nccgroup/ScoutSuite/blob/master/ScoutSuite/providers/gcp/rules/findings/iam-lack-of-service-account-key-rotation.json finding should only flag USER_MANAGED keys (https://cloud.google.com/iam/docs/reference/rest/v1/projects.serviceAccounts.keys), as SYSTEM_MANAGED keys are "managed and rotated by Google"

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. create .bandit file with content:

[bandit]
tests: B101,B102,B301

2. run bandit -c .bandit -r module/
3. get error:
   [main] ERROR .bandit : Error parsing file.

Expected behavior
working as described in readme

Bandit version

ba

This will help reduce some copy pasted boiler plate code.

These files when added magically but not part of git tracked files causes update failure.

reference: frappe/bench#1225

related: frappe/frappe#16616 (you'll find which function create this file in this PR)