kdb5_util could issue an unexplained error if a command argument
matched a command name, such as when trying to load a dump file named
"dump". It could also mysteriously work if the command name and its
arguments were misordered, such as "kdb5_util kdb.dump load".
In the main option loop, build cmd_argv without special-casing command
names; then look up cmd_argv[0] after the loop.
ticket: 8806
exit(1);
}
memset(cmd_argv, 0, sizeof(char *)*argc);
- cmd_argc = 1;
+ cmd_argc = 0;
argv++; argc--;
while (*argv) {
manual_mkey = TRUE;
global_params.mkey_from_kbd = 1;
global_params.mask |= KADM5_CONFIG_MKEY_FROM_KBD;
- } else if (cmd_lookup(*argv) != NULL) {
- if (cmd_argv[0] == NULL)
- cmd_argv[0] = *argv;
- else
- usage();
} else {
cmd_argv[cmd_argc++] = *argv;
}
if (cmd_argv[0] == NULL)
usage();
+ cmd = cmd_lookup(cmd_argv[0]);
+ if (cmd == NULL)
+ usage();
if( !util_context->default_realm )
{
"while setting up enctype %d", master_keyblock.enctype);
}
- cmd = cmd_lookup(cmd_argv[0]);
if (cmd->opendb && open_db_and_mkey())
return exit_status;