|
Posted by on May 6, 2005, 7:15 pm
If you were Registered and logged in, you could reply and use other advanced thread options
hello,
I want to send my data in encrpted form so that nobody in middle of
data tranmission can intercept that and modify it? which
encryption/decryption algorithm i use? where can i get source code for
that algorithm?
Can it be possible for me to do that? I want whatever is send from
my pc to other pc must go throgh scramble way not in plaintext?
Please suggest if this not possible any other ways. Please consider
both pcs are at distant locations. Using Redhat 9 linux.
|
|
Posted by Walter Roberson on May 7, 2005, 3:33 am
If you were Registered and logged in, you could reply and use other advanced thread options
: I want to send my data in encrpted form so that nobody in middle of
:data tranmission can intercept that and modify it? which
:encryption/decryption algorithm i use? where can i get source code for
:that algorithm?
Earlier you were asking a bunch of questions about IPSec;
you do not appear to have researched and absorbed the information
I gave you at that time.
As I said before:
The ONLY unbreakable encryption algorithm is One Time Pads.
EVERY algorithm that re-uses keys or computes new keys in a
deterministic way can be broken if the attacker gan gather enough
data.
There is NO exception. Unless the entropy of the encryption key
is at least as large as the length of the material to be encrypted,
the encryption can be broken.
The problem with One Time Pads is that you have to get the random
keys to the recipients ahead of time, through some -other- means.
: Can it be possible for me to do that?
NO, NO, NO, NO.
:Please suggest if this not possible any other ways.
Either use One Time Pads, with all the associated key
distribution problems, or GIVE UP ON THIS PROBLEM.
You CANNOT solve it. It is NOT SOLVABLE. It's like trying to
"square the circle" or find "the last digit of Pi": something
that has been mathematically proven to be impossible.
The business of encryption these days is NOT to write an
"unbreakable" code, because it is now known that you can't do that.
The business of encryption these days is to write an encryption
algorithm that is so difficult to solve that people don't even
bother trying because other ways are so much easier and
cheaper (e.g., kidnapping your family, or bugging your computer.)
There are a lot of potential algorithms out there that are
*hard* to solve. Very few people need encryption that would
take longer than an average of a million cpu-years to break.
There is a lot of room to make a name for yourself by writing
a really good encryption algorithm that is fast and secure --
but if you persist on trying to find an encryption algorithm
that "nobody" could ever break, then you aren't going to get
very far.
--
This signature intentionally left... Oh, darn!
|
| Similar Threads | Posted | | visual crypto readability | December 16, 2004, 12:19 am |
| Free GUI front-end to a crypto lib? | May 19, 2005, 5:00 pm |
| Data Recovery | November 28, 2004, 12:06 pm |
| data security | July 19, 2005, 2:39 pm |
| CPU that will not execute data? | September 21, 2005, 12:10 pm |
| Securing tcp data | November 10, 2005, 2:51 pm |
| Serious level HDD data protection | May 11, 2004, 2:40 am |
| Transfer of data via handshake | July 20, 2006, 3:54 am |
| Another computer with VA data has gone missing | August 10, 2006, 11:37 am |
| capturing data from Telnet possible? | November 29, 2007, 12:00 pm |
|
XML site map