This repository has been archived by the owner on Jul 9, 2022. It is now read-only.
Lockbit scraper fixed (now uses playwright) #74 #89
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the changes
Lockbit 2.0 now uses a ddos protection mechanism hence the regular http get method is no longer working.
As a workaround I have implemented the playwright Microsoft library which behaves as if a proper browser did the request.
Summary of the changes:
lockbit.py
: replaced the use of requests by playwrightrequirements.txt
: added playwrightI have also upgraded at the top of the Dockerfile from
python3.9-buster
topython3.10-bullseye
.Related issue(s)
It fixes Issue #74
Note that the scraping engine for lockbit has been left untouched as it is still perfectly working. Only the web page retrieval method has been altered.
How was it tested?
docker-compose build app
docker-compose up --abort-on-container-exit