GPG Problem - invalid radix64 character

[Faramir]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

El 16-05-2011 12:35, Jerome Baum escribió:
...
> In the worst case, you may be looking at loosing everything from the
> corruption point onwards, assuming some kind of stream compression. This
> is IIRC the default for GnuPG when it encrypts. Otherwise you may be
...

> For the future, look at alternative ways to run this backup. Why
> ascii-armor? Why gpg? Encrypting w/ gpg has a huge potential for data
> loss in case of corruption -- of even a single bit. This isn't really an
> issue with gpg, it simply doesn't _by default_ operate in a manner
> designed for this. You may be able to tweak it, but how about this instead:

  I don't have an knowledge about compression algos, so I assume you are
right. However, we can disable GPG's compression to avoid that problem.
What is the advantage of encrypting data with OpenSSL over GPG?

  Best Regards
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCAAGBQJN0aSsAAoJEMV4f6PvczxAv64H/3AQuDMVDh3A5HQ+f85VPCfA
4+jtVeEoTMxLXVXoWoh4+OrZev+Wiyo/zEDIu3RpRs1o/EV7kmZUcFslZebeHbkr
laSqcBlJvcKhfknKnERkNb/oKBBxF+AsUhyi2P6GGc+3lvAQUx+F+0i/IJ6Y0Bix
F4Q4kVf8OU1tJC0G5Tr5c65tiEXakRhrjj0Cdf2ZTevG4WzGq87NGPaN6NoNXUaO
fJtQeYCvpaqTDyX4KDV0W/cQpDd2AnBMHATo7u5dfNA8aH5lF9+M2wfgsvuIL0jr
0rqkhcndeKwG2a25dk1eR3mG61/Y+5ZvBq7YCfMM678cRgvTJjtrvj5uoKg6AP0=
=7/bT
-----END PGP SIGNATURE-----