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

lack of isolation between running instances #999

Open
dogasantos opened this issue Dec 15, 2023 · 0 comments
Open

lack of isolation between running instances #999

dogasantos opened this issue Dec 15, 2023 · 0 comments

Comments

@dogasantos
Copy link

hi guys, just want to share a weird behavior I noticed
Perhaps this is something you're not aware of yet, or perhaps it might be a won't fix.

If you run multiple instances of amass using the same user on the same linux machine (different directories), you'll start to see results for all instances on all outputs.

example:
amass01 running on example01.com
amass02 running on example02.com
...
amass05 running on example05.com

After some time, results of amass05 will appear on each of those other instances. and outputs of those other instances will appear on amass05 and so on.

Not sure if this is memory isolation issue, but positive this is a problem

Hope this helps to find a bug
Ty

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant