All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Stefan Schmidt <stefan@osg.samsung.com>
Cc: Simon Vincent <simon.vincent@xsilon.com>, linux-wpan@vger.kernel.org
Subject: Re: The 802.15.4 Security Layer
Date: Fri, 26 Jun 2015 13:20:25 +0200	[thread overview]
Message-ID: <20150626112024.GC10816@omega> (raw)
In-Reply-To: <20150626102405.GB10816@omega>

status update:

Phoebe meant do 1:1 what iptables does, this means:

1. Implement all interface cmds to iwpan.
2. The config file are only per line separated arguments of iwpan.
3. we implement a store/restore for that fileformat.

Okay this is much easier to implement and we should do that for the
first. I think that the order is important for setup such setting, so we
have internal dependencies which need to be setup at first. Then we need
to care about that.

At first a new file format is not necessary, later we can think about to
introduce such file format _maybe_ for a better handling.

This is just "Keep it simple and stupid" and (short, safe, whatever).

- Alex

  reply	other threads:[~2015-06-26 11:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 12:31 The 802.15.4 Security Layer Alexander Aring
2015-06-18 15:42 ` Stefan Schmidt
2015-06-18 15:58   ` Simon Vincent
2015-06-18 19:43     ` Stefan Schmidt
2015-06-23 15:34       ` Simon Vincent
2015-06-23 16:00         ` Simon Vincent
2015-06-24 10:00         ` Alexander Aring
2015-06-24 14:01           ` Alexander Aring
2015-06-26  8:56             ` Simon Vincent
2015-06-26  9:32               ` Alexander Aring
2015-06-26  9:45                 ` Stefan Schmidt
2015-06-26  9:58                   ` Alexander Aring
2015-06-26 10:14                     ` Stefan Schmidt
2015-06-26 10:24                       ` Alexander Aring
2015-06-26 11:20                         ` Alexander Aring [this message]
2015-06-21 21:12 ` Alexander Aring
2015-06-22 12:33   ` Phoebe Buckheister
2015-06-23 11:03     ` Alexander Aring
2015-06-23 12:46       ` Phoebe Buckheister

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=20150626112024.GC10816@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=simon.vincent@xsilon.com \
    --cc=stefan@osg.samsung.com \
    /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.