9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "LiteStar numnums" <litestar@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] OT: the simplest public key encryption code...
Date: Wed,  4 Oct 2006 11:49:46 -0400	[thread overview]
Message-ID: <283f5df10610040849s13446537ke08df0d6f214e9a3@mail.gmail.com> (raw)
In-Reply-To: <0268aca8a93ae163523c43f0c7addca9@quintile.net>

[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]

TEA and XTEA are really, really simple and XTEA is resonably secure.
XXTEA & Block TEA have weaknesses, but XTEA should be simple enough &
fast enough for an embedded system.
Good Luck,
 -- Sztefan

http://en.wikipedia.org/wiki/XTEA
http://en.wikipedia.org/wiki/Tiny_Encryption_Algorithm

On 10/4/06, Steve Simon <steve@quintile.net> wrote:
>
> I ask here as those who read this list have an understanding of the word
> simple.
>
> I am after some very simple public key encryption code which I intend to
> use to
> encrypt the md5 of a license file on an embedded system - so in needs to
> be
> really small and simple.
>
> I am tempeted to use the plan9 RSA code, but is there somthing else even
> simpler
> about? Perhaps less secure than RSA but stronger than a password embedded
> in
> the code, XORed with 0xdeadbeef :-)
>
> Anyone seen anything on the net?
>
> -Steve
>



-- 
If work and leisure are soon to be subordinated to this one utopian
principle -- absolute busyness -- then utopia and melancholy will come to
coincide: an age without conflict will dawn, perpetually busy -- and without
consciousness.

-- Günter Grass

[-- Attachment #2: Type: text/html, Size: 1604 bytes --]

  reply	other threads:[~2006-10-04 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-04 12:00 Steve Simon
2006-10-04 15:49 ` LiteStar numnums [this message]
2006-10-04 17:29   ` Steve Simon
2006-10-04 17:41     ` LiteStar numnums
2006-10-06  7:51       ` bituman

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=283f5df10610040849s13446537ke08df0d6f214e9a3@mail.gmail.com \
    --to=litestar@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).