Hi!
For some reason I didn't see or receive the reply to this bug report.
Anyway, thanks for the explanation, but I am not sure what to make of it -
on the one hand, it confirms the bug (unrar incorrectly mangles filenames
by trying to recode them), but on the other hand, it's still clearly a
bug.
And while not as bad as, say, a buffer overflow, this could still have
security implications, as unrar will try to process a different file
than what the user specified, which could result in unwanted information
disclosure.
I would agree that this is not a terribly likely scenario, but I don't
see a reason why this bug shouldn't get fixed eventually, and I certainly
wouldn't call it harmless - I lost some data due to this bug, as some
perfectly fine archives were flagged as undecodable due to this spurious
error and were deleted before I understood that this is just unrar being
broken and not actually a problem in the archives themselves.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schm...@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
