All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Byszuk <adebex@gmail.com>
To: "B.A.T.M.A.N. Mailing List" <b.a.t.m.a.n@lists.open-mesh.org>
Subject: [B.A.T.M.A.N.] Security & node authentication in BATMAN network
Date: Sun, 25 Apr 2010 21:36:25 +0200	[thread overview]
Message-ID: <201004252136.25395.adebex@gmail.com> (raw)

Hello,

I'm currently working on project (part of my Bachelor work) which will use to 
transfer very sensitive data over the network, and I'd like to use mesh 
networks to transfer this data. Additionally, it should also be possible for 
"normal people" to connect to this network (e.g. to surf internet). 
Preliminary, I've chosen BATMAN to build this network. But I've got a few 
questions regarding security of this solution:

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. I can imagine situation when 
some fake nodes claim "Hey, I'm the server collecting this data"...
I think this is also important when someone would try to destroy our mesh 
network by placing some fake nodes in it.
2. If point nr one isn't possible, maybe there is some other way to ensure 
security? I don't know too much about security or cryptography, but I can 
think of solutions such as openVPN or IPsec.

Generally, the goal is to assert security of transmitting some data *without* 
losing open characteristics of mesh network.

I will very thankful for any answers.

Kind regards,
Adrian

             reply	other threads:[~2010-04-25 19:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-25 19:36 Adrian Byszuk [this message]
2010-04-25 19:53 ` [B.A.T.M.A.N.] Security & node authentication in BATMAN network Andrew Lunn
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=201004252136.25395.adebex@gmail.com \
    --to=adebex@gmail.com \
    --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.