Re: Release 1.1 (beta) of my AES implementation

From: Mok-Kong Shen (mok-kong.shen_at_t-online.de)
Date: 06/25/03 

Date: Wed, 25 Jun 2003 17:55:24 +0200

Tom St Denis wrote:
>

> So what did you have in mind?
>
> #include "aes.c"
> #include "sha1.c"
> #include "...."
>
> ???

Exactly. (Unfortunately.)
 
> You're not going to get any users [re: bug finders] that way.

I am not sure of that. In my past experience lots of
people program that way.

> > I can think that a candidate application of my code
> > would be doing something like:
> >
> > read a block from input file to aesin;
> > aesprocess();
> > write aesout to output file;
> >
> > There is nothing to fork, isn't it?
>
> fork does not a thread make. fork makes processes [hint: there is a
> difference].
>
> If an application is threaded the global variable share the same
> location in memory. If two threads wanted to use AES simultaneously
> they could not with your code.
>
> Want a very realistic application of this?
>
> Sure. Sony Computer Entertainment of America [SCEA], who uses
> LibTomCrypt for their PC and PS2 development intends to use it to
> encrypt packets over UDP/IP going in both directions. They have
> contacted me about several ideas for handling UDP traffic. I think
> their idea is to spawn two threads for each direction and apply the
> cipher at the outgoing/ingoing edges. Anyways, the fact that LTC is
> thread safe [in that respect] was appreciated by the developers.

Sorry that I don't yet understand. If two independent
programs each include my code as header file, one
piece of my code (only the functions actually needed)
would be in each of their memory spaces which are
independent of each other. There couldn't be any
concurrent access to any variable, for there isn't any
common (shared) variable in the first place. Or am I
missing something?

Thanks.

M. K. Shen

Relevant Pages

  • Re: The Hicks Big Mistake (one of them)
    ... > gives directions from that address. ... Turn SLIGHT LEFT onto UPPER COLEVILLE RD. ... Keep RIGHT at the fork in the ramp. ...
    (sci.med.diseases.lyme)
  • Re: Local access only, no internet?
    ... No directions on what fork to take will crash you into the middle of the ... They're called interface and gateway metrics. ... by way of the route command ...
    (microsoft.public.windows.vista.networking_sharing)
  • Re: Unintelligible BrE for AmE speakers?
    ... intersections that say 'toutes directions' for one fork and -- ... "autres directions" for the other. ... baguettes, obviously planted by the local tourist authority) who, ...
    (alt.usage.english)
  • Re: ncu kuv yawg pob lub tsev
    ... I can give you directions as to how to get there but you have to ask ... When at the fork, take the less traveled ... This yet-to-be-name road (if and when the ancient natives ... Phongsavang and you should get there no later then a day at most. ...
    (soc.culture.hmong)