Peer-review my encryption methodology?

[rascalcode]

Hi - I am Ron, and my interest is writing alternate encryption methods. I thought this might be a good place to get come comments on my methodology - sort of a peer review.

I think DES and AES are unintuitive and just messy and my attempt is to use simple procedures that can be combined to produce Cryptographically Secure (CS) encryption procedures.

I have written a subroutine library that I think is very powerful and can allow almost anyone to write their own powerful encryption code. I am not asking for a critique of the code, but an analysis of the ideas. I subset I can write unbreakable code (55,000 bit encryption) with keys each as long as 4,000 UTF-8 bytes (key***rd of text file content was the idea.)

Is this the right place? Here is a teaser...

[url]http://rascalcode.home.bresnan.net/case.html[/url]

Ron.

[gordo]

try here. [url]http://triviasecurity.net/***rds/index.php/***rd,25.0.html[/url]

[rascalcode]

Thanks. I'll give.em a try.

[anna2020]

By going to the ridiculous extreme of 55,000 bit encryption I thought it was clear that remaining in a "256-bit" world was a little old-hat. I was trying to expand thinking to something beyond that by demonstrating that you could achieve good encryption in other ways - more simple ways than AES.

I thought that it might be a good idea to expand ideas a bit. I know prof's have lesson plans worked out on AES SPNs. I just wonder if surrendering your ability to think is in the best interests of the future. I s***est that progress is not made by followers, or those who defend the Status Quo.
.......................................................................................

[sasi12]

A formula used to turn ordinary data, or "plaintext," into a secret code known as "ciphertext." Each algorithm uses a string of bits known as a "key" to perform the calculations. The larger the key (the more bits), the greater the number of potential patterns can be created, thus making it harder to break the code and descramble the contents.

Most encryption algorithms use the block cipher method, which codes fixed blocks of input that are typically from 64 to *28 bits in length. Some use the stream method, which works with the continuous stream of input.
---------------------------------------------------------------------------------------------------------------------------
[u

[seri]

The dialog box below from the ScramDisk encryption program shows the various algorithms offered to encrypt data on your hard disk. The free, open source, legacy version of ScramDisk is available at [url]www.samsimpson.com[/url]. The accompanying descriptions and performance comparisons from the ScramDisk documentation manual are provided because they provide a brief and clear summary of current-day secret key encryption algorithms.

....................................................................
[url=http://kratom.org]kratom[/url]
[url=http://www.smartlipotopdocs.com/]Smart Lipo[/url]

[Eddiewilson]

Hi,

Thanks you provide great information and best way to explain it.

Thanks
Eddie wilson

[akitodito]

File-Sharing Solicitors Under Investigation

wow.. this has been long overdue

[Joneswilliamsc]

try here. [url]http://triviasecurity.net/***rds/index.php/***rd,25.0.html[/url]

Hey I also interested in Encryption. But I have searched on Google but not able to search the correct information from there. After reading this post I got a lot of information here. The link which you have given here it provides very nice information for Encryption.