Open s7x opened 1 year ago
I'm 99% sure that this issue is due to a bug in pywebcopy
, upon which this feature depends. I can't be certain since the URL you submitted is redacted, so I had to do my best using what I believe to be a similar sign-in URL for the same site / domain. Here's what I got when trying to clone the site using pywebcopy directly:
Reproduction Command:
python3 -m pywebcopy -p --url https://accounts.google.com/v3/signin/identifier\?continue\=[..snip..] --location ./test --bypass_robots 2>&1 | grep ERROR
Output:
ERROR - pywebcopy.elements.GenericResource:373 - Status Code [<404>] received from the server [https://accounts.google.com/v3/signin/]
ERROR - pywebcopy.schedulers.Scheduler:110 - Invalid url schema: [data] for url: [data:image/svg+xml;charset=UTF-[..snip..]
ERROR - pywebcopy.elements.JSResource:373 - Status Code [<404>] received from the server [https://www.gstatic.com/_/mss/boq-identity=[..snip..]
ERROR - pywebcopy.schedulers.Scheduler:187 - No connection adapters were found for 's://g'
ERROR - pywebcopy.elements.JSResource:373 - Status Code [<404>] received from the server [..snip..]
ERROR - pywebcopy.schedulers.Scheduler:182 - Scheduler ConnectionError Failed to retrieve resource from [..snip..]
ERROR - pywebcopy.schedulers.Scheduler:182 - Scheduler ConnectionError Failed to retrieve resource from [..snip..]
Can you do me a favor and re-run the command shown above using your unredacted URL? Don't worry about pasting the console output, just let me know if you get similar error messages from pywebcopy
. If you do, I'll open an issue with pywebcopy
.
Describe the bug
When attempting to create a template of a login page, the script always fail with the following error:
A traceback is present in the wskeylogger.log file mentioning an InvalidSchema :
In conjunction with a lot of errors of this type:
I suppose most of them can be disregarded, except for the stack trace?
The last thing to mention is, in addition to not properly create the template, the 2 last lines of the log file are these (separated with a newline for readability):
To Reproduce
Steps to reproduce the behavior:
sudo eaphammer --create-template --name google --url 'https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fwww.google.com%2F&[REDACTED]' --debug
Expected behavior
A proper clone of the login page is created and available with the
--list-template
flag.Screenshots
Command string(s) used
EAPHammer verbose output (using the --debug flag)
EAPHammer Version (./eaphammer --version)
OS (the OS from which you are running EAPHammer)
Thanks for your help!