Guy Macon wrote:
> Ah. You are now asking about verification. Before you were asking
> about encryption.
No, the question was always the same. You simply didn't understand
it any more than you know the answer TO any of it.
Don't guess. Google it or STFU, or you'll look like a buffoon....
>
> There are a bunch of ways to add verification to the above encryption
> scheme. One simple way is this:
>
> When you channge "I have a secret message." to
> "a.agssmat raacese vah Ie", send it to me like this:
>
> The encrypted message is "a.agssmat raacese vah Ie".
> The original message has an odd number of "a" characters,
> an even number of spaces and an odd number of "e" characters.
> ... and so on for hundreds of verification tests.
What nonsense. Nothing but made up gibberish.
The answer, in case the OP still wants to know, is that modern
crypto software hashes the password you enter when you create an
encrypted container and then compares a hash of the one you enter
when you attempt to access it with that stored hash. Since hashing
is a one way function it's "impossible" to learn your password by
examining the hash.
Yeah, it really is that simple.
That's why having good/strong hash algorithms is at least as
important as having good crypto algorithms.
> These are, of course, simple examples I made up so that they
They're also totally bullshit examples you made up.

~~~~~~~~~~~~~~~~~~~~~
This message was posted via one or more anonymous remailing services.
The original sender is unknown. Any address shown in the From header
is unverified. Please report spam or misuse to the remailer-operator:
<nightmix@fahr-zur-hoelle.org>