Alexandre Dulaunoy
Alexandre Dulaunoy
I see. Why don't use sticky session on the reverse proxies/load balancers? but how do you load-balancing between the kvrocks database? I won't work as is with the current design...
Does the crawler work if you submit manually an onion address to crawl?
@deadbits It sounds like a great idea. Don't hesitate to PR even a beta version. We would be glad to review it and integrate it.
Following a discussion @FafnerKeyZee the idea is to simply trigger the delete based: - Size of the underlying dataset (if reaching a certain level) - how much space is free...
Another option (more complex) and might generate some false-positive: https://github.com/dxa4481/truffleHog but entropy analysis is maybe under used in AIL.
Maybe a better approach would be to squeeze the archive in squashfs as mentioned in [Squashfs As A Forensic Container](https://www.foo.be/2017/01/Squashfs_As_A_Forensic_Container). (warning self ref ;-)
https://github.com/miso-belica/sumy other summarizers
It's a good idea. CFR are usually related to https://www.cfr.org/cyber-operations/ but we could make an official meta field called `vulnerabilities-exploited` to include the information with the list of CVEs.
If you have a 403 error, it’s a perm issue and not really an issue with PyMISP.
The explanation is in your screenshot... "PyMISP is not defined" ;-)