Skip to content

L
libloc
Switch branch/tag
  1. 25 Feb, 2022 1 commit
  3. 16 Feb, 2022 1 commit
  5. 11 Feb, 2022 3 commits
  7. 02 Jan, 2022 4 commits
  9. 13 Dec, 2021 4 commits
  11. 23 Nov, 2021 3 commits
  13. 20 Nov, 2021 4 commits
  15. 02 Nov, 2021 2 commits
    • Peter Müller's avatar
      location-importer.in: Add Spamhaus DROP lists · 69b3d894
      Peter Müller authored 
      A while ago, it was discussed whether or not libloc should become an
"opinionated database", i. e. including any information on a network's
reputation.

In general, this idea was dismissed as libloc is neither intended nor
suitable for such tasks, and we do not want to make (political?)
decisions like these for various reasons. All we do is to provide a
useful location database in a neutral way, and leave it up to our users
on how to react on certain results.

However, there is a problematic area. Take AS55303 as an example: We
_know_ this is to be a dirty network, tampering with RIR data and
hijacking IP space, and strongly recommend against processing any
connection originating from or directed to it.

Since it appears to be loaded with proxies used by miscreants for
abusive purposes, all we can do at the time of writing is to flag it
as "anonymous proxy", but we lack possibility of telling our users
something like "this is not a safe area". The very same goes for known
bulletproof ISPs, IP hijackers, and so forth.

This patch therefore suggests to populate the "is_drop" flag introduced
in libloc 0.9.8 (albeit currently unused in production) with the
contents of Spamhaus' DROP lists (https://www.spamhaus.org/drop/), to
have at least the baddest of the bad covered. The very same lists are,
in fact, included in popular IPS rulesets as well - a decent amount of
IPFire users is therefore likely to have them already enabled, but in a
very costly way.

It is not planned to go further, partly because there is no other feed
publicly available, which would come with the same intention,
volatility, and FP rate.

The third version of this patch makes use of an auxiliary function to
sanitise ASNs, hence avoiding boilerplate code, and treats any line
starting with a semicolon as a comment, which should be sufficient.
Further, extracting ASNs from the ASN-DROP feed is done in a more clear
way, avoiding code snippets hard to read.
Signed-off-by: default avatarPeter Müller <peter.mueller@ipfire.org>
Signed-off-by: default avatarMichael Tremer <michael.tremer@ipfire.org>
      69b3d894
    • Peter Müller's avatar
      location-importer: Introduce auxiliary function to sanitise ASNs · 43fe570c
      Peter Müller authored 
      The third version of this patch does this in an even more Pythonic way.
Signed-off-by: default avatarPeter Müller <peter.mueller@ipfire.org>
Signed-off-by: default avatarMichael Tremer <michael.tremer@ipfire.org>
      43fe570c
  17. 25 Oct, 2021 1 commit
  19. 11 Oct, 2021 1 commit
  21. 30 Sep, 2021 13 commits
  23. 23 Sep, 2021 1 commit
  25. 21 Sep, 2021 1 commit
  27. 04 Sep, 2021 1 commit
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7