public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: location@lists.ipfire.org
Subject: [PATCH 2/4] override-xd: Initial commit
Date: Fri, 03 Dec 2021 12:28:21 +0100	[thread overview]
Message-ID: <d1886352-4c55-936e-a754-0c5f19d03def@ipfire.org> (raw)
In-Reply-To: <3541e51b-9697-1058-9997-c72e2e9bdd5b@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1821 bytes --]

Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
 overrides/override-xd.txt | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 overrides/override-xd.txt

diff --git a/overrides/override-xd.txt b/overrides/override-xd.txt
new file mode 100644
index 0000000..8318b49
--- /dev/null
+++ b/overrides/override-xd.txt
@@ -0,0 +1,27 @@
+#
+# override-xd [.txt]
+#
+# This file contains Autonomous Systems and IP networks strongly believed or proofed to be hostile,
+# posing a _technical_ threat against libloc users in general and/or IPFire users in particular.
+#
+# libloc neither was intended to be an "opinionated" database, nor should it become that way. Please
+# refer to commit 69b3d894fbee6e94afc2a79593f7f6b300b88c10 for the rationale of implementing a special
+# flag for hostile networks.
+#
+# Technical threats cover publicly routable network infrastructure solely dedicated or massively abused to
+# host phishing, malware, C&C servers, non-benign vulnerability scanners, or being used as a "bulletproof"
+# hosting space for cybercrime infrastructure.
+#
+# This file should not contain short-lived threats being hosted within legitimate infrastructures, as
+# libloc it neither intended nor suitable to protect against such threats in a timely manner - by default,
+# clients download a new database once a week.
+#
+# Networks posing non-technical threats - i. e. not covered by the definition above - must not be listed
+# here.
+#
+# Improvement suggestions are appreciated, please submit them as patches to the location mailing
+# list. Refer to https://lists.ipfire.org/mailman/listinfo/location and https://wiki.ipfire.org/devel/contact
+# for further information.
+#
+# Please keep this file sorted.
+#
-- 
2.26.2

  reply	other threads:[~2021-12-03 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03 11:28 [PATCH 1/4] override-other: Clarify file description and fix typos Peter Müller
2021-12-03 11:28 ` Peter Müller [this message]
2021-12-03 11:28   ` [PATCH 3/4] override-other: Regular batch of various overrides Peter Müller
2021-12-03 11:28     ` [PATCH 4/4] overrides-xd: Add ASNs of Dutch bulletproof ISP conglomerate "Ecatel" Peter Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d1886352-4c55-936e-a754-0c5f19d03def@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=location@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox