How the Zenmap command line should work
Ideally, this is how scanning in Zenmap should work.
- The user should be able to enter a command with a typed command line, using a command constructor, or from a profile.
- Command lines should be able to be constructed with an assistant like the current profile editor. The constructed command line would go right in the box, not in a new profile.
- The way to create a new profile is to build a command line (by just typing it or through the constructor) and then save it as a profile. Similarly a profile is modified by selecting the profile, editing the command line, and saving it again.
- However a command line was created (by typing or through the constructor), it can be edited by either method. That is, if you type in a command you can go back and modify it by clicking buttons.
- A scan profile is optional. Typing in a command does not associate a profile with the scan. If you set a command line from a profile and then edit it, the scan should not be associated with a profile.
- The final say for how a command runs is the command line string, not the profile specification. When a scan is loaded from a file, the options that are shown are those loaded from the command line in the file, not from the stored profile name.