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.

Sign up for GitHub

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

Option "-http-addr" is not working in replay #195

Closed
juanmera opened this issue Nov 27, 2022 · 1 comment · Fixed by #204
Closed

Option "-http-addr" is not working in replay #195

juanmera opened this issue Nov 27, 2022 · 1 comment · Fixed by #204
Assignees
@tarunKoyalwar
Labels
Priority: Medium This issue may be useful, and needs some attention. Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Milestone
proxify v0.0.9

Comments

@juanmera
Copy link

Proxify version:

This is actually for the replay tool but the current version of proxify is 0.0.8

Current Behavior:

replay -output logs -http-addr ":10080" is returning the error [FTL] Could not listen and serve: listen tcp :80: bind: permission denied

Expected Behavior:

replay -output logs -http-addr ":10080" should listen on port 10080

Steps To Reproduce:

  1. Run replay -output logs -http-addr ":10080"
  2. See error [FTL] Could not listen and serve: listen tcp :80: bind: permission denied

Anything else:

In https://github.com/projectdiscovery/proxify/blob/master/cmd/replay/replay.go#L88 the ":80" is hardcoded but options.HTTPListenerAddress should be used.
@juanmera juanmera added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Nov 27, 2022
@Mzack9999 Mzack9999 added the Priority: Medium This issue may be useful, and needs some attention. label Dec 19, 2022
@tarunKoyalwar tarunKoyalwar self-assigned this Dec 21, 2022
@tarunKoyalwar tarunKoyalwar mentioned this issue Dec 22, 2022
Merged
4 tasks
@tarunKoyalwar tarunKoyalwar linked a pull request Dec 22, 2022 that will close this issue
replay: remove hardcoded listen address #204
Merged
4 tasks
@ehsandeep ehsandeep added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Dec 22, 2022
@ehsandeep
Copy link
Member

@juanmera thank you for flagging this, this is now fixed in the dev version.

@ehsandeep ehsandeep added this to the proxify v0.0.9 milestone Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tarunKoyalwar tarunKoyalwar

Labels
Priority: Medium This issue may be useful, and needs some attention. Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Milestone
proxify v0.0.9
Development

Successfully merging a pull request may close this issue.

replay: remove hardcoded listen address projectdiscovery/proxify
4 participants
@juanmera @ehsandeep @Mzack9999 @tarunKoyalwar