OS/Environment

None yet, but I'm working on OS X v10.11.6 'El Capitan' client-side. (See 'The way of deployment (cloud or local)' below for details on considered server infrastructure.)

Ansible version

None yet, as I haven't yet gotten that far into setting up Algo.

Version of components from requirements.txt

Not applicable (see above.)

Summary of the pro

If you call fuzz on a layer that contains a PacketField, that fuzz does not recurse down into a PacketField within the layer

class Foo(Packet):
    name='Foo'
    fields_desc=[
        int64("bar"),
    ]
    def extract_padding(self, s):
        return b'', s
        
class demo(Packet):
    name="demo"
    fields_desc = [ PacketField(name="foo",default=Foo(),cls=Foo)]
inst

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

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

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

Like in #1675 we should review all the dependencies to see if we can pin exactly what dependencies we want. Something like pip freeze.

The generic Windows audit log config lacks many event ids, e.g.

• registry events
• driver load service addition events, System/7045 and Security/4697
• likely others

Describe the bug
In the docs found here:
https://bandit.readthedocs.io/en/latest/plugins/index.html#complete-test-plugin-listing

B109 and B111 show a description instead of a plugin name. This looks inconsistent since all the other plugin names are listed. I believe this is a result of a recent change to remove these deprecated plugins.

To Reproduce

1. Navigate to https://bandit

Currently, facades implement good exception handling, but resource parsing does not. That means that for a given resource type, if parsing fails for any given resource, the fetch_all method fails and stops, hence not parsing any additional resources.

All resources should be reviewed and updated, to ensure they handle parsing errors.

e.g., for AWS IAM roles (https://github.com/nccgroup/Scou