All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arif Hossain <aftnix@gmail.com>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel <netfilter-devel@vger.kernel.org>,
	nefilter@vger.kernel.org
Subject: Re: CRYPT target patch for newer kernel ?
Date: Wed, 08 Aug 2012 19:53:04 +0600	[thread overview]
Message-ID: <1344433984.4763.28.camel@localhost> (raw)
In-Reply-To: <alpine.LNX.2.01.1208081535440.857@frira.zrqbmnf.qr>

On Wed, 2012-08-08 at 15:41 +0200, Jan Engelhardt wrote:
> On Wednesday 2012-08-08 14:25, Arif Hossain wrote:
<snip>
> Complicated? No, not at all. http://inai.de/2008/02/24
> Heavyweight? Neither. The RSS is ~5 MB, most of which is pretty much
> glibc anyway.
> 

If clients are mainly embedded devices, and most of the time, all we can
do is to install a software on them, then is it feasible to use IPSEC? 

At this moment we are including the cryptography in the software we
provide for them, and many low end mobile devices has severe memory
limitation. 

Just for an example, we used tls for only the initial session
establishment, not the original data, and it proved very inefficient so
we had to abandon the thing completely.

The limitations of clinet devices forces us to use a very lightweight
and easy to implement (so that we can implement it in the limited
environment present in client devices) algorithms.

> --
> To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2012-08-08 14:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 12:25 CRYPT target patch for newer kernel ? Arif Hossain
2012-08-08 13:41 ` Jan Engelhardt
2012-08-08 13:53   ` Arif Hossain [this message]
2012-08-08 14:15     ` Jan Engelhardt
2012-08-08 14:15       ` Arif Hossain
2012-08-08 15:34         ` Jan Engelhardt
2012-08-08 15:41           ` Arif Hossain
2012-08-08 16:06             ` Jan Engelhardt

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=1344433984.4763.28.camel@localhost \
    --to=aftnix@gmail.com \
    --cc=jengelh@inai.de \
    --cc=nefilter@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.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.