From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Mon, 26 Apr 2010 05:07:18 +0800 References: <201004252136.25395.adebex@gmail.com> In-Reply-To: <201004252136.25395.adebex@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201004260507.19020.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] Security & node authentication in BATMAN network Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking 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