Skip to content
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

Terminal Input Issues #882

Closed
TheTechromancer opened this issue Nov 29, 2023 · 3 comments
Closed

Terminal Input Issues #882

TheTechromancer opened this issue Nov 29, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@TheTechromancer
Copy link
Collaborator

TheTechromancer commented Nov 29, 2023

The current system for terminal input is very unstable. Even on medium-sized scans, the ability to change the verbosity or issue scan commands becomes completely broken. Also, the terminal is usually screwed up after a scan so that you can't see the characters you're typing. This occurs even on scans without sudo prompts.

EDIT: I suspect this might be caused by certain subprocesses like nmap or nuclei contending for the stdin file descriptor.

@TheTechromancer TheTechromancer added the bug Something isn't working label Nov 29, 2023
@TheTechromancer TheTechromancer self-assigned this Nov 29, 2023
@TheTechromancer
Copy link
Collaborator Author

Testing this tonight to see whether an individual module is responsible.

@TheTechromancer
Copy link
Collaborator Author

It's nmap.

@TheTechromancer
Copy link
Collaborator Author

Fixed in #946.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant