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

Whitelisting UUIDs for reverse_tcp_uuid handlers #5975

Closed
silverqx opened this issue Sep 14, 2015 · 6 comments
Closed

Whitelisting UUIDs for reverse_tcp_uuid handlers #5975

silverqx opened this issue Sep 14, 2015 · 6 comments
Labels
attic Older submissions that we still want to work on again confirmed Issues confirmed by a committer meterpreter payload

Comments

@silverqx
Copy link

reverse_tcp's handlers doesn't contain IgnoreUnknownPayloads setting.

@silverqx silverqx changed the title Whitelisting UUIDs for reverse_tcp Whitelisting UUIDs for reverse_tcp handlers Sep 14, 2015
@hdm
Copy link
Contributor

hdm commented Sep 14, 2015

Updating the description to clarify that this should be for the reverse_tcp_uuid handlers.

@hdm hdm changed the title Whitelisting UUIDs for reverse_tcp handlers Whitelisting UUIDs for reverse_tcp_uuid handlers Sep 14, 2015
@bcook-r7
Copy link
Contributor

This is similar to issue #5986 , or did I misinterpret it?

@hdm
Copy link
Contributor

hdm commented Sep 21, 2015

@bcook-r7 A little different; SSL pinning is for whether Meterpreter trusts Metasploit, UUIDs are for whether Metasploit trusts a given Meterpreter (or stage).

@silverqx
Copy link
Author

@hmoore-r7 Exactly as wrote.

@github-actions
Copy link

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

@github-actions github-actions bot added the Stale Marks an issue as stale, to be closed if no action is taken label Jan 18, 2021
@dwelch-r7 dwelch-r7 added confirmed Issues confirmed by a committer and removed Stale Marks an issue as stale, to be closed if no action is taken labels Jan 18, 2021
@adfoster-r7 adfoster-r7 added the attic Older submissions that we still want to work on again label Jun 6, 2023
@github-actions
Copy link

github-actions bot commented Jun 6, 2023

Thanks for your contribution to Metasploit Framework! We've looked at this issue, and unfortunately we do not currently have the bandwidth to prioritize this issue.

We've labeled this as attic and closed it for now. If you believe this issue has been closed in error, or that it should be prioritized, please comment with additional information.

@github-actions github-actions bot closed this as completed Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
attic Older submissions that we still want to work on again confirmed Issues confirmed by a committer meterpreter payload
Projects
None yet
Development

No branches or pull requests

5 participants