From: "Marek Küthe" <m-k-mailling-list@mk16.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Authenticity of routing information in Batman
Date: Fri, 30 Jun 2023 14:46:23 +0200 [thread overview]
Message-ID: <20230630144623.238fe33e@parrot> (raw)
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
Hello,
I recently came across Batman Adv and the question arose in my mind
whether it is possible to authenticate the routing information exchange
- for example with HMAC as in babel. This would for example prevent
attacks where a malicious node says "I have the perfect route to the
destination!". I am not concerned with encryption or authentication of
the traffic, only of the routing information. Is there anything like
this in Batman (Adv)? If not, is it planned to implement something like
this? If there isn't, does anyone have an idea how something like this
could be done differently (in a different layer)?
I would be very happy to receive answers!
Greetings
Marek Küthe
--
Marek Küthe
m.k@mk16.de
er/ihm he/him
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-06-30 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 12:46 Marek Küthe [this message]
2023-07-03 8:55 ` Authenticity of routing information in Batman Marek Lindner
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=20230630144623.238fe33e@parrot \
--to=m-k-mailling-list@mk16.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).