> Moses wrote:
> > O...I see.
> > I've get the correct hash on Linux..., thank you all! :-)
> >
> > The problem remains now is how to get the same hashing on Windows,
> > because echo on windows does not have -n flag:
> > > echo -n AAA
> > -n AAA
> > so, on windows "echo -n AAA | gpg --p
Graham Todd wrote:
> John, I respect your point of view and I shall defend to the death your
> ability to say it. However, whether the US Navy uses slang of this
> kind doesn't make it part of the English language, nor whether these
> things can be found in the histories of the CIA and NSA is irre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 06 Sep 2007 14:34:04 -0500
John Clizbe <[EMAIL PROTECTED]> wrote:
> From a wiki of US Navy slang
> (http://www.mshtawy.com/en-wiki.php?title=U.S._Navy_slang):
>
> Cryppy/Cryppy Critter: Cryptographer, also seen on a highway near
> the Cry
Noiano wrote:
> to choose and why. Is it one more secure than the other? I don't think
> so but I think there are some difference that make one algorithm
> suitable for some uses than the other.
There was a lengthy discussion on this list about the differences between
RSA and DSA a few weeks ago.
[EMAIL PROTECTED] wrote:
>>Message: 9
>>Date: Thu, 06 Sep 2007 07:26:19 -0500
>>From: "Robert J. Hansen"
>>Subject: Re: RSA or DSA? That's the question
> ..
>>While I agree that a cryppie's definition of "break"
>>is not the same as a practical break,
> ..
> ..
> a little OT here:
More than, and
[EMAIL PROTECTED] wrote:
>>Message: 9
>>Date: Thu, 06 Sep 2007 07:26:19 -0500
>>From: "Robert J. Hansen"
>>Subject: Re: RSA or DSA? That's the question
> ..
>>While I agree that a cryppie's definition of "break"
>>is not the same as a practical break,
> ..
> ..
> a little OT here:
More than, and
Robert J. Hansen wrote:
> Werner Koch wrote:
>> I have not heard of a SHA-1 collision yet. IIRC it still takes
>> something in the range of 2^60.
>
> Rechberger and Cannière had some interesting things at CRYPTO 2006--I
> don't recall the details, but it sounded like a partial preimage attack,
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
John Clizbe wrote:
> The *only* way to get the pejorative connotation you refer to is to
> conflate cryppy with the homophone you cite, crippie - something that
> is a bit difficult to do via written text.
Or even in conversational speech. The co
Werner Koch wrote:
> I have not heard of a SHA-1 collision yet. IIRC it still takes
> something in the range of 2^60.
Rechberger and Cannière had some interesting things at CRYPTO 2006--I
don't recall the details, but it sounded like a partial preimage attack,
not just a simple collision. They o
vedaal wrote:
-BEGIN PGP SIGNED MESSAGE-
...
...
...
...
...
...
...
-BEGIN PGP SIGNATURE-
sorry,
hushmail insisted on duplicating the periods,
there should be only one period instead of two on the lines
indicated,
if the message is copied and the extra period is delet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>Message: 9
>Date: Thu, 06 Sep 2007 07:26:19 -0500
>From: "Robert J. Hansen"
>Subject: Re: RSA or DSA? That's the question
..
>While I agree that a cryppie's definition of "break"
>is not the same as a practical break,
..
..
a little OT here:
..
i h
On Thu, 6 Sep 2007 14:26, [EMAIL PROTECTED] said:
> E.g., it took MD5 almost a decade to go from a purely academic break to
> an actual collision, but it took SHA-1 under a year.
I have not heard of a SHA-1 collision yet. IIRC it still takes
something in the range of 2^60.
I should not have ta
On Thu, Sep 06, 2007 at 06:55:59AM -0700, paladino wrote:
>
> Hi, I'm sorry to jump right in with a dumb question, but I've tried doing
> some research myself and I have to confess to much of this being way over my
> head.
>
> I work for a University that uses GnuPG to encrypt files to send out t
paladino wrote:
> When I look at the file here, immediately before it is encrypted, the 13
> white spaces are still there. When I look at the file at the vendor,
> immediately after decryption, the 13 spaces are gone.
Have you tried a test decryption on your end? E.g., encrypt the file
with your
Hi, I'm sorry to jump right in with a dumb question, but I've tried doing
some research myself and I have to confess to much of this being way over my
head.
I work for a University that uses GnuPG to encrypt files to send out to
various vendors.
We're having a very odd situation right now with o
Werner Koch wrote:
> that does not mean you or anyone in the world is able to break it now
> or in the next couple of years.
While I agree that a cryppie's definition of "break" is not the same as
a practical break, I think it's dangerous to make predictions about how
long it takes a cryptographic
Noiano wrote:
> to choose and why. Is it one more secure than the other? I don't think
> so but I think there are some difference that make one algorithm
> suitable for some uses than the other.
Not really. Some places have to conform with regulations or laws which
might demand RSA. Some people
On Thu, 6 Sep 2007 11:26, [EMAIL PROTECTED] said:
> I was thinking to create one rsa key and one subkey for encryption. What
> do you think? What do you advise?
If you want to be standard conform and your goal is best
interoperability you need to use DSA and Elgamal. These are the MUST
algorith
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everybody
as you can see my key is about to expire and I need to create a new one.
When I created it I didn't know which algorithm was the best choice and
I just chose the first option. Now I still don't know which is the best
to choose and why.
19 matches
Mail list logo