shell >/etc/init.d/mysql stop shell >/etc/init.d/mysql start --skip-grant-tables Which additional argument makes this operation safer?

Question

Options

• A-old-passwords, to start MySQL to use the old password format while running without the grant tables.
• B-reset-grant-tables, to start the server with only the mysql database accessible.
• C-read-only, to set all data to read-only except for super users
• D-skip-networking, to prohibit access from remote locations

• A
  5% (2)
• B
  3% (1)
• C
  11% (4)
• D
  82% (31)

Explanation

Starting MySQL with --skip-grant-tables disables all authentication, meaning anyone who can reach the server gets unrestricted root-level access - so adding --skip-networking prevents TCP/IP connections entirely, restricting access to local Unix socket connections only and eliminating the remote exploitation risk.

Why the distractors are wrong:

• A (--old-passwords) only changes the password hashing algorithm; it adds zero security when grant tables are already disabled.
• B (--reset-grant-tables) is not a real MySQL argument - it's a fabricated, plausible-sounding distractor.
• C (--read-only) blocks writes for non-super users, but --skip-grant-tables effectively grants everyone super user privileges, so this protection is bypassed anyway - and defeats the purpose of the operation (e.g., resetting a password requires a write).

Memory tip: Think of it as "I unlocked the front door (skipped grants), so I must bolt the gate (skip networking) to keep outsiders from walking in." The two flags are a standard paired recipe for safely resetting a MySQL root password.

No community discussion yet for this question.