Closed g4ze closed 1 month ago
is this still a draft?
Facing the same problem I did on domain check and knockpy.
I think this problem only arises when I'm implementing analysers that use new libraries or packages.
are you rebuilding the containers after you change the requirements?
yes I am, I'll redo it and update you again.
{
"assertions": [
{
"engine": "XVirus",
"asserts": "Benign"
},
{
"engine": "Jiangmin",
"asserts": "Benign"
},
{
"engine": "Qihoo 360",
"asserts": "Benign"
},
{
"engine": "SecureAge",
"asserts": "Benign"
},
{
"engine": "Filseclab",
"asserts": "Benign"
},
{
"engine": "Alibaba",
"asserts": "Benign"
},
{
"engine": "Crowdstrike Falcon ML",
"asserts": "Benign"
},
{
"engine": "Proton",
"asserts": "Benign"
},
{
"engine": "Electron",
"asserts": "Benign"
},
{
"engine": "DrWeb",
"asserts": "Benign"
},
{
"engine": "SecondWrite",
"asserts": "Benign"
},
{
"engine": "NanoAV",
"asserts": "Benign"
},
{
"engine": "ClamAV",
"asserts": "Benign"
},
{
"engine": "Ikarus",
"asserts": "Benign"
},
{
"engine": "RedDrip APT Scanner - RAS",
"asserts": "Benign"
}
],
"positives": 0,
"total": 15,
"PolyScore": 0.33460048640798623,
"sha256": "605bbe9256a3f1abffc8b09d011a25674e4fbd631d0f93694766f21190ae32e4",
"md5": "7598c0b3c9b830502a1103ccae2fab68",
"sha1": "091329d524469c468b5b2b1659ffac045b9880a0",
"extended_type": "ASCII text, with CRLF line terminators",
"first_seen": "2024-08-07T10:06:00.436896",
"last_seen": "2024-08-07T10:06:00.436896",
"permalink": "https://polyswarm.network/scan/results/file/605bbe9256a3f1abffc8b09d011a25674e4fbd631d0f93694766f21190ae32e4/54275927186401150"
}
lmk the migration sequence for once we are ready. Also i think the previous problem was something related to docker build cache and my ISP. All good now.
polyswarm -> knock so you can finish this while you are here
Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
i've updated the pr, kindly review. do check the TLP.
ah my bad! on it!
i think the free tier doesnt allow usage of ioc endpoints. hashes seem to be working tho.
oki, I think you can keep them both and we write in the analyzer description that that specific endpoint is for paid customers only. ty!
for hashes
there is an error in the CI, after that I'll merge it! great work!
seems gtg @mlodic
Description
Please include a summary of the change and link to the related issue.
Type of change
Please delete options that are not relevant.
Checklist
develop
dumpplugin
command and added it in the project as a data migration. ("How to share a plugin with the community")test_files.zip
and you added the default tests for that mimetype in test_classes.py.FREE_TO_USE_ANALYZERS
playbook by following this guide.url
that contains this information. This is required for Health Checks._monkeypatch()
was used in its class to apply the necessary decorators.MockUpResponse
of the_monkeypatch()
method. This serves us to provide a valid sample for testing.Black
,Flake
,Isort
) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf.tests
folder). All the tests (new and old ones) gave 0 errors.DeepSource
,Django Doctors
or other third-party linters have triggered any alerts during the CI checks, I have solved those alerts.Important Rules