Skip to content
#

pentesting

Here are 1,909 public repositories matching this topic...

lastcrash
lastcrash commented Jan 23, 2021

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
bee-san
bee-san commented Oct 18, 2020

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

wstg
jespunya
jespunya commented Mar 13, 2020

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

Improve this page

Add a description, image, and links to the pentesting topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the pentesting topic, visit your repo's landing page and select "manage topics."

Learn more