doomedraven

many of the feeds can be fetched from github, i have the firehol feed, it has all in 1 of them, so we won't process old data over and over

https://github.com/yeti-platform/yeti/pull/448 this will add support for firehol, badip.com, binary defense

after check all this feeds a lot of them are dead, the rest uf working feeds, requires check last-modified header ``` https://lists.blocklist.de/lists/22.txt http://www.cert.at/static/downloads/data/conficker/all_domains.txt http://www.chaosreigns.com/iprep/bind_zone.txt http://charles.the-haleys.org/ssh_dico_attack_hdeny_format.php/hostsdeny.txt http://cinsscore.com/list/ci-badguys.txt http://rules.emergingthreats.net/blockrules/compromised-ips.txt host-file feed of...

done https://github.com/yeti-platform/yeti/pull/426

user groups is done. please review the PR

yes :)

from what i have tracked down the problem is here https://github.com/yeti-platform/yeti/blob/master/core/observables/observable.py#L183 it first check type and then normalyze ``` def clean(self): if self.check_type(self.value): self.normalize() else: raise ObservableValidationError( "'{}' is not...

yes its regex, well thats hard, as if you add new space, it can start match some extra things just after url so not sure

the problem is to force every yeti user to do that, which you understand won't work maybe something like? next instead of the code in this pr? ``` if self.__class__.__name__...

or wouldnot it be better first call normalize and then validate? as now it don't in "wrong" order, but we already know type on that stage