Re: Anything to this mumbo jumbo I found while surfing the net?
From: flip (flip_alpha@safebunch.com)
Date: 02/12/03
- Next message: Johannes Schnitzer: "Re: Help: using private key to encrypt in crypto++"
- Previous message: flip: "Re: CRT Question ... PLEASE Disregard, I figured it out~~~"
- Next in thread: Paul Crowley: "Re: Anything to this mumbo jumbo I found while surfing the net?"
- Maybe reply: Paul Crowley: "Re: Anything to this mumbo jumbo I found while surfing the net?"
- Maybe reply: Bob Mathews: "Re: Anything to this mumbo jumbo I found while surfing the net?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "flip" <flip_alpha@safebunch.com> Date: Wed, 12 Feb 2003 14:04:49 -0800
See the thread "Meganet Strikes Back"
This was also discussed before and IIRC as "Snake Oil"!!!
HTH
"No One" <no-one@home.com.cotse.net> wrote in message
news:Y3VydHdpbGw=.a2ac16f3651c5ba69ac3cdd79ef14992@1045086972.cotse.net...
> Anyone care to comment on the following?
>
> Found at: http://www.meganet.com/Technology/intro.htm
>
>
> We believe there is one very simple rule in encryption - if someone can
> encrypt data, someone else will be able to decrypt it. The idea behind
> VME is that the data is not being encrypted nor transferred. And if
> it's not encrypted and not transferred - there is nothing to break. And
> if there's nothing to break - it's unbreakable.
>
> How does it work?
>
> The basis of VME is a Virtual Matrix, a matrix of binary values which
> is, in theory, infinite in size and therefore contains no redundant
> values. The data to be encrypted is compared to the data in the Virtual
> Matrix. Once a match is found, a set of pointers that indicate how to
> navigate inside the Virtual Matrix is created. That set of pointers
> (which is worthless unless pointing to the right Virtual Matrix) is
> then further encrypted using dozens of other algorithms in different
> stages to create an avalanche effect. The result is an encrypted file
> that even if decrypted is completely meaningless since the decrypted
> data is not the actual data but rather a set of pointers. Considering
> that each session of VME uses a unique Virtual Matrix, and that the
> data pattern within the Virtual Matrix is completely random and non-
> redundant, there is no way to derive the data out of the pointer set.
>
> Stated simply, the content of the message is not sent with the
> encrypted data. Rather, the encrypted data consists of pointers to
> locations within a virtual matrix, a large (infinitely large in
> concept), continuously changing array of values. VME provides a data
> security method and apparatus that provides an exceptional degree of
> security at low computational cost.
> VME uses a very large key of one million bits or more which creates a
> level of security much higher than any other existing method. The key
> is not transferred but is instead created from a file of any size that
> is available on both a computer used to send a secure message and a
> computer used to receive a secure message. A smaller, Specific
> Transaction Key is sent end-to-end and is used in conjunction with the
> very large key to avoid a security hazard in instances where the same
> file is used repeatedly to create the very large key.
>
> A central Virtual Matrix algorithm is surrounded by a myriad of other
> algorithms. A single byte may be encrypted many, many times, each
> successive result being passed to another algorithm in what may be
> regarded as a random path determined by reseeding of a random number
> generator at various junctures using values from the very large key,
> the smaller key and various other user supplied parameters. These
> parameters include, for example, source user, destination user, file
> name, save-as file name, and description.
>
> An optional higher level of security is available. If the message is
> secured using the same string as the file name and save-to file name,
> then when unlocking is attempted the first time, the original file will
> be overwritten, affording only single opportunity for the message to be
> unlocked.
>
> A message may be secured in accordance with various options specifying
> an intended audience, including Global, Group, Specific and Private
> options. Global allows anyone having a copy of the data security
> software to decrypt the message providing that person has the correct
> keys and is able to supply parameters matching those with which the
> message was secured. Group allows the possibility of successful
> decryption by any of a number of users within a group identified by its
> members having copies of the software program with a common prefix.
> Specific allows only a user having a particular numbered copy of the
> software program to decrypt. Finally, Private allows decryption only by
> the same software copy used to secure the message originally. Without
> the correct keys and parameters, it is impossible for the message to be
> unlocked.
>
> Security can be further enhanced by defining a date range wherein the
> data can be decrypted correctly, hence preventing lengthy efforts to
> break the code by brute computational force.
>
>
>
- Next message: Johannes Schnitzer: "Re: Help: using private key to encrypt in crypto++"
- Previous message: flip: "Re: CRT Question ... PLEASE Disregard, I figured it out~~~"
- Next in thread: Paul Crowley: "Re: Anything to this mumbo jumbo I found while surfing the net?"
- Maybe reply: Paul Crowley: "Re: Anything to this mumbo jumbo I found while surfing the net?"
- Maybe reply: Bob Mathews: "Re: Anything to this mumbo jumbo I found while surfing the net?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|