Cryptography-Digest Digest #626, Volume #9       Mon, 31 May 99 15:13:03 EDT

Contents:
  Re: i have an encrypted password file that i want to decrypt, can anyone tell me any 
ways of going about it? (kurt wismer)
  Re: Please recommend freeware encryption SDK (Geoff Thorpe)
  Re: Oriental Language Based Enryption (Patrick Juola)
  Re: 8Bit encryption code. Just try and break it. - code3.ecr (0/1) ("Steve Sampson")
  Re: OTP Problems ([EMAIL PROTECTED])
  Re: 8Bit encryption code. Just try and break it. - code3.ecr (0/1) (Phoenix)
  Re: PGP Info wanted... (Tom McCune)

----------------------------------------------------------------------------

From: kurt wismer <[EMAIL PROTECTED]>
Subject: Re: i have an encrypted password file that i want to decrypt, can anyone tell 
me any ways of going about it?
Date: Mon, 31 May 1999 20:20:12 GMT

Jim Whitehead wrote:
> 
> i have an encrypted password file that i want to decrypt, can anyone tell me
> any ways of going about it?

hmm... that depends, do you mean the file itself has been encrypted by
some program or the passwords are encrypted?

if the former then it really sort of depends on which program was used
to encrypt the file (in that case the fact that it contains passwords
may well be irrelevant)...

if the latter then the passwords probably aren't encrypted but are
instead hashed since there isn't a great need to use a reversible
transformation for passwords (just hash the user entered password and
compare the hash to the stored hash)... hashes typically cannot be
reversed/decrypted though... 

-- 
"close your eyes and bow your head
 i need a little sympathy
 cause fear is strong and love's for
 everyone who isn't me"


------------------------------

From: Geoff Thorpe <[EMAIL PROTECTED]>
Crossposted-To: news.groups,at.test,alt.gothic,sci.math
Subject: Re: Please recommend freeware encryption SDK
Date: 31 May 1999 13:50:59 GMT

This message intentionally left encrypted.


Sdyej wrest ybtps keky ehfo mee
lav zkeap fj lmeog va
duwodf ltl lvkou kreowe deoiy
pi woq kt cfupu.

Csfudo mtei embbp kkuti kior
ol eelt yjb rbbc ylpr swdsa
deygau cpoa iirr sqcd ii
wefs ypoe gb imwbx
hkz eur ydbg xdy eeo lzhz.

Omy foc vxk ri?

Siaq hfi byety zpby ev eofoe
soeo jzgkx mfe ekltu drkr smyip
xvkca mos tul pretpv irnmi
cuwtib deyvo zql mku pdiy
ryee yuvedt pieg fheex ese hte
nlc reer xkwpkd fiozb
boyu ysyek qcc iqr
rqvm ie palieei mlt flkewio rbyxe.

Oaszi eldu mm eapp sb ecyp
twf ecfl zwy qtet lre eboex
otlf stg mfe vsurv lrbef ftcjk?

Lmkil iusb cae jeitm
tatz lela zef lf
ka rae krck kfey ek oey
hlk opkpxm neru kbqd
ee kgld rd jso vies yii
ir osdjh lhye id tolyl crs
oudox ooe fhr ei.

Etvjktz pe yerp saee
leo ceq ez uzee we pua
ufjg ial yylym meeeb eucr
epi eztkjee anoif pbne li?

Kbzkyz ooe kre pofiam oykb!

Ktrbal ams ecar rant
yia mpda coo arlr ryp.

Trutr kid otr lt
lqt bumv shuke ndoe
yqpemu edcfw kpe buyo.

Seeaesc yqnzeh ecltill alt
autx mipee bfaee ufkqe!





------------------------------

From: [EMAIL PROTECTED] (Patrick Juola)
Crossposted-To: news.groups,at.test,alt.gothic,sci.math
Subject: Re: Oriental Language Based Enryption
Date: 31 May 1999 13:52:27 GMT

This message intentionally left encrypted.


Fwkw pprb mmbke ipeg esmu
kliyw mowmilu medhr noml
po upftco thmql iesc xalli.

Aeale kbe ljtn xvo
pioa nfn ykub vqaea xski?

Dtgasca epp ymk bupaiw ujaiu
illf rsau mpfb xjd xjde
bems whyy gobs rmfrns fplo
rki eefg prfi rolul.

Ryelyqsn ipwlu yolr zmpi nfdwlie stlsk
wnowd tfw grls bwl sd
prmigb losm oardiu szrsrf lvlsdz leiw.

Krkeur slsa fnm eisep nofel pn
flmw ylqt ail nb oo qb!

Lbee vea cho mwnkb xdlil
dydoep legl ofobnj ezzs dk
dyno pcet jipim pba eaosk mi
xyk uitel rurea esejl sbpllb rmcbe?

Zmqhdo lleb ejwjen les
dhnd laeedu yexou ar
lysk yst zilxs ohe
ufb kdct inqp yafhw
oddor pdebbpf qbtjuwb eahlbbw ywi
gei xle beja mwpikp rme vz.

Ybbyz neei kehe en
fij etma eecj bzh vvsdqm mgbg
abol yrm ul avs ec?

Viffb vaz inlemh ybyy zshomo ak
uyr ro aibal akm sym
io keio ib sj iy me.

Txnpi fie llh pfq ciy
nlt oiz sultl awfi
omsi ztersbl tr ned vci
bsa zbo ilm olet si
anmbkj ou treeo od
bebm rlfl lsypx xeel
pwex ulzek hhy ptunrr heu.

Henmpdnu udbgsc sx mogffk iz bl.

Dysfd iey lwtc eicb hiy
imjtz rwte gqrpz eeekd vpl?

Eov qp lgwz esi strt!

Wualvhm rqmse leakzt cze
les eqll ulez dades
bkbn tjly ega icli utikk
eyyeei yi pygss kjice.

Nhsyos aif eeo hf
pfjsb sebcg smrn sdu igm deedy
umib eqfg amp pbap tgmy
myf dof ppred sllrg
ptac pfibf njez bke plkyb ia
mkde eeo yerl zxou iuur tmfmd
lmu omgu etox mjwe lepr
fwja yoove iefm rnek.




------------------------------

From: "Steve Sampson" <[EMAIL PROTECTED]>
Subject: Re: 8Bit encryption code. Just try and break it. - code3.ecr (0/1)
Date: Mon, 31 May 1999 13:33:10 -0500

This is a multi-part message in MIME format.

=======_NextPart_000_0009_01BEAB6A.20649BA0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

No, without knowing the algorithm, it is harder to break
the encryption.

Here's the file code3.ecr in hexadecimal (first pass, align on
byte with heavy repetition).  This already shows that for
some reason there is some bits stuck, and is not going to
be a good algorithm.  It has high overhead as well, and the
coded file could then be smaller.

I then noticed that the second to last bytes nibbles always was greater
than 9 hex and wrapped other lines at that point as well, BUT there are
some exceptions.
02 85         d1 9a    16 58 50      b7 9a10 36 83      7c 9a10 52 88    =
  dc 9a18 93 90      da 9a10 88 19      d2 0992 96         a4 9a16 85 25 =
     de 9a10 72 14      f9 0796 08         1c 9a22 89 80      9d 9a12 90 =
42      db 9a17 71 92      c0 9a10 96 75      7d 9a10 68 93      c8 9a16 =
09 28      7b 9a11 44 90      e3 9a10 78 56      fc 9a16 64 92      5e =
9a13 10 75      fb 9a12 19 80      b7 9a15 57 92      fe 9a16 21 05      =
0c 9a13 70 67      2d 9a13 31 08      e0 9a13 85 65      1b 9a10 94 61   =
   9f 9a13 22 52      f7 9a12            84 9a    Exception to rule      =
        a2 9a12 74 37      4a 9a13 82 44      c8 9a10 37 90      a4 9a13 =
06 47      8c 9a13 86 72      5b 9a18 51 10      be 0622 74         ab =
9a13 99 56      6e 9a19 90 20      9f 0725 46         f2 9a16 77 76      =
c5 9a18 08 30      2d 09              63 9a    Exception to rule         =
     cf 9a13 39 64      e5 9a19 09 95      b8 0902 01         a7 9a15 02 =
28      b2 9a16 47 80      ac 0780 03         a3 9a14 80 88      1c 9a21 =
50 70      fb 0728 67         a1 9a16 39 24      b0 9a17 44 10      ae =
0603 48         c5 9a15 15 12      4a 9a17 22 70      c9 9a13 35 36      =
a1 0770 40         dd 9a17 76 20      d9 9a12 32 64      e5 0924 48      =
   5c 9a17 22 70      2e 9a13 86 72      3b 9a10 57 16      b7 9a16 69 =
20      b8 9a11 81 28      2a 9a12 54 04      cd 9a22 68 40      9b 9a10 =
20 78      d1 9a12            84 9a        Exception to rule             =
 b6 9a19 09 95      d9 9a12 51 90      ac 0911 64         5b 9a          =
    20 9a        Exception to rule90            2c 9a10 88 19      4c =
9a10 52 88      2d 9a23 21 90      7a 9a10 43 25      d8 9a18 27 56      =
cc 9a10 91 40      2b 9a10 75 35      8b 9a16 99 16      7d 9a15 56 85   =
   ae 9a10 84 98      8e 9a16 73 48      af 9a13 10 75      ea 9a12 06 =
96      d9 9a15 75 04      8c 9a15 40 80      2a 9a13 83 51      a4 9a13 =
69 60      2f 9a16 31 75      c4 9a13 16 10      3e 9a13 52 48      5d =
9a13 96 35      3c 9a12 80 79      8f 9a13 52 48      f3 9a13 05 40      =
a3 9a              13 9a     Exception to rule05            e4 9a13 65 =
32      d4 9a21 72 10      8e 0629 16         a4 9a14 20 96      4d 9a22 =
30 95      b8 0683 73         b8 9a16 99 16      b3        Exception to =
rule
Phoenix wrote in message <[EMAIL PROTECTED]>...
>No I am not posting random numbers as a joke... I mean 16bit because
>there are only 64k possibilities.  to answer a few other
>questions/threats the program was written in Visual Basic. =20




> So, even you concede that an encryption cannot be broken without any
>knowledge of the algorithm?



>
> [EMAIL PROTECTED]
>
>fungus wrote:
>>=20
>> Phoenix wrote:
>> >
>> > Here is a better message with a better code.  NO I will not =
publicize
>> > my algorythm (my co-programmer forbids it) when it is broken by one =
of
>> > you I will send it to someone (CoderX2, anyone else who wants it) =
and
>> > have it evaluated.  But I would still like people to try and break =
it.
>> > Also its not 8-bit it is 16.  And I know that uncertainty about the
>> > algorythm would add more bits.  So here it is.
>> >
>>=20
>> How do we know you're not just posting random numbers as a joke?
>>=20
>> --
>> <\___/>
>> / O O \
>> \_____/  FTB.

=======_NextPart_000_0009_01BEAB6A.20649BA0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3616.1301"' name=3DGENERATOR>
</HEAD>
<BODY>
<DIV>No, without knowing the algorithm, it is harder to break</DIV>
<DIV>the encryption.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Here's the file code3.ecr in hexadecimal (first pass, align =
on</DIV>
<DIV>byte with heavy repetition).&nbsp; This already shows that =
for</DIV>
<DIV>some reason there is some bits stuck, and is not going to</DIV>
<DIV>be a good algorithm.&nbsp; It has high overhead as well, and =
the</DIV>
<DIV>coded file could then be smaller.</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>I then noticed that the second to =
last bytes=20
nibbles always was greater</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>than 9 hex </FONT><FONT size=3D2>and =
wrapped other=20
lines at that point as well, BUT there are</FONT></DIV>
<DIV><FONT size=3D2>some exceptions.</FONT></DIV><PRE><PRE>02 =
85&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  d1 9a &nbsp;&nbsp; =
</PRE><PRE>16 58 50&nbsp;&nbsp;&nbsp;   b7 9a</PRE><PRE>10 36 =
83&nbsp;&nbsp;&nbsp;   7c 9a</PRE><PRE>10 52 88&nbsp;&nbsp;&nbsp;   dc =
9a</PRE><PRE>18 93 90&nbsp;&nbsp;&nbsp;   da 9a</PRE><PRE>10 88 =
19&nbsp;&nbsp;&nbsp;   d2 09</PRE><PRE>92 96&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;  a4 9a</PRE><PRE>16 85 25&nbsp;&nbsp;&nbsp;   de =
9a</PRE><PRE>10 72 14&nbsp;&nbsp;&nbsp;   f9 07</PRE><PRE>96 =
08&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  1c 9a</PRE><PRE>22 89 =
80&nbsp;&nbsp;&nbsp;   9d 9a</PRE><PRE>12 90 42&nbsp;&nbsp;&nbsp;   db =
9a</PRE><PRE>17 71 92&nbsp;&nbsp;&nbsp;   c0 9a</PRE><PRE>10 96 =
75&nbsp;&nbsp;&nbsp;   7d 9a</PRE><PRE>10 68 93&nbsp;&nbsp;&nbsp;   c8 =
9a</PRE><PRE>16 09 28&nbsp;&nbsp;&nbsp;   7b 9a</PRE><PRE>11 44 =
90&nbsp;&nbsp;&nbsp;   e3 9a</PRE><PRE>10 78 56&nbsp;&nbsp;&nbsp;   fc =
9a</PRE><PRE>16 64 92&nbsp;&nbsp;&nbsp;   5e 9a</PRE><PRE>13 10 =
75&nbsp;&nbsp;&nbsp;   fb 9a</PRE><PRE>12 19 80&nbsp;&nbsp;&nbsp;   b7 =
9a</PRE><PRE>15 57 92&nbsp;&nbsp;&nbsp;   fe 9a</PRE><PRE>16 21 =
05&nbsp;&nbsp;&nbsp;   0c 9a</PRE><PRE>13 70 67&nbsp;&nbsp;&nbsp;   2d =
9a</PRE><PRE>13 31 08&nbsp;&nbsp;&nbsp;   e0 9a</PRE><PRE>13 85 =
65&nbsp;&nbsp;&nbsp;   1b 9a</PRE><PRE>10 94 61&nbsp;&nbsp;&nbsp;   9f =
9a</PRE><PRE>13 22 52&nbsp;&nbsp;&nbsp;   f7 =
9a</PRE><PRE>12&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;     84 =
9a&nbsp;&nbsp;&nbsp; Exception to rule</PRE><PRE>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp; a2 9a</PRE><PRE>12 74 =
37&nbsp;&nbsp;&nbsp;   4a 9a</PRE><PRE>13 82 44&nbsp;&nbsp;&nbsp;   c8 =
9a</PRE><PRE>10 37 90&nbsp;&nbsp;&nbsp;   a4 9a</PRE><PRE>13 06 =
47&nbsp;&nbsp;&nbsp;   8c 9a</PRE><PRE>13 86 72&nbsp;&nbsp;&nbsp;   5b =
9a</PRE><PRE>18 51 10&nbsp;&nbsp;&nbsp;   be 06</PRE><PRE>22 =
74&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  ab 9a</PRE><PRE>13 99 =
56&nbsp;&nbsp;&nbsp;   6e 9a</PRE><PRE>19 90 20&nbsp;&nbsp;&nbsp;   9f =
07</PRE><PRE>25 46&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  f2 =
9a</PRE><PRE>16 77 76&nbsp;&nbsp;&nbsp;   c5 9a</PRE><PRE>18 08 =
30&nbsp;&nbsp;&nbsp;   2d 09</PRE><PRE>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;   63 9a&nbsp;&nbsp;&nbsp; =
Exception to rule</PRE><PRE>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; &nbsp; cf 9a</PRE><PRE>13 39 64&nbsp;&nbsp;&nbsp;   =
e5 9a</PRE><PRE>19 09 95&nbsp;&nbsp;&nbsp;   b8 09</PRE><PRE>02 =
01&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  a7 9a</PRE><PRE>15 02 =
28&nbsp;&nbsp;&nbsp;   b2 9a</PRE><PRE>16 47 80&nbsp;&nbsp;&nbsp;   ac =
07</PRE><PRE>80 03&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  a3 =
9a</PRE><PRE>14 80 88&nbsp;&nbsp;&nbsp;   1c 9a</PRE><PRE>21 50 =
70&nbsp;&nbsp;&nbsp;   fb 07</PRE><PRE>28 67&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;  a1 9a</PRE><PRE>16 39 24&nbsp;&nbsp;&nbsp;   b0 =
9a</PRE><PRE>17 44 10&nbsp;&nbsp;&nbsp;   ae 06</PRE><PRE>03 =
48&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  c5 9a</PRE><PRE>15 15 =
12&nbsp;&nbsp;&nbsp;   4a 9a</PRE><PRE>17 22 70&nbsp;&nbsp;&nbsp;   c9 =
9a</PRE><PRE>13 35 36&nbsp;&nbsp;&nbsp;   a1 07</PRE><PRE>70 =
40&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  dd 9a</PRE><PRE>17 76 =
20&nbsp;&nbsp;&nbsp;   d9 9a</PRE><PRE>12 32 64&nbsp;&nbsp;&nbsp;   e5 =
09</PRE><PRE>24 48&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  5c =
9a</PRE><PRE>17 22 70&nbsp;&nbsp;&nbsp;   2e 9a</PRE><PRE>13 86 =
72&nbsp;&nbsp;&nbsp;   3b 9a</PRE><PRE>10 57 16&nbsp;&nbsp;&nbsp;   b7 =
9a</PRE><PRE>16 69 20&nbsp;&nbsp;&nbsp;   b8 9a</PRE><PRE>11 81 =
28&nbsp;&nbsp;&nbsp;   2a 9a</PRE><PRE>12 54 04 &nbsp;&nbsp;&nbsp;  cd =
9a</PRE><PRE>22 68 40&nbsp;&nbsp;&nbsp;   9b 9a</PRE><PRE>10 20 =
78&nbsp;&nbsp;&nbsp;   d1 9a</PRE><PRE>12&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 84 9a&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; Exception to rule</PRE><PRE>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp; b6 9a</PRE><PRE>19 09 =
95&nbsp;&nbsp;&nbsp;   d9 9a</PRE><PRE>12 51 90&nbsp;&nbsp;&nbsp;   ac =
09</PRE><PRE>11 64&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  5b =
9a</PRE><PRE>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;20 9a&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Exception to =
rule</PRE><PRE>90&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; 2c 9a</PRE><PRE>10 88 19&nbsp;&nbsp;&nbsp;   4c =
9a</PRE><PRE>10 52 88&nbsp;&nbsp;&nbsp;   2d 9a</PRE><PRE>23 21 =
90&nbsp;&nbsp;&nbsp;   7a 9a</PRE><PRE>10 43 25&nbsp;&nbsp;&nbsp;   d8 =
9a</PRE><PRE>18 27 56&nbsp;&nbsp;&nbsp;   cc 9a</PRE><PRE>10 91 =
40&nbsp;&nbsp;&nbsp;   2b 9a</PRE><PRE>10 75 35&nbsp;&nbsp;&nbsp;   8b =
9a</PRE><PRE>16 99 16&nbsp;&nbsp;&nbsp;   7d 9a</PRE><PRE>15 56 =
85&nbsp;&nbsp;&nbsp;   ae 9a</PRE><PRE>10 84 98&nbsp;&nbsp;&nbsp;   8e =
9a</PRE><PRE>16 73 48&nbsp;&nbsp;&nbsp;   af 9a</PRE><PRE>13 10 =
75&nbsp;&nbsp;&nbsp;   ea 9a</PRE><PRE>12 06 96&nbsp;&nbsp;&nbsp;   d9 =
9a</PRE><PRE>15 75 04&nbsp;&nbsp;&nbsp;   8c 9a</PRE><PRE>15 40 =
80&nbsp;&nbsp;&nbsp;   2a 9a</PRE><PRE>13 83 51&nbsp;&nbsp;&nbsp;   a4 =
9a</PRE><PRE>13 69 60&nbsp;&nbsp;&nbsp;   2f 9a</PRE><PRE>16 31 =
75&nbsp;&nbsp;&nbsp;   c4 9a</PRE><PRE>13 16 10&nbsp;&nbsp;&nbsp;   3e =
9a</PRE><PRE>13 52 48&nbsp;&nbsp;&nbsp;   5d 9a</PRE><PRE>13 96 =
35&nbsp;&nbsp;&nbsp;   3c 9a</PRE><PRE>12 80 79&nbsp;&nbsp;&nbsp;   8f =
9a</PRE><PRE>13 52 48&nbsp;&nbsp;&nbsp;   f3 9a</PRE><PRE>13 05 =
40&nbsp;&nbsp;&nbsp;   a3 9a</PRE><PRE>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;13 =
9a&nbsp;&nbsp;&nbsp;  Exception to rule</PRE><PRE>05&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; e4 9a</PRE><PRE>13 65 =
32&nbsp;&nbsp;&nbsp;   d4 9a</PRE><PRE>21 72 10&nbsp;&nbsp;&nbsp;   8e =
06</PRE><PRE>29 16&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;  a4 =
9a</PRE><PRE>14 20 96&nbsp;&nbsp;&nbsp;   4d 9a</PRE><PRE>22 30 =
95&nbsp;&nbsp;&nbsp;   b8 06</PRE><PRE>83 73&nbsp;&nbsp;&nbsp;  =
&nbsp;&nbsp;&nbsp; b8 9a</PRE><PRE>16 99 16&nbsp;&nbsp;&nbsp;  =
&nbsp;b3&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Exception to =
rule</PRE></PRE>
<DIV>Phoenix<[EMAIL PROTECTED]> wrote in message &lt;<A=20
href=3D"mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>=
&gt;...</DIV>
<DIV>&gt;No I am not posting random numbers as a joke... I mean 16bit=20
because<BR>&gt;there are only 64k possibilities.&nbsp; to answer a few=20
other<BR>&gt;questions/threats the program was written in Visual =
Basic.&nbsp;=20
<BR></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt; So, even you concede that an encryption cannot be broken =
without=20
any<BR>&gt;knowledge of the algorithm?<BR></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;<BR>&gt; <A=20
href=3D"mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A><BR>&gt;<BR>&gt;fung=
us=20
wrote:<BR>&gt;&gt; <BR>&gt;&gt; Phoenix wrote:<BR>&gt;&gt; =
&gt;<BR>&gt;&gt; &gt;=20
Here is a better message with a better code.&nbsp; NO I will not=20
publicize<BR>&gt;&gt; &gt; my algorythm (my co-programmer forbids it) =
when it is=20
broken by one of<BR>&gt;&gt; &gt; you I will send it to someone =
(CoderX2, anyone=20
else who wants it) and<BR>&gt;&gt; &gt; have it evaluated.&nbsp; But I =
would=20
still like people to try and break it.<BR>&gt;&gt; &gt; Also its not =
8-bit it is=20
16.&nbsp; And I know that uncertainty about the<BR>&gt;&gt; &gt; =
algorythm would=20
add more bits.&nbsp; So here it is.<BR>&gt;&gt; &gt;<BR>&gt;&gt; =
<BR>&gt;&gt;=20
How do we know you're not just posting random numbers as a =
joke?<BR>&gt;&gt;=20
<BR>&gt;&gt; --<BR>&gt;&gt; &lt;\___/&gt;<BR>&gt;&gt; / O O =
\<BR>&gt;&gt;=20
\_____/&nbsp; FTB.</DIV></BODY></HTML>

=======_NextPart_000_0009_01BEAB6A.20649BA0==


------------------------------

Date: Mon, 31 May 1999 02:51:17 -0400
From: [EMAIL PROTECTED]
Subject: Re: OTP Problems

Matthias Bruestle wrote:
> 
> Mahlzeit
> 
> [EMAIL PROTECTED] wrote:
> > > [EMAIL PROTECTED] wrote:
> > > > > i) Anyone duplicating the CD can read messages
> > > > Let's see if I understand your point. You are critizing the OTP system
> > > > because anyone with the proper key can read the messages?  Can you
> > > > describe what is bad about this property?
> > > IMO he critizices the OTP because there is a CD which can be dublicated.
> > > With 3DES/IDEA/Blowfish/etc. you can memorize the key.
> > This contention _still_ does not make sense.  Do we really think that a
> > memorizble key is more secure than one that is not?
> 
> Depends on your opponents. A password in your brain can normally not
> be copied without notice, but it is normally possible with a CD. If
> for your application a key on a CD is better you can still write the
> 3DES/IDEA/Blowfish/etc. key to a CD.
> 
> > > For what OTP is really not usefull is storage encryption.
> > Why not?  With a proper definition of "time" (instance) an OTP can be
> > quite useful.
> Where is the difference berween
>    plaintext on harddisk
> and
>    cyphertext on harddisk and pad on another harddisk
> ?
> 
> In the both examples you have to lock away one harddisk, only in the
> second example you need twice as much harddisks.
> 

If you assume persistent store of both key and data your conclusion is
valid.  But there is no reason to make such an assumption.

> Mahlzeit
> 
> endergone Zwiebeltuete
> 
> --
> PGP: SIG:C379A331 ENC:F47FA83D      I LOVE MY PDP-11/34A, M70 and MicroVAXII!
> --
> How much for the leetle girls?
>                                 -- Stuart Woolford

------------------------------

From: Phoenix <[EMAIL PROTECTED]>
Subject: Re: 8Bit encryption code. Just try and break it. - code3.ecr (0/1)
Date: Mon, 31 May 1999 10:58:18 -0700

No I am not posting random numbers as a joke... I mean 16bit because
there are only 64k possibilities.  to answer a few other
questions/threats the program was written in Visual Basic.  
        So, even you concede that an encryption cannot be broken without any
knowledge of the algorithm?

                                [EMAIL PROTECTED]

fungus wrote:
> 
> Phoenix wrote:
> >
> > Here is a better message with a better code.  NO I will not publicize
> > my algorythm (my co-programmer forbids it) when it is broken by one of
> > you I will send it to someone (CoderX2, anyone else who wants it) and
> > have it evaluated.  But I would still like people to try and break it.
> > Also its not 8-bit it is 16.  And I know that uncertainty about the
> > algorythm would add more bits.  So here it is.
> >
> 
> How do we know you're not just posting random numbers as a joke?
> 
> --
> <\___/>
> / O O \
> \_____/  FTB.

------------------------------

From: [EMAIL PROTECTED] (Tom McCune)
Subject: Re: PGP Info wanted...
Date: Mon, 31 May 1999 17:58:19 GMT

=====BEGIN PGP SIGNED MESSAGE=====

In article <[EMAIL PROTECTED]>, "james b"
<[EMAIL PROTECTED]> wrote:
>Have just got PGP 6.0 and have a couple of questions regarding security of
>the key when using Windows 98.

My PGP pages may answer some of your questions.

>Just how secure is my passphrase from prying eyes?

Someone else has responded about a sniffer program that could be placed on
your computer.  If you really have high security needs, it's good to keep
your computer relatively secure from such attack with BIOS password, and
possibly other encryption software such as PGPdisk, ScramDisk, F-Secure
Desktop, etc.  I use a large aggressive dog in my home.  :-)

>Could an experienced user access the key, given a few hours to tinker with
>my computer?

Of course they must have actual access to your computer (above). There is no
problem in locating your key, but your private key is encrypted to your
passphrase, so if you have a truly secure passphrase, your key is not of
much value to them.

>I ask these questions as I constantly read people bemoaning the security
>features of Win 98.

Part of this concern is why you should use software to wipe your disk and
swapfile.  PGP 6.0 is suppose to prevent swapping of the passphrase to the
hard disk, but I doubt that is perfect.

>Is there an optimal keylength? (Or is that a very silly question)

I give comments on key type and key size on my pages, but basically a 2048
bit key is both fast and secure.

=====BEGIN PGP SIGNATURE=====
Version: PGP Personal Privacy 6.0.2
Comment: Tom McCune's PGP Page: http://www.borg.com/~tmccune/PGP.htm

iQCVAwUBN1LNt8MxrQ5/VTwtAQFqfwQAjvsNIV5u9bAO/wJDboDbjKqpqAFQfY+f
4eq+EjEX5/09NwyY8d+0J8rrpenUpK6gRe4Gql6DbCgx5bnALX/a9PENBPOEmEtu
+MBqDrw3iLAyBvl83a5kg9K5gXSkEYMHI2ThBxkkcWstlklrHCpX8RuBhZuizCX6
ajSwKGOn8gE=
=Na9E
=====END PGP SIGNATURE=====

------------------------------


** 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
******************************

Reply via email to