From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Adding security on BATMAN-ADV
Date: Wed, 21 May 2014 20:18:38 +0200 [thread overview]
Message-ID: <20140521181838.GB7725@lunn.ch> (raw)
In-Reply-To: <CAEbDFcQS-f4zRCph0RVyXd9k953DiczGVS4k5TP4vFeio3GhSw@mail.gmail.com>
On Wed, May 21, 2014 at 10:30:08PM +0530, Krishnathiepan Rasanayagam wrote:
> Hi,
>
> We are trying to add authentication when nodes join the network. Like
> when other nodes start adding a node in their routing table. basically
> authenticating the node.
So some form of HMAC on the packets between peers, and only accept
them if you can verify the HMAC.
You say here routing tables. So you are trying to authenticate routing
information. You don't care about actual data carried over the mesh?
That is not authenticated?
> We like to do with Threshold cryptography for authenticating.
So you mean you want at least X peers to be able to authenticate a
peer before it is allowed to join the mesh? So how do you boot strap
the system when the mesh is first forming and you don't have X peers?
Andrew
next prev parent reply other threads:[~2014-05-21 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 13:19 [B.A.T.M.A.N.] Adding security on BATMAN-ADV Krishnathiepan Rasanayagam
2014-05-20 14:01 ` Andrew Lunn
2014-05-20 19:29 ` Krishnathiepan Rasanayagam
2014-05-20 21:41 ` Andrew Lunn
2014-05-21 17:00 ` Krishnathiepan Rasanayagam
2014-05-21 18:18 ` Andrew Lunn [this message]
2014-05-22 5:53 ` Krishnathiepan Rasanayagam
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=20140521181838.GB7725@lunn.ch \
--to=andrew@lunn.ch \
--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