close
The Wayback Machine - https://web.archive.org/web/20200918155212/https://github.com/RustScan/RustScan/issues/222
Skip to content

/ RustScan

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[VOTE] Using flags for addresses vs positional arguments #222

Open
bee-san opened this issue Sep 15, 2020 · 0 comments
Open

[VOTE] Using flags for addresses vs positional arguments #222

bee-san opened this issue Sep 15, 2020 · 0 comments
Labels
good first issue help wanted question

Comments

@bee-san
Copy link
Collaborator

@bee-san bee-san commented Sep 15, 2020

We have a problem which has 2 possible solutions.

  1. We create a custom parser for positional arguments so you can do rustscan 127.0.0.1,google.com
  2. We create a flag such as rustscan -a 127.0.0.1,google.com

The 2nd option would solve a significant amount of bugs, whereas the 1st option also solves the bugs but adds a lot more complexity to the program. See #211 for more info.

Question: Would you be okay with using a flag to specify addresses?
@issue-label-bot issue-label-bot bot added the question label Sep 15, 2020
@RustScan RustScan deleted a comment from issue-label-bot bot Sep 15, 2020
@bee-san bee-san pinned this issue Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue help wanted question
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
@bee-san
You can’t perform that action at this time.