Stephen Kurt
BANNED
- Jan 15, 2016
- 50
- 10
Here is mine note after study Add/Train New PlatForms.
1. Fieldname match logic in [step] section:
(search/match) fieldname=variable/value
reg_username={Jack000|%user-name%}
Example:
<form
...
<input...name="reg_username"
...
<input...name="reg_password"
...
<input...name="reg_password2"
...
First will search/check if there are exact/phrase matches. (eg. without*); and is unaffected
by the from up to down order of exact searching fieldnames in a step section.
If matches one, the matched fieldnames in a form will not be searched by the rest search conditions any more.
Second is searching with *.
The process is:
Take the first one with * in a [step], search a fieldname with it in a form from it's top to bottom. It can match more than one fieldnames.
Then the 2nd condition, but the previous matched which had been found with a *, will not affacted by the current/and later searches now.
Then the rest.
The effect is: those without *, their orders in a submission [step] don't affact the final result.
But the order of those with * can influence filling a form. So in theory, related strings with *,
put the long string close to the beginning of step, will increase accuracy. And if there are many .ini file, collect all the fieldname key=value part, if their value part is same, for example, (same) password value, then the numbers of search keys for password field can be reduced, even only left one, by using *.
2. FormMustContain & FormMustNotContain
Login often mixed with Register, so
FormMustNotContain=login*login*login sometimes it's a little dangerous.
1. Fieldname match logic in [step] section:
(search/match) fieldname=variable/value
reg_username={Jack000|%user-name%}
Example:
<form
...
<input...name="reg_username"
...
<input...name="reg_password"
...
<input...name="reg_password2"
...
First will search/check if there are exact/phrase matches. (eg. without*); and is unaffected
by the from up to down order of exact searching fieldnames in a step section.
If matches one, the matched fieldnames in a form will not be searched by the rest search conditions any more.
Second is searching with *.
The process is:
Take the first one with * in a [step], search a fieldname with it in a form from it's top to bottom. It can match more than one fieldnames.
Then the 2nd condition, but the previous matched which had been found with a *, will not affacted by the current/and later searches now.
Then the rest.
The effect is: those without *, their orders in a submission [step] don't affact the final result.
But the order of those with * can influence filling a form. So in theory, related strings with *,
put the long string close to the beginning of step, will increase accuracy. And if there are many .ini file, collect all the fieldname key=value part, if their value part is same, for example, (same) password value, then the numbers of search keys for password field can be reduced, even only left one, by using *.
2. FormMustContain & FormMustNotContain
Login often mixed with Register, so
FormMustNotContain=login*login*login sometimes it's a little dangerous.
Code:
[step]
FormMustContain=register.php"*method=|action=*signup*signup*method=|="joinForm"*method=|register"*method="|creaccount*method=|action=*signup*signup*method=|Confirm password|value="Create account"|type="image"
Formmustnotcontain=action="/search|search*method=|search"*action=|value="search|value="Sign In"|value="Log in"|login.php?*method=|"processlogin"|name="persistent"
Last edited:
