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

Feature Request: Save Beacon #9

Open
ssnkhan opened this issue Apr 29, 2021 · 2 comments
Open

Feature Request: Save Beacon #9

ssnkhan opened this issue Apr 29, 2021 · 2 comments

Comments

@ssnkhan
Copy link

ssnkhan commented Apr 29, 2021

Thank you for the great update!

Now that the script supports configuration parsing directly via a URL, could a --save option be added to allow the script to save a copy of the beacon locally please? The file could be saved/named as its md5. Thanks for your consideration!

@0xflux
Copy link

0xflux commented Sep 8, 2022

@ssnkhan Hey! I have just modified the code to do something similar, I'm saving both the decrypted beacon as a blob, and saving a file as JSON. Saving the file as a JSON dump is done by calling from another script using subprocess(), however I have modified this script to dump the raw bytes. I might fork it if you are interested, it's only a small amendment!

@0xflux
Copy link

0xflux commented Sep 8, 2022

Actually, I might fork it and add the process of saving the json as a file.

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

2 participants