Linux iad1-shared-b7-18 6.6.49-grsec-jammy+ #10 SMP Thu Sep 12 23:23:08 UTC 2024 x86_64
Apache
: 67.205.6.31 | : 216.73.216.47
Cant Read [ /etc/named.conf ]
8.2.29
fernandoquevedo
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
README
+ Create Folder
+ Create File
/
usr /
local /
wp /
vendor /
wp-cli /
db-command /
features /
[ HOME SHELL ]
Name
Size
Permission
Action
db-check.feature
3.67
KB
-rw-r--r--
db-columns.feature
3.56
KB
-rw-r--r--
db-export.feature
2.49
KB
-rw-r--r--
db-import.feature
4.9
KB
-rw-r--r--
db-prefix.feature
224
B
-rw-r--r--
db-query.feature
3.14
KB
-rw-r--r--
db-search.feature
29.69
KB
-rw-r--r--
db-size.feature
5.96
KB
-rw-r--r--
db-tables.feature
5.95
KB
-rw-r--r--
db.feature
8.63
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : db-check.feature
Feature: Check the database Scenario: Run db check to check the database Given a WP install When I run `wp db check` Then STDOUT should contain: """ wp_cli_test.wp_users """ And STDOUT should contain: """ Success: Database checked. """ Scenario: Run db check with MySQL defaults to check the database Given a WP install When I run `wp db check --defaults` Then STDOUT should contain: """ wp_cli_test.wp_users """ And STDOUT should contain: """ Success: Database checked. """ Scenario: Run db check with --no-defaults to check the database Given a WP install When I run `wp db check --no-defaults` Then STDOUT should contain: """ wp_cli_test.wp_users """ And STDOUT should contain: """ Success: Database checked. """ Scenario: Run db check with passed-in options Given a WP install When I run `wp db check --dbuser=wp_cli_test` Then STDOUT should contain: """ Success: Database checked. """ When I run `wp db check --dbpass=password1` Then STDOUT should contain: """ Success: Database checked. """ When I run `wp db check --dbuser=wp_cli_test --dbpass=password1` Then STDOUT should contain: """ Success: Database checked. """ When I try `wp db check --dbuser=no_such_user` Then the return code should not be 0 And STDERR should contain: """ Access denied """ And STDOUT should be empty When I try `wp db check --dbpass=no_such_pass` Then the return code should not be 0 And STDERR should contain: """ Access denied """ And STDOUT should be empty When I try `wp db check --dbuser=wp_cli_test --verbose` Then the return code should be 0 And STDOUT should contain: """ Success: Database checked. """ # '--user' is ignored. When I try `wp db check --user=no_such_user` Then STDOUT should contain: """ Success: Database checked. """ # '--password' works, but MySQL may (depending on version) print warning to STDERR When I try `wp db check --password=password1` Then the return code should be 0 # Match STDERR containing "insecure" or empty STDERR. And STDERR should match /^(?:.+insecure.+|)$/ And STDOUT should contain: """ Success: Database checked. """ # Bad '--password' works in that it causes access fail. When I try `wp db check --password=no_such_pass` Then the return code should not be 0 And STDERR should contain: """ Access denied """ And STDOUT should be empty # '--dbpass' overrides '--password'. When I run `wp db check --dbpass=password1 --password=no_such_pass` Then STDOUT should contain: """ Success: Database checked. """ When I try `wp db check --dbpass=no_such_pass --password=password1` Then the return code should not be 0 And STDERR should contain: """ Access denied """ And STDOUT should be empty Scenario: MySQL defaults are available as appropriate with --defaults flag Given a WP install When I try `wp db check --defaults --debug` Then STDERR should match #Debug \(db\): Running shell command: /usr/bin/env (mysqlcheck|mariadb-check) %s# When I try `wp db check --debug` Then STDERR should match #Debug \(db\): Running shell command: /usr/bin/env (mysqlcheck|mariadb-check) --no-defaults %s# When I try `wp db check --no-defaults --debug` Then STDERR should match #Debug \(db\): Running shell command: /usr/bin/env (mysqlcheck|mariadb-check) --no-defaults %s#
Close