pentesting

Hey Hackers of this spoopy month! 👻
Welcome to the Ciphey repo(s)!
This issue requires you to add a decoder.

This wiki section walks you through EVERYTHING you need to know, and we've added some more links at the bottom of this issue to detail more about the decoder.
https://github.com/Ciphey/Ciphey/wiki#adding-your-own-crackers--decoders

https://www.dcode.fr/t9-cipher
https://en.wikipe

Can we have a feature where a normal brute force is running based on HTTP response like 403/401 do a recursive brute force on that endpoint?

I testing bruteforce my opencart store.

this is body request:

-----------------------------34237939373614592773956005873
Content-Disposition: form-data; name="username"

^USER^
-----------------------------34237939373614592773956005873
Content-Disposition: form-data; name="password"

^PASS^
-----------------------------34237939373614592773956005873
Content-Disposition: form-dat

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

What would you like added?
Common Platform Enumeration (CPE) is a structured naming scheme for information technology systems, software, and packages. Based upon the generic syntax for Uniform Resource Identifiers (URI), CPE includes a formal name format, a method for checking names against a system, and a description format for binding text and tests to a name.

The usage of CPE naming is

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

p.s thx for awesome tool