Cryptography-Digest Digest #820, Volume #11 Fri, 19 May 00 11:13:00 EDT
Contents:
Cipher Contest: Whirl128 (announce) (Runu Knips)
Re: About AES contest (DJohn37050)
Re: Cipher Contest: Whirl128 (paper) (Runu Knips)
Matrix reduction (Chris Card)
Re: AES final comment deadline is May 15 (Casper H.S. Dik - Network Security
Engineer)
OT: selfmodifying code (Runu Knips)
<!-- To use a different cobrand, make sure you have a template for it in
/parts/cobrand/ --> (wFIykmki)
Re: Interpretation of Hitachi patent claims (Roger Schlafly)
Re: Is OTP unbreakable? (Paul Koning)
Re: NSA hardware evaluation of AES finalists (Paul Koning)
----------------------------------------------------------------------------
Date: Fri, 19 May 2000 14:06:03 +0200
From: Runu Knips <[EMAIL PROTECTED]>
Subject: Cipher Contest: Whirl128 (announce)
Hello !
Okay, after much struggle in the last time I finally decided to
publish this thing. Its a 128 bit block cipher with a 14 double
round Feistel network. Its at the lowest end of my speed
tolerance (1.5 MB/s on a 300 MHz AMD K6-II, without any
optimizations for the machine). But hey its my first cipher
ever.
Runu
------------------------------
From: [EMAIL PROTECTED] (DJohn37050)
Subject: Re: About AES contest
Date: 19 May 2000 12:24:52 GMT
The way I would word it is:
The conventional "wisdom" is that Ri, Se, and Tw are good candidates and that
RC and MA are less so. But it all depends on what one uses for criteria. ANY
of the finalists are "best" under some criteria.
Don Johnson
------------------------------
Date: Fri, 19 May 2000 14:30:56 +0200
From: Runu Knips <[EMAIL PROTECTED]>
Subject: Re: Cipher Contest: Whirl128 (paper)
Runu Knips wrote:
> [...]
> 2. Encryption process
> ---------------------
> From the key schedule, the cipher gets 64 32 bit values. The first
> eight ones are used for whitening the input and output values.
Damned ! That should read: the last eight ones :-(
> [...]
> The input whitening looks like this:
>
> *------------------------------------------------------------------*
> | A := I[0] xor K[56]; |
> | B := I[1] xor K[57]; |
> | C := I[2] + K[58]; |
> | D := I[3] + K[59]; |
> *------------------------------------------------------------------*
> [...]
> Finally, an output whitening is added.
>
> *------------------------------------------------------------------*
> | O[0] := A + K[60]; |
> | O[1] := B + K[61]; |
> | O[2] := C xor K[62]; |
> | O[3] := D xor K[63]; |
> *------------------------------------------------------------------*
As I said. Can also be verified in the C source.
> [...]
> static const struct test testv[] = {
> { {0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0},
> {0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0} },
> { {0x80,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0},
> {0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0} },
> { {'a','a','a','a','a','a','a','a',
> 'a','a','a','a','a','a','a','a'},
> {'a','a','a','a','a','a','a','a',
> 'a','a','a','a','a','a','a','a'} },
> { {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15},
> {0x0f,0x1e,0x2d,0x3c,0x4b,0x5a,0x69,0x78,
> 0x87,0x96,0xa5,0xb4,0xc3,0xd2,0xe1,0xf
Hu ? The rest got cutted ? Okay, here it is:
struct test {
char key[16];
char ibf[16];
};
static const struct test testv[] = {
{ {0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0},
{0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0} },
{ {0x80,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0},
{0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0} },
{ {'a','a','a','a','a','a','a','a',
'a','a','a','a','a','a','a','a'},
{'a','a','a','a','a','a','a','a',
'a','a','a','a','a','a','a','a'} },
{ {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15},
{0x0f,0x1e,0x2d,0x3c,0x4b,0x5a,0x69,0x78,
0x87,0x96,0xa5,0xb4,0xc3,0xd2,0xe1,0xf0} },
};
int main ()
{
int i;
char buf[16];
keysched K;
#ifdef TEST_PROFILE
clock_t t;
/*-----------------------------------------------------*/
printf ("100,000 times key schedule: "); fflush (stdout);
t = clock ();
for (i = 0; i != 100000; ++i) {
setkey (&K, testv[0].key, 16);
}
t = clock () - t;
printf ("%0.14g sec\n", (double)t / CLOCKS_PER_SEC);
/*-----------------------------------------------------*/
printf ("1,000,000 times encrypt: "); fflush (stdout);
t = clock ();
for (i = 0; i != 1000000; ++i) {
encrypt (&K, testv[0].ibf, buf);
}
t = clock () - t;
printf ("%0.14g sec\n", (double)t / CLOCKS_PER_SEC);
#else
/*-----------------------------------------------------*/
for (i = 0; i != countof(testv); ++i) {
putc ('\n', stdout);
setkey (&K, testv[i].key, 16);
putbuf ("K: ", testv[i].key);
printf ("-----------------------------------\n");
putsched (&K);
printf ("-----------------------------------\n");
encrypt (&K, testv[i].ibf, buf);
printf ("-----------------------------------\n");
putbuf ("I: ", testv[i].ibf);
putbuf ("O: ", buf);
decrypt (&K, buf, buf);
putbuf ("C: ", buf);
putc ('\n', stdout);
}
#endif
return 0;
}
#endif
/*---------------------------------------------------------------*/
------------------------------
Subject: Matrix reduction
From: Chris Card <[EMAIL PROTECTED]>
Date: Fri, 19 May 2000 05:36:51 -0700
I understand that the matrix reduction step of modern
factorisation algorithms is usually done using the Block Lanczos
algorithm (I don't understand the algorithm yet though ...).
Has anyone looked at the possibility of using hillclimbing
methods to find a linear dependency in the matrix? I haven't
given it much thought, but on the face of it there is a large
solution space with many possible solutions and an obvious metric
(number of non-zero entries). Or is this complete rubbish? :-)
Chris
* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
------------------------------
From: [EMAIL PROTECTED] (Casper H.S. Dik - Network Security Engineer)
Subject: Re: AES final comment deadline is May 15
Date: 19 May 2000 12:32:25 GMT
[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]
Runu Knips <[EMAIL PROTECTED]> writes:
>However, JIT has nothing to do with self-modifying code. There is NO
>self-modifying code, that technique is absolutely forbidden now !
>For modern processors can't handle that well anymore. You would have
>to disable the first and second level cache to make that work.
from a processor's viewpoint, self-modifying code and code-generation
on-the-fly are pretty much the same thing.
In an ideal world, modifications written to instruction space not
previously used would not have landed in the Icache; but cachelines
are larger then instruction so they often are.
CPUs support flushing (parts of) the caches so self-modifying code can
be made safe. The Solaris runtime linker (and I'm sure others too)
extensively modifies code while executing.
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
------------------------------
Date: Fri, 19 May 2000 15:15:28 +0200
From: Runu Knips <[EMAIL PROTECTED]>
Subject: OT: selfmodifying code
"Casper H.S. Dik - Network Security Engineer" wrote:
> Runu Knips <[EMAIL PROTECTED]> writes:
> >However, JIT has nothing to do with self-modifying code. There is NO
> >self-modifying code, that technique is absolutely forbidden now !
> >For modern processors can't handle that well anymore. You would have
> >to disable the first and second level cache to make that work.
>
> from a processor's viewpoint, self-modifying code and code-generation
> on-the-fly are pretty much the same thing.
Wrong. A processor which is executing JIT code can't see any difference
to normal code. Its just the same. On the contrary, a processor
executing
self-modifying code has always to check if there isn't already an
updated
version of the code it is currently executing. This means, it has to
disable its code cache, or its code cache has to be far more complex
that
it normally (or often) is. Because normally code caches assume that code
doesn't change. Too, it might also have to disable its pipeline. Because
the pipeline might contain instructions which might have already been
updated in memory.
> In an ideal world, modifications written to instruction space not
> previously used would not have landed in the Icache; but cachelines
> are larger then instruction so they often are.
The code cache has not seen those values written by the JIT compiler
before, while with self-modifying code there is already some code in
those caches.
> CPUs support flushing (parts of) the caches so self-modifying code can
> be made safe. The Solaris runtime linker (and I'm sure others too)
> extensively modifies code while executing.
I'm not sure what you mean. Of course any dynamic linker changes the
code which has to be executed BEFORE it is executed. But not WHILE it
is executed. In a certain sense, a dynamic linker is like a very
primitive JIT.
It is possible that some dynamic linkers (like that one on Solaris)
link libraries not earlier than the moment they are needed. But that
doesn't make this operation a really cheap one !!! That code would
have to assert that all bad opcodes are thrown out of the cache, or
get reloaded. I don't know much about the internals of the Sparc and
UltraSparc processors, but I'm pretty sure microsecond hunters wont
win here.
The only way to get selfmodifying code work efficiently is when you're
able to always put the new version at a new address, or if you have
some comfortable cache which allows to throw out every instruction
which has been changed.
------------------------------
From: wFIykmki <[EMAIL PROTECTED]>
Subject: <!-- To use a different cobrand, make sure you have a template for it in
/parts/cobrand/ -->
Date: 19 May 2000 10:30:39 GMT
<!-- Get Specific Variables for cobrand -->
<!-- YESs and NOs are CaSe SeNsItIvE... Always use ALL CAPS for them! -->
<!-- EXTRA_CODE_AFTER_TOP/BOTTOM are typically used for consistent
identification or used for "floating" nav bars. If you say YES
make sure you hare corresponding code in /parts/cobrand/ -->
<!-- What Modules to use --->
<HTML>
<HEAD>
<TITLE>XOOM.it Servizi Iscritti: </TITLE>
<META name="resource-type" content=document>
<META name="description" content="XOOM.COM Get your web space free! Get Chat! See
Movies! Cool Stuff all for Free!">
<META name="keywords" content="XOOM FREE CHAT WEB SPACE MOVIES EMAIL WEB CLIP ART HTML
CLIPART CARDS DOWNLOADS">
<META name=distribution content=global>
</HEAD>
<BODY BGCOLOR="#FFFFFF" BACKGROUND="http://media.xoom.it/new/Background.gif"
TEXT="#000000" LINK="#0000FF" VLINK="#0000FF" ALINK="#FF0000">
<!-- Top Part Table -->
<TABLE border=0 cellPadding=0 cellSpacing=0 width=600>
<TBODY>
<TR>
<TD background="http://media.xoom.it/new/Left_Background.gif" vAlign=top wid
th=111>
<A href="http://www.xoom.it">
<IMG border=0 height=113 hspace=0
src="http://media.xoom.it/new/logo_corner.gif" width=111>
</A>
<TABLE background="http://media.xoom.it/new/spacer.gif" border=0 cellPaddi
ng=0 cellSpacing=0 width=111>
<TBODY>
<TR>
<TD align=middle vAlign=top>
<!--- inizio HOTSPOT --->
<IMG height=1 hspace=0 src="http://media.xoom.it/new/clear.gif" width=90><BR><IMG
height=25 hspace=0 src="http://media.xoom.it/new/hot_spots_top.gif" width=90><BR>
<!-- Hotspot 1 -->
<A href="http://www.xoom.it/cgi-bin/redir.cgi?url=http://www.mrprice.it&title=hs"
target=_top>
<IMG alt="Vinci fantastici premi" border=0 height=27
src="http://media.xoom.it/hotspots/hs_misterprice.gif" width=90></A><BR>
<!-- Hotspot 2 -->
<A href="http://www.xoom.it/cgi-bin/redir.cgi?url=http://www.risateonline.it&title=hs"
target=_top>
<IMG alt="Barzellette via email" border=0 height=27
src="http://media.xoom.it/hotspots/hs_barzelletta.gif" width=90></A><BR>
<!-- Hotspot 3 -->
<A href="http://www.xoom.it/chat" target=_top>
<IMG alt="Preleva la tua Chat" border=0 height=27
src="http://media.xoom.it/hotspots/hs_chat.gif" width=90></A><BR>
<!-- Hotspot 4 -->
<A
href="http://www.xoom.it/cgi-bin/redir.cgi?url=http://www.namesecure.com/partners/xoom/it/&title=hs"
target=_top>
<IMG alt="Registra il tuo dominio" border=0 height=27
src="http://media.xoom.it/hotspots/hs_namesecure2.gif" width=90></A><BR>
<IMG height=1 hspace=0 src="http://media.xoom.it/new/hot_spots_bottom.gif"
width=90><BR><IMG height=10 src="http://media.xoom.it/new/spacer.gif" width=90><BR>
<!--- fine HOTSPOT --->
<!-- *** HOTSPOT *** -->
<!--< include ("/usr/WWW/parts/hotspot.html");>-->
<!---- inizio RISORSE ---->
<br>
<IMG alt="" border=0 height=177 hspace=0 src="http://media.xoom.it/new/resources6.gif"
useMap=#RESOURCES width=90>
<MAP name=RESOURCES>
<AREA alt="" coords=1,17,88,32
href="http://www.xoom.it/cgi-bin/redir.cgi?url=http://www.xoom.it/dizionario&title=ris"
shape=RECT>
<AREA alt="" coords=1,34,88,48 href="http://www.xoom.it/chatroom/xoom" shape=RECT>
<AREA alt="" coords=2,50,88,65 href="/products/boutique.php" shape=RECT>
<AREA alt="" coords=2,66,88,80
href="http://www.xoom.it/cgi-bin/redir.cgi?url=http://www.tariffe.it/xoom" shape=RECT>
<AREA alt="" coords=2,82,88,95
href="http://www.xoom.it/cgi-bin/redir.cgi?url=http://cartoline.xoom.it/xigo"
shape=RECT>
<AREA alt="" coords=2,97,88,111
href="http://www.xoom.it/cgi-bin/redir.cgi?url=http://www.mrprice.it&title=ris"
shape=RECT>
<AREA alt="" coords=2,113,88,126
href="http://www.xoom.it/cgi-bin/redir.cgi?url=http://www.webcast.it&title=ris"
shape=RECT>
<AREA alt="" coords=2,129,88,141
href="http://www.xoom.it/cgi-bin/redir.cgi?url=http://www.tuttogratis.com/cgi/entra.cgi&title=ris"
shape=RECT>
<AREA alt="" coords=2,145,88,157
href="http://www.xoom.it/cgi-bin/redir.cgi?url=http://sharehouse.xoom.it&title=ris"
shape=RECT>
<AREA alt="" coords=2,161,88,173
href="http://www.xoom.it/cgi-bin/redir.cgi?url=http://www.qxl.com/cgi-bin/qxlhome.cgi/IT/xoom&title=ris1"
shape=RECT>
</MAP>
<!--- fine RISORSE --->
<!---- inizio RISORSE ---->
<br><br>
<IMG alt="" border=0
hspace=0 src="http://media.xoom.it/services/altriservizi.gif"
useMap=#altrimap width=90> <MAP name=altrimap><AREA alt=""
coords=1,17,88,32
href="http://www.xoom.it/clipart"
shape=RECT><AREA alt="" coords=1,34,88,48
href="http://www.xoom.it/downloads"
shape=RECT>
</MAP>
<!--- fine RISORSE --->
</TD></TR></TBODY></TABLE></TD>
<TD vAlign=top width=489>
<!--- inizio LATO DESTRO ---> <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0
WIDTH=489><TR>
<TD HEIGHT=2 BGCOLOR=#000000 COLSPAN=2 WIDTH=489><SPACER TYPE="BLOCK" WIDTH=1 HE
IGHT=2></TD></TR>
</TABLE>
<TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=489 bgcolor=#ffcc99><TR>
<!-- Inizio banner -->
<STYLE TYPE=text/css>
<!--
xoom8 {font-family:Verdana,Tresbuchet MS,Helvetica,Arial; font-size:7pt;}
xoom9 {font-family:Verdana,Tresbuchet MS,Helvetica,Arial; font-size:8pt;}
xoom10 {font-family:Verdana,Tresbuchet MS,Helvetica,Arial; font-size:8pt;}
xoom12 {font-family:Verdana,Tresbuchet MS,Helvetica,Arial; font-size:10pt; }
xoom14 {font-family:Verdana,Tresbuchet MS,Helvetica,Arial; font-size:12pt; }
xoom16 {font-family:Verdana,Tresbuchet MS,Helvetica,Arial; font-size:14pt; }
xoomhead {font-family:Verdana,Tresbuchet MS,Helvetica,Arial; font-size:14pt;
font-weight:bold; }
xoomcomhead {font-family:Verdana,Tresbuchet MS,Helvetica,Arial; font-size:10pt;
font-weight:bold;}
xoomcomsubhead {font-family:Verdana,Tresbuchet MS,Helvetica,Arial; font-size:9pt;
margin-left:4pt; }
-->
</STYLE>
<TD bgcolor=#FFCC66 align=center WIDTH=487>
<table border=0><tr><td height=4 nowrap>
</td></tr></table>
<IFRAME
SRC="http://ad.it.doubleclick.net/adi/xoom.it/membersarea;area=membersarea;sz=468x60;ord=2801?"
WIDTH=468 HEIGHT=60 MARGINWIDTH=0 MARGINHEIGHT=0 HSPACE=0 VSPACE=0 FRAMEBORDER=0
SCROLLING=no BORDERCOLOR="#FFCC66">
<SCRIPT language="JavaScript1.1"
SRC="http://ad.it.doubleclick.net/adj/xoom.it/membersarea;area=membersarea;abr=!ie;sz=468x60;ord=2801?">
</SCRIPT>
<NOSCRIPT>
<A
HREF="http://ad.it.doubleclick.net/jump/xoom.it/membersarea;area=membersarea;abr=!ie4;abr=!ie5;sz=468x60;ord=2801?">
<IMG
SRC="http://ad.it.doubleclick.net/ad/xoom.it/membersarea;area=membersarea;abr=!ie4;abr=!ie5;sz=468x60;ord=2801?"
BORDER=0 WIDTH=468 HEIGHT=60>
</A>
</NOSCRIPT>
</IFRAME>
<CENTER><IMG SRC="http://media.xoom.it/NovLook/spacer.gif" HEIGHT=3 WIDTH=468><BR>
<IMG SRC="http://media.xoom.it/blackline.gif" HEIGHT=1 WIDTH=468><BR>
<TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%>
<TR>
<TD COLSPAN=4><IMG SRC="http://media.xoom.it/new/clear.gif"
WIDTH="487" HEIGHT="4" HSPACE="0" VSPACE="0"><BR></TD>
</TR>
<TR>
<!-- Tastino 1 -->
<TD VALIGN=TOP ALIGN=MIDDLE WIDTH=25%><A
HREF="http://www.xoom.it/cgi-bin/redir.cgi?url=http://www.italianetwork.it"
TARGET=_top><IMG SRC="http://media.xoom.it/bottoni/rin_nero.gif" BORDER=1 WIDTH=88
HEIGHT=31></A><BR>
<FONT FACE="Verdana,Arial,HELVETICA" SIZE=1><SPAN CLASS=X9><B>NET
RADIO</B></SPAN></FONT></TD>
<!-- Tastino 3 -->
<TD VALIGN=TOP ALIGN=MIDDLE WIDTH=25%><A HREF="http://www.webcast.it/newsmp3.php3"
TARGET=_top><IMG SRC="http://media.xoom.it/bottoni/wc_mp3news_88x31.gif" BORDER=1
WIDTH=88 HEIGHT=31></A><BR>
<FONT FACE="Verdana,Arial,HELVETICA" SIZE=1><SPAN CLASS=X9><B>NOVITA' via
E-MAIL</B></SPAN></FONT></TD>
<!-- Tastino 2 -->
<TD VALIGN=TOP ALIGN=MIDDLE WIDTH=25%><A
HREF="http://www.xoom.it/cgi-bin/redir.cgi?url=http://www.xoom.it/premiowww.php"
TARGET=_top><IMG SRC="http://media.xoom.it/bottoni/premiowww_new.gif" BORDER=1
WIDTH=88 HEIGHT=31></A><BR>
<FONT FACE="Verdana,Arial,HELVETICA" SIZE=1><SPAN CLASS=X9><B>PREMIO
WWW</B></SPAN></FONT></TD>
<!-- Tastino 4 -->
<TD VALIGN=TOP ALIGN=MIDDLE WIDTH=25%><A
HREF="http://www.xoom.it/cgi-bin/redir.cgi?url=http://www.risateonline.it/barzaemailx.phtml&title=but"
TARGET=_top><IMG SRC="http://media.xoom.it/bottoni/barza_88x27.gif" BORDER=1 WIDTH=88
HEIGHT=31></A><BR>
<FONT FACE="Verdana,Arial,HELVETICA" SIZE=1><SPAN CLASS=X9><B>RISATE ON
LINE!</B></SPAN></FONT></TD>
</TR>
</TABLE>
<!-- fine banner -->
</TD>
<TD BGCOLOR=#000000><SPACER TYPE="BLOCK" WIDTH=2 HEIGHT=2></TD>
</TR>
<TR>
<TD HEIGHT=2 BGCOLOR=#000000 COLSPAN=2><SPACER TYPE="BLOCK" WIDTH=1
HEIGHT=2></TD>
</TR>
</TABLE>
<TABLE CELLPADDING=10 BORDER=0> <!-- Inside Table START Only here for padding -->
<TR><TD>
<IMG SRC="http://media.xoom.it/images/headers/Ooops.gif" ALT="( Ooops! )" WIDTH="450"
HEIGHT="48"><P>
<FONT SIZE=+2>
La pagina a cui stai cercando di accedere non pu� essere trovata!<P></FONT>
Cause possibili:<P>
<UL>
<LI TYPE="circ">La pagina � momentaneamente offline per allestimento. Controlla
l'homepage di XOOM.it per il sistema status/alerts e riprova pi� tardi.
<LI TYPE="circ"> Indirizzo non corretto. (Ricorda, gli indirizzi URL sono
case-sensitive!) </LI>
<LI TYPE="circ">La suddetta pagina non esiste pi�</LI>
<LI TYPE="circ">Il membro � stato rimosso per violazione delle <A
HREF=http://xoom.it/TOS>Condizioni di Utilizzo</A>di XOOM.it.</FONT><P>
</UL>
XOOM.it non permette riferimenti a:<P>
<UL>
<LI TYPE="circ">materiale pornografico e a sfondo sessuale di natura oscena;
<LI TYPE="circ">materiale che viola i diritti d'autore, in particolare software pirata
("WAREZ, CRACK") file musicali, immagini, video, testi
protetti da
copyright;
<LI TYPE="circ">materiale offensivo incluse espressioni diffamatorie, di fanatismo,
razzismo, odio, irriverenza o minaccia;
<LI TYPE="circ">materiale che promuove o fornisce informazioni che istruiscano su
attivit� illegali o che possano causare pregiudizio a terzi;
<LI TYPE="circ">software, informazioni o altro materiale contenente virus o componenti
dannosi;
<LI TYPE="circ">iniziative legate al gioco d'azzardo, concorsi, giochi che richiedono
una
partecipazione a titolo oneroso.
<LI TYPE="circ">Inserire sulla tua pagina pubblicit� o banner di sponsor.
<LI TYPE="circ">Rimuovere dalla tua pagina il banner di XOOM.it e relativi
collegamenti a
XOOM.it o sue directory.
<LI TYPE="circ">Concedere l'accesso alla tua pagina(e) XOOM.it solo a utenti con
password.
<LI TYPE="circ">Inviare email utilizzando un indirizzo di XOOM.it o contenenti
riferimenti
alla tua home page su XOOM.it.
<LI TYPE="circ">Utilizzare nella fase di registrazione come membro un account di email
che non � il tuo o che non funziona.
<P>
</UL>
<FONT SIZE=+2>Per conoscere al completo le Condizioni di Utilizzo
clicca <A HREF=http://xoom.it/TOS>qui</A>.<P>
Se pensi che la tua pagina membro sia stata rimossa
per errore, spedisci una e-mail a <A
HREF=mailto:[EMAIL PROTECTED]>Webmaster</A>.<P>
<A HREF="http://xoom.it/signup/JoinNow.xihtml?R=0&P=7">Iscriviti ora a XOOM.it! E'
gratis!</A></FONT><P>
</FONT>
</TD></TR></TABLE>
</TD></TR>
<TR>
<TD background="http://media.xoom.it/new/Left_Background.gif" height=70
vAlign=bottom width=111><IMG align=baseline height=70 hspace=0
src="http://media.xoom.it/new/left_bottom4.gif" width=111></TD>
<TD height=70 vAlign=top width=489 bgcolor=#ffcc66>
<!---- punto di inserimento snap ----->
<TABLE border=0 cellPadding=0 cellSpacing=0 height=2 width=489>
<TBODY>
<TR>
<TD bgColor=#000000 colSpan=2 height=2 width=489><SPACER HEIGHT="2"
WIDTH="1" TYPE="BLOCK"></TD></TR></TBODY></TABLE>
<TABLE border=0 cellPadding=0 cellSpacing=0 height=66 width=489>
<TBODY>
<TR>
<TD bgColor=#ffcc66 width=487><IMG height=5 hspace=0
src="http://media.xoom.it/new/spacer.gif" width=314><BR><B><FONT class=X11
face="Verdana, Arial, Helvetica"> Iscriviti a XOOM.it adesso per
questi servizi gratuiti!<BR></FONT>
<FONT class=X11 face="Verdana, Arial, Helvetica"> </FONT><FONT
class=xh9 face="Arial, Helvetica" size=1><A href="http://xoom.it/webspace/">Spazio
Web</A> | <A href="http://xoom.it/email/">Email</A> | <A
href="http://xoom.it/chat/">Chat Room</A> | <A
href="http://xoom.it/cgi-bin/redir.cgi?url=http://counter.xoom.it/">Xoomcounter</A> |
<A href="http://xoom.it/clipart/">Clip
Art</A> | <A href="http://xoom.it/downloads/">Area Download</A>
</FONT></B><IMG height=2 hspace=0
src="http://media.xoom.it/new/spacer.gif" width=314><BR><FONT class=
X11
face="Verdana, Arial, Helvetica"> </FONT><FONT class=X9
face="Arial, Helvetica" size=1><A href="http://xoom.it/about">Chi e'
Xoom.it</A> |
<A href="http://xoom.it/about/advertising">Pubblicita'</A> | <A
href="http://xoom.it/PPS">Legge sulla privacy</A> | <A
href="http://xoom.it/TOS">Condizioni di utilizzo</A><BR><A
href="http://xoom.it/copyright">Copyright</A> xa9 1999 Licenze XOOM.it.
Tutti i d
iritti riservati. Powered by <a href=http://www.it.net><b><font color="#800000">
IT</font><font color="#008000"><i>net</i></b></a></FONT>.
<br>
<BR clear=all><IMG height=5 hspace=0
src="http://media.xoom.it/new/spacer.gif" width=314><BR></TD>
<TD bgColor=#000000 width=2><SPACER HEIGHT="2" WIDTH="2"
TYPE="BLOCK"></TD></TR></TBODY></TABLE>
<TABLE border=0 cellPadding=0 cellSpacing=0 height=2 width=489>
<TBODY>
<TR>
<TD bgColor=#000000 colSpan=2 height=2 width=489><SPACER HEIGHT="2"
WIDTH="1" TYPE="BLOCK"></TD></TR></TBODY></TABLE></TD></TR>
<TR>
<TD align=left colSpan=2 vAlign=top><IMG height=20
src="http://media.xoom.it/new/fade_bottom.gif" width=250>
</TD></TR></TBODY></TABLE>
</FORM>
</BODY>
</HTML>
------------------------------
From: Roger Schlafly <[EMAIL PROTECTED]>
Subject: Re: Interpretation of Hitachi patent claims
Date: Fri, 19 May 2000 07:59:32 -0700
Richard Heathfield wrote:
> I would be most interested in seeing Hitachi's letter. Unfortunately,
> it's in pdf (Portable Document Format) which, ironically, doesn't work
> on my system. Is it available anywhere in a portable document format
> (i.e. ASCII text)?
A lot of version of MSIE have this problem. But you can save
it to a file (right mouse click, save as), and then view it
with the Adobe reader.
------------------------------
From: Paul Koning <[EMAIL PROTECTED]>
Subject: Re: Is OTP unbreakable?
Date: Fri, 19 May 2000 10:56:25 -0400
Richard Herring wrote:
>
> In a...
> > Still, OTP has two weaknesses though:
> >...
> 3. An attacker can modify the message. If he knows the position of
> some item within the plaintext, he can change it to any other string
> with the same length.
Easy to fix: calculate a hash (e.g., HMAC), append it, and encrypt
the result. The security provided by OTP protects the hash as well,
though you do want a good hash -- for example, an IP checksum will
not do at all.
paul
------------------------------
From: Paul Koning <[EMAIL PROTECTED]>
Subject: Re: NSA hardware evaluation of AES finalists
Date: Fri, 19 May 2000 10:53:41 -0400
Paul Rubin wrote:
> ...
> Generally you can increase performance by increasing chip area, by
> adding more pipelining and so forth. So assuming both scale the same
> way, speed per area is still interesting. Changing feature size
> doesn't affect the relationship either. And high performance doesn't
> necessarily mean trying to get the maximum possible bits/sec through a
> single cipher instance. You might want a bunch of instances on the
> same chip, so you can do parallel encryption with different keys
Yes, that can be useful. On the other hand, single stream performance
is a really important parameter; if you have two products that both
do 300 Mb/s but one can do it single stream and the other can only do
it if you have at least 4 streams (i.e., 75 Mb/s single stream) the
former clearly has the competitive advantage.
Of course you can do parallel processing on several queued packets
of a single stream (provided it's stateless, e.g., IPsec). That helps
a bit...
paul
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and sci.crypt) via:
Internet: [EMAIL PROTECTED]
End of Cryptography-Digest Digest
******************************
