Re: Still on the Arithmetic coder

Thanks for the reply - a little bit over the top though. I'm only testing
the ground, not proposing any radical new theory. Its just as I said, when,
under certain circumstances, the coder is interrogated it seems to be able
to produce a picture of possible outcomes. Nothing more or less. The larger
bit sequencing was to see if this is what is really happening and if there
was something worth investigating. End of story.

Regards

"David A. Scott" <daVvid_a_scott@xxxxxxxxx> wrote in message
news:Xns975841AD97561H110W296LC45WIN3030R@xxxxxxxxxxxxxxxxxx
> "Learning_boy" <Newbie@xxxxxxxxxxx> wrote in
> news:43d9f493$0$18619$5a62ac22@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:
>
>>
>> Actually, the reason for the migration to greater than 64bit was that
>> it seemed that under certain circumstances the arithmetic coder became
>> a linear predictor. To me this seemed to suggest that frequencies
>> ahead might be seen(predictable) - not sure on that yet - or that as a
>> linear predictor it might be useful as a cryptography tool.
>>
>>
>
> Actually cryptography has more hype written about it than compression.
> But the advantage of working in compression is that when some blow hard
> writes reems of documenation on how well a compression method is one can
> write a test program and compare it directly with some other method then
> the average user can use his own test files to actaully see how they
> differ. The bad thing is still the blow hards will write and publish
> reems of material and not all will be aware of the tests.
>
> All that said aside crypto is my first love. Many make mistakes even me
> when we first play the crypto game but it is more fun. The said thing is
> it often is not as testable as compression. But shannon has married the
> two and is a good why to approach it. The reason my arithmetic is 64 bits
> and bijective is more because of crypto than any need in real compression.
>
>
> David A. Scott
> --
> My Crypto code
> http://bijective.dogma.net/crypto/scott19u.zip
> http://www.jim.com/jamesd/Kong/scott19u.zip old version
> My Compression code http://bijective.dogma.net/
> **TO EMAIL ME drop the roman "five" **
> Disclaimer:I am in no way responsible for any of the statements
> made in the above text. For all I know I might be drugged.
> As a famous person once said "any cryptograhic
> system is only as strong as its weakest link"
>


.

Relevant Pages

  • Re: AES and Diehard
    ... >you could employ kill file, ... The result of encryption which might eventually develop ... a standard for crypto the 'diversity' of interests is ... compression algorithm could exploit in order to compress. ...
    (sci.crypt)
  • Re: Compression and crypto
    ... Modern crypto people I guess its for job security only want to make ... assumptions base on complexity by saying its provable secure because ... I used most peoples compression with AES the task would be to hard. ...
    (sci.crypt)
  • NSA and crypto
    ... To the guy who wanted the NSA to test his crypto. ... The field of compression is wide open and ... the nice thing is you can test bijective compression ...
    (sci.crypt)
  • Re: Tiers
    ... Joe Peschel wrote in ... crypto I think compression is far more visible. ... But if you really have good compression. ... My Crypto code ...
    (sci.crypt)
  • Re: Binary String Transform
    ... type of coder other bijectiv methods needed at end. ... string if ones and zeroes based directly on some universal code ... be runs of 2 the more longer the runs the better the compression. ... My Crypto codehttp://bijective.dogma.net/crypto/scott19u.ziphttp://www.jim.com/jame...version ...
    (comp.compression)