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.] Security & node authentication in BATMAN network
Date: Sun, 25 Apr 2010 21:53:17 +0200 [thread overview]
Message-ID: <20100425195317.GA3734@lunn.ch> (raw)
In-Reply-To: <201004252136.25395.adebex@gmail.com>
> 1. Does BATMAN provide any method of *authenticating* nodes?
> As I've said earlier, sometimes transferred data will be highly
> sensitive (for example: information of patients health in hospital),
> so it's absolutely critical to not allow leaking this information.
For this sort of application you need end-to-end security. That is,
your end devices authenticate each other, probably using
certificates. They then negotiate a key and then encrypt all the
traffic end-to-end. It does not matter if the data leaks, since its
not practical for anybody to decode it. You then don't care about you
mesh, its just an untrusted data pipe from A to B.
You should probably get a good book on security and learn all about
what Alice and Bob need to do.
The mesh itself is not important. You cannot trust it, hence its not
important.
Andrew
next prev parent reply other threads:[~2010-04-25 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 19:36 [B.A.T.M.A.N.] Security & node authentication in BATMAN network Adrian Byszuk
2010-04-25 19:53 ` Andrew Lunn [this message]
2010-04-25 20:08 ` Sven Eckelmann
2010-04-25 20:13 ` Daniel Golle
2010-04-25 21:14 ` Marek Lindner
2010-04-25 23:24 ` Adrian Byszuk
2010-04-26 5:14 ` Andrew Lunn
2010-04-25 21:07 ` Marek Lindner
2010-04-25 22:01 ` Simon Wunderlich
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=20100425195317.GA3734@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.