From: bruno randolf <bruno@thinktube.com>
To: b.a.t.m.a.n@open-mesh.net
Cc: Marek Lindner <lindner_marek@yahoo.de>
Subject: Re: [B.A.T.M.A.N.] AHdemo mode
Date: Thu, 10 Apr 2008 15:04:48 +0900 [thread overview]
Message-ID: <200804101504.48485.bruno@thinktube.com> (raw)
In-Reply-To: <200804101222.16445.lindner_marek@yahoo.de>
On Thursday 10 April 2008 13:22:16 Marek Lindner wrote:
> IMHO the olsr secure plugin idea has a good intention but the concept is
> broken. There are several aspects:
> - As long as only a single instance (one admin) knows the key everything is
> fine. But every node joining the mesh will need that key. Either the admin
> has a _lot_ of freetime or you have to hand out the key. In the later case
> check Ebay from to time to time to find out about the value of your key.
still that can be better than no security at all...
> ;-) - Furthermore, batman is used for _community_ meshing. Everybody should
> be able to join quickly ...
i basically agree, but some people might like to set up a more controlled
environment. even in a community network this might be useful at times, for
example if you want to set up a backbone network.
one way to solve this without a static key which has to be known to all nodes
is using a public key infrastructure (PKI) with a certificate authority (CA).
the clients can generate their own private and public keys and send the
public key to be signed by the CA. that could go hand in hand with adding
their nodes to a map and accepting some basic agreement (pico peering). after
it has been signed they could start using encryption for an extra level of
mesh security.
> - You give your users a FALSE impression of security: "We have the secure
> plugin enabled - we are secure!". Still everybody can sniff the data, man
> in the middle, etc
yes people have to understand that only the mesh protocol will be encrypted,
not the data.
> - Encryption on an embedded device like a router is a performance killer if
> the encryption is not done in the hardware itself.
it's not too bad as long as the bandwith is low, as it would be the case with
protocol traffic.
> - Most important: Nothing is better than end to end encryption /
> authentication / authorization.
that's true, but it doesn't help if the underlying mesh protocol can be
disturbed easily by un-authenticated nodes and your traffic never reaches the
other endpoint.
there are two different layers of adding authentication and encryption. one is
the mesh protocol itself the other one is end-to-end user encryption. both
are necessary if you want to make your network secure.
bruno
next prev parent reply other threads:[~2008-04-10 6:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 23:52 [B.A.T.M.A.N.] AHdemo mode GUSL
2008-04-10 0:52 ` Marek Lindner
2008-04-10 1:55 ` GUSL
2008-04-10 2:23 ` Vinay Menon
2008-04-10 4:22 ` Marek Lindner
2008-04-10 6:04 ` bruno randolf [this message]
2008-04-10 6:59 ` Vinay Menon
2008-04-11 7:48 ` Simon Wunderlich
2008-04-10 4:12 ` Marek Lindner
-- strict thread matches above, loose matches on Subject: below --
2008-04-10 9:41 Marek Lindner
2008-04-10 9:51 ` elektra
2008-04-11 18:30 ` Aaron Kaplan
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=200804101504.48485.bruno@thinktube.com \
--to=bruno@thinktube.com \
--cc=b.a.t.m.a.n@open-mesh.net \
--cc=lindner_marek@yahoo.de \
/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