security-tools

currently we have a version selector for every git tag, which is unnecessary overhead on the user. It is not needed from documentation perspective as there aren't (shouldn't be) any docs change in patch versions, only for new/changed features.

before:
v0.27.0, v0.27.1, v0.27.2, v0.28.0
after
v0.27, v0.28

Support for Microsoft Incoming Webhooks (Eg: Microsoft Teams Channel Webhooks) would be useful

Example:
https://customertenantname.webhook.office.com/webhookb2/ffffffff-ffff-ffff-ffff-ffffffffffff@ffffffff-ffff-ffff-ffff-ffffffffffff/IncomingWebhook/ffffffffffffffffffffffffffffffff/ffffffff-ffff-ffff-ffff-ffffffffffff

Possible Regex:

https:\/\/[a-z0-9A-Z]+\.webhook\.office\.com

Is your feature request related to a problem? Please describe.
Currently a hard refresh of the Index page is required in order to load the new index list and stats.

Describe the solution you'd like
A refresh button will help get the latest index list and stats.

Describe alternatives you've considered
None

Additional context
None

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

Disclaimer

The BEST way to contribute to Scapy is to play around with it, to find and fix broken stuff by yourself, i.e. Before you attempt to fix one of those pesky issues, just HAVE FUN with Scapy !😺

By using Scapy in your work, experiments, hacks, course

RustScan has an accessible mode, rustscan --accessible which should promise not to have any weird ASCII text in it.

Write CI that runs RustScan with --accessible a few times, with different flags / options and check the terminal output to see if it contains one of these:

1. [!]
2. [~]
3. [>]
4. | {}

If any of these characters appear in any of the tests, fail the CI. E

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

The recommendation is to set Cache-Control: private, no-store on any endpoint with sensitive information. Because while you can protect the traffic with TLS, you also need to keep sensitive information out of a client's (unencrypted) HTTP cache. I'm not sure how relevant this is to the API context of step-ca though—I've never seen an HTTP client library that caches content. But I guess the poi

Hey, here we need add url decoding cuz that invalid link with symbols of get request like ?, &, = etc

p.s thx for awesome tool

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