On Thu, 2012-12-20 at 17:18 -0400, Joey Hess wrote: > Ian Campbell wrote: > > I expect this is because sha256sum quotes the checksum if the filename > > contains > > certain characters: > > I've put in a fix for this. It will avoid the \ for new files added, > but still allows for it in existing annexed files. > > You can migrate files without changing the backend, to get rid of the \
Neat, thanks.
> > The other two have files ending in '.?.ogg' and '.".ogg' which g-a appears
> > to
> > treat as part of the extension for SHA256E purposes:
>
> > Does g-a treat suffixes from the second last "." on purpose? I should
> > probably
> > be using the SHA256 (no E) backend anyway.
>
> It does, with the intent of handling .tar.gz etc.
Ah, that's pretty obvious now you mention it.
> I've also put in a fix for this, migrating existing files will exclude
> non-alphanumerics from extensions.
Great, looking forward to the next release (direct mode too, yay!).
> I am going to leave this bug open since at least the WORM and URL
> backends can still get keys that contain unusual characters like \
> It may be worth changing these other backends eventually.
OK by me.
Thanks,
Ian.
--
Ian Campbell
May you do Good Magic with Perl.
-- Larry Wall's blessing
signature.asc
Description: This is a digitally signed message part
