All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
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: Mon, 26 Apr 2010 05:07:18 +0800	[thread overview]
Message-ID: <201004260507.19020.lindner_marek@yahoo.de> (raw)
In-Reply-To: <201004252136.25395.adebex@gmail.com>


Hi,

> 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.

I tend to agree with Andrew: If you wish to secure patient data transfers end-
to-end encryption is probably what you are looking for (e.g. SSL). But 
"ensuring security" is a very broad term which we hear quite often. Please 
check our FAQ: http://www.open-mesh.org/wiki/FAQ

Cheers,
Marek

  parent reply	other threads:[~2010-04-25 21:07 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
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 [this message]
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=201004260507.19020.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.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 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.