===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
libdbd-mock-perl-1.58/t/021_DBD_Mock_Session.t-21- # look for the right username and password
libdbd-mock-perl-1.58/t/021_DBD_Mock_Session.t:22: my ($user_id) = $dbh->selectrow_array("SELECT user_id FROM users WHERE username = '$u' AND password = '$p'");
libdbd-mock-perl-1.58/t/021_DBD_Mock_Session.t-23- # if we find one, then ...
##############################################
libdbd-mock-perl-1.58/t/021_DBD_Mock_Session.t-31- # see if the username exists ...
libdbd-mock-perl-1.58/t/021_DBD_Mock_Session.t:32: my ($user_id, $login_failures) = $dbh->selectrow_array("SELECT user_id, login_failures FROM users WHERE username = '$u'");
libdbd-mock-perl-1.58/t/021_DBD_Mock_Session.t-33- # if we do have a username, and the password doesnt match then ...
##############################################
libdbd-mock-perl-1.58/t/021_DBD_Mock_Session.t-37- # update the login failures
libdbd-mock-perl-1.58/t/021_DBD_Mock_Session.t:38: $dbh->do("UPDATE users SET login_failures = (login_failures + 1) WHERE user_id = $user_id");
libdbd-mock-perl-1.58/t/021_DBD_Mock_Session.t-39- return 'BAD PASSWORD';
##############################################
libdbd-mock-perl-1.58/t/021_DBD_Mock_Session.t-43- # we must update the login failures, and lock the account
libdbd-mock-perl-1.58/t/021_DBD_Mock_Session.t:44: $dbh->do("UPDATE users SET login_failures = (login_failures + 1), locked = 1 WHERE user_id = $user_id"); return 'USER ACCOUNT LOCKED';
libdbd-mock-perl-1.58/t/021_DBD_Mock_Session.t-45- }
##############################################
libdbd-mock-perl-1.58/README.md-189- This feature is conceptually different from the `mock_can_connect` attribute
libdbd-mock-perl-1.58/README.md:190: of the `$dbh` in that it has a driver-wide scope, where `mock_can_connect`
libdbd-mock-perl-1.58/README.md:191: is handle-wide scope. It also only prevents the initial connection, any `$dbh`
libdbd-mock-perl-1.58/README.md-192- handles created prior to setting `mock_connect_fail` to true (`1`) will still
##############################################
libdbd-mock-perl-1.58/README.md-439- records stocked in the result set. So if your code/application makes use of the
libdbd-mock-perl-1.58/README.md:440: `$sth->rows` method for things like `UPDATE` and `DELETE` calls you
libdbd-mock-perl-1.58/README.md-441- should stock the result set like so:
##############################################
libdbd-mock-perl-1.58/README.md-487- more information on this, see the ["DBD::Mock::Session"](#dbd-mock-session) docs below. This
libdbd-mock-perl-1.58/README.md:488: attribute can also be used to remove the current session from the `$dbh`
libdbd-mock-perl-1.58/README.md-489- simply by setting it to `undef`.
##############################################
libdbd-mock-perl-1.58/README.md-522- `prepare` it will only increment for each `execute`. This allows it to be
libdbd-mock-perl-1.58/README.md:523: used over multiple `execute` calls in a single `$sth`. It's usage looks like
libdbd-mock-perl-1.58/README.md-524- this:
##############################################
libdbd-mock-perl-1.58/README.md-621-
libdbd-mock-perl-1.58/README.md:622: Currently the `mysql_insertid` attribute for `$dbh` and `$sth` are aliased
libdbd-mock-perl-1.58/README.md:623: to the `$dbh` attribute `mock_last_insert_id`.
libdbd-mock-perl-1.58/README.md-624-
##############################################
libdbd-mock-perl-1.58/README.md-626-
libdbd-mock-perl-1.58/README.md:627: Currently the `mariadb_insertid` attribute for `$dbh` and `$sth` are aliased
libdbd-mock-perl-1.58/README.md:628: to the `$dbh` attribute `mock_last_insert_id`.
libdbd-mock-perl-1.58/README.md-629-
##############################################
libdbd-mock-perl-1.58/README.md-749-
libdbd-mock-perl-1.58/README.md:750: Then `$sth->{mock_execution_history}` would be:
libdbd-mock-perl-1.58/README.md-751-
##############################################
libdbd-mock-perl-1.58/README.md-861-
libdbd-mock-perl-1.58/README.md:862:- **`is_executed( $yes_or_no )`** (Statement attribute `mock_is_executed`)
libdbd-mock-perl-1.58/README.md-863-
##############################################
libdbd-mock-perl-1.58/README.md-865-
libdbd-mock-perl-1.58/README.md:866:- **`is_finished( $yes_or_no )`** (Statement attribute `mock_is_finished`)
libdbd-mock-perl-1.58/README.md-867-
##############################################
libdbd-mock-perl-1.58/README.md-888-
libdbd-mock-perl-1.58/README.md:889:- **`bound_param( $param_num, $value )`**
libdbd-mock-perl-1.58/README.md-890-
libdbd-mock-perl-1.58/README.md:891: Sets bound parameter `$param_num` to `$value`. Returns the arrayref of
libdbd-mock-perl-1.58/README.md-892- currently-set bound parameters. This corresponds to the `bind_param` statement
##############################################
libdbd-mock-perl-1.58/README.md-968-`DBD::Mock` finds a session in the `mock_session` attribute, then it will
libdbd-mock-perl-1.58/README.md:969:pass the current `$dbh` and SQL statement to that `DBD::Mock::Session`. The
libdbd-mock-perl-1.58/README.md-970-SQL statement will be checked against the `statement` field in the current
##############################################
libdbd-mock-perl-1.58/README.md-996-
libdbd-mock-perl-1.58/README.md:997:- **`new ($session_name, @session_states)`**
libdbd-mock-perl-1.58/README.md-998-
libdbd-mock-perl-1.58/README.md:999: A `$session_name` can be optionally be specified, along with at least one
libdbd-mock-perl-1.58/README.md:1000: `@session_states`. If you don't specify a `$session_name`, then a default one
libdbd-mock-perl-1.58/README.md-1001- will be created for you. The `@session_states` must all be HASH references as
##############################################
libdbd-mock-perl-1.58/README.md-1003-
libdbd-mock-perl-1.58/README.md:1004:- **`verify_statement ($dbh, $SQL)`**
libdbd-mock-perl-1.58/README.md-1005-
libdbd-mock-perl-1.58/README.md:1006: This will check the `$SQL` against the current state's `statement` value, and
libdbd-mock-perl-1.58/README.md:1007: if it passes will add the current state's `results` to the `$dbh`. If for
libdbd-mock-perl-1.58/README.md-1008- some reason the `statement` value is bad, not of the prescribed type, an
##############################################
libdbd-mock-perl-1.58/README.md-1010-
libdbd-mock-perl-1.58/README.md:1011:- **`verify_bound_params ($dbh, $params)`**
libdbd-mock-perl-1.58/README.md-1012-
libdbd-mock-perl-1.58/README.md-1013- If the `bound_params` slot is available in the current state, this will check
libdbd-mock-perl-1.58/README.md:1014: the `$params` against the current state's `bound_params` value. Both number
libdbd-mock-perl-1.58/README.md-1015- of parameters and the parameters themselves must match, or an error will be
##############################################
libdbd-mock-perl-1.58/README.md-1202- property to be undef in this situation then set the
libdbd-mock-perl-1.58/README.md:1203: `$DBD::Mock::DefaultFieldsToUndef` flag to `1`.
libdbd-mock-perl-1.58/README.md-1204-
##############################################
libdbd-mock-perl-1.58/README.md-1289-
libdbd-mock-perl-1.58/README.md:1290:- Odd `$dbh` attribute behavior
libdbd-mock-perl-1.58/README.md-1291-
libdbd-mock-perl-1.58/README.md:1292: When writing the test suite I encountered some odd behavior with some `$dbh`
libdbd-mock-perl-1.58/README.md-1293- attributes. I still need to get deeper into how DBD's work to understand what