Re: Possible new crypto system

On Tue, 17 Feb 2009 11:31:21 -0800 (PST), BDthatsme
<bdggetcetc@xxxxxxxxxxxxxxxxxx> wrote:

I was just wondering about something. I'm only interested in
cryptography as a layperson. So I was wondering how good of an
algorithm I have come up with. Comments appreciated.
One of the rules of cryptography is that crypto systems designed by
laypeople almost invariably have mistakes in them. I know, I still
have the scars. Be prepared to be very heavily criticised if you do
ever post anything detailed. Expect that your idea will not turn out
to be as good as you think it is.


It's actually fairly simple. I won't go into detail in case it is
actually something worth something. (sorry for being purposely
abstruse)
Standard cryptographic advice is never to touch any secret algorithm
with a barge pole. Only if the algorithm is public and has stood up
to some extremely heavy analysis is it worth considering. Secrecy
must lie in the key, not in the algorithm. Comnplete details of DES,
AES and others are all published.


My question is, if I had a way to encrypt a "text" (some binary data
set) of any length, fairly easily and quickly (probably about as fast
or faster than any existing system), using certain "functions", that
would also decrypt fairly easily and quickly, and, if you knew what
the functions were that caused the encryption, and tried to brute-
force an answer, or maybe even tried to be a little intelligent and
creative about it, but the permutations were, for a fairly simple
encrypt/decrypt key of about 400 bits, about
6.5331862350007090609669026715806e+77 "operations", would that make
the system basically unbreakable?
Those are the basic requirements for any crypto system. If it cannot
encrypt and decrypt at a reasonable speed and with reasonable security
then it is worthless.


If you take that large number and divide by 1 trillion (using quick
rounded calculations and numbers) that say a supercomputer could do as
operations per second (+/-), and divide by 60 to get minutes, and then
60 again to get hours, and then 24 to get days and then 365 to get
years, you end up with 2.0716597650306662420620569100649e+58 years to
calculate a solution by brute force. (potentially)
Any good modern crypto system is proof against brute force. Unless we
have seen the exact details of your system then we will not know if
there is a weakness in it that reduces its security to less than brute
force.


That number seems SO large, that, even if some tricks were used (and I
know that depends on the way the system works, so there could be some
"cute tricks" you could use to figure it out quickly), it seems like
it would be unbreakable.
Available "tricks" depend on the details of the algorithm you are
using. Many of the breaks in previous proposed cyphers have depended
on the details of each specific algorithm.


I don't know if this is the right place to ask this type of a
question, but I hope someone who knows something about this stuff can
comment.
By all means ask, but we need to see the detail of the algorithm. You
have to make your idea public if it is to have any acceptance. If it
does work then you can make your money from consultancy. If it
doesn't then just buy yourself a beer. :)

rossum


Thanks.

.

Relevant Pages

  • Re: Encryption key changing the encryption logic.
    ... >>decides among various elementary crypto operations based on what it sees ... >>adversary knows which key bits select which algorithm and, in practice, N ... > or two rounds of a different block cipher. ... this design is covered under the 1-of-N discussion and your design is ...
    (sci.crypt)
  • Re: Is it possible to encrypt without a key ?
    ... Start by learning about crypto, you can get the Handbook of Applied ... Encryption, with a fairly good algorithm, is usually a fast process ... >extractor easily ... >generic extractor by desassembling any extractor of any master. ...
    (sci.crypt)
  • Re: How much must be revealed
    ... You can convince peope to trust your /algorithm/ by publishing it. ... You can convince people that you are not a liar by providing source code. ... Not only because the algorithm cannot be ... Microsoft-built crypto software in the black. ...
    (sci.crypt)
  • Re: SSH - securing the port
    ... Exactly how do you plan to use your knowledge of SSH ... That best form of crypto is the one that exactly one person ... unpublished algorithm. ... mathmatics out at the limits of human ingenuity, not secret decoder ...
    (comp.unix.solaris)
  • RE: How to use szOID_PKCS_1 ID to encrypt?
    ... Even with only four bytes you don't encrypt data directly with PKCS#1. ... I have to encrypt a 4 byte value with PKCS#1 algorithm. ... API is returing following error code. ... This is really my first attempt to use Crypto API and new to RSA algorithms. ...
    (microsoft.public.platformsdk.security)