On 07/29/2014 08:24 PM, pedro.mar...@ml1.net wrote:
On 07/29/2014 12:44 AM, flapflap wrote:
pedro.mar...@ml1.net:
You lost me with the "emails" stuff. ( i don't know what do they have to do
in this topic)
What I'm saying it is pretty easy, I'm bad with passwords, so i rather
damage the key t
ghtest bit. You might make the attacker laugh, though.
Don't be creative! You need either a good passphrase or good physical
protection or both, not some mangling of data.
I wasn't aware of this, thanks for the info!
("i made good" to ask here before doing creative stuff..
y to use Brute force on it. He will need to
repair the key before ( and good luck for that )
Note. I think that for extra security i will generate the keys in a usb
stick that i'll overwrite
with zeros after corrupting the private key. This will prevent some
smart mallory from using
softwar
On 07/28/2014 08:04 PM, Pete Stephenson wrote:
> I told to my self that it would be interesting as securing method to
sign
> stuff with a private key "with out having the public key". this
would mean that only
> the person who has public key would have access to the data with out
needing
> a p
keyring, and then
i imported only the secret key. For my surprise there was also the
public key.
Is there anyway to only import the secret key?
Thanks again,
Pedro markov
On 27/07/14 23:51, pedro.mar...@ml1.net wrote:
Hi,
I'm a new user to the GPG world, and i haven't find informati
Hi,
I'm a new user to the GPG world, and i haven't find information
about the "CRC" error when importing a key.
What does CRC means?
When importing a corrupted key the following message apears:
gpg: CRC error; 9BAD9F - 00F1D7
gpg: read_block: read error: invalid keyring
gpg: import from
