-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John W. Moore III escribió:
> Faramir wrote:
>
>> If he is using ftp to upload the files... standard ftp sends username
>> and password unencrypted... so it could be sniffed...
>
> So? The UID and PW to access the FTP Server is not [or shouldn't
Hi all,
I might be doing something wrong here, but I can't seem to change the
default signing key. I've edited ~/.gnupg/gpg.conf, and set
default-key to . I've even setted it to 0x and but none of those works either.
When I try to sign a file (using --debug=64), it tells me that what
configuratio
> > $ cat /etc/passwd | aespipe | md5sum Password:
> > 9220c2e1d5a5a83710d020b04c306c24 - $ cat /etc/passwd | aespipe | md5sum
> > Password: 9220c2e1d5a5a83710d020b04c306c24 - $
> >
> ?
>
> Apples and Oranges. Consider:
Don't consider please. :-)
Original question was what are proper tools
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kiss Gabor (Bitman) wrote:
>>> The password is not random therefore every time you encrypt the same
>>> plaintext you got the same cryptfile.
>> No, you won't. All sound encryption schemes use a bit of random to
>> make the resulting ciphertext differ
> > The password is not random therefore every time you
> > encrypt the same plaintext you got the same cryptfile.
>
> No, you won't. All sound encryption schemes use a bit of random to make
> the resulting ciphertext different. In the easiest case this is called
> a salt and used to stop dictio
On Sat, 2 Aug 2008 19:36, [EMAIL PROTECTED] said:
> The password is not random therefore every time you
> encrypt the same plaintext you got the same cryptfile.
No, you won't. All sound encryption schemes use a bit of random to make
the resulting ciphertext different. In the easiest case this
