GPG Problem - invalid radix64 character

Turbo Fredriksson turbo at
Fri May 13 12:42:40 CEST 2011

On 13 maj 2011, at 12.08, Jerome Baum wrote:

> 1. What character is D0, 00, AD and DE? What can I look for
>  (to try to diagnose the problem/file)
> You can look for D0, 00, AD and DE.

Doh! I assumed that these where some code characters (meaning it's
something else in the actuall file).

Looking for these (egrep 'D0|00|AD|DE') basically gives me every single
line! They are everywhere, even in the very first file (which extracted
without any problems).

>  2. Is there ANYTHING I can do to get my data, exept making a
>  new archive (which, for various reasons, take about
>  two-three weeks)?
> First find the offending file, then you'll know your options.

Any (other) idea how I do that?

> I've googled this problem, but most (if not all) get this
> when/if receiving an ASCII armor via mail which messes
> things up. I doubt very much that's the problem here, since
> I'm using the exact, identical file I started with, not a
> copy (which is the result of mailing it)...
> But the files are ASCII armored and messed up, right?

They are ASCII armored, but I can't find a reason why they should
be messed up.

The commandline(s) are simple enough and doesn't ... rewrite anything
(other the 'transference' of clear text data to encrypted data by  
gpg), there
is no compression involved in any of the pipes and they are on a RAID5
with XFS,

I usually hate it myself when people say 'it used to work' and/or 'it  
before', but this setup have been thoroughly tested and verified and I'm
not a noob, not even with PGP/GnuPG...

> You should still try out the suggestions you found. It's possible  
> your file got corrupt even if it's "the exact, identifcal file [you]  
> started with" -- think bit rot.

To be honnest, I've heard about that before, but in my 20 years with  
I never, ever encountered it :). Data is always the same as the one  
you put there.


	1. FS errors (noticable one way or the other)
	2. Disk errors (also noticable one way or the other)
	3. Pipe (Command line) or program/application errors (possible GPG

> Personally I'd first find the file that's causing the problem, by  
> looking for those bytes. It's more difficult to solve a problem when  
> you can't see it.
> -- 
> Jerome Baum
> tel +49-1578-8434336
> email jerome at
> -- 
> PGP: A0E4 B2D4 94E6 20EE 85BA E45B 63E4 2BD8 C58C 753A
> PGP: 2C23 EBFF DF1A 840D 2351 F5F5 F25B A03F 2152 36DA

If something's hard to do, then it's not worth doing.
- Homer Simpson

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20110513/0ed829ef/attachment.htm>

More information about the Gnupg-users mailing list