Closed sbond75 closed 4 months ago
Also I am on the latest commit, 295e58a
Hi, thanks a lot for opening this. I pushed a fix to master just now at https://github.com/0x09/hfsfuse/commit/529cb8b37f6305cc3719822aba687b59c27df822 which resolves it. I'll publish a release with this shortly. Let me know if you try this out and run into any issues.
edit: release with these changes added at https://github.com/0x09/hfsfuse/releases/tag/0.214
Nice, that fixed it. I have another slight issue which I think I will make a new issue for.
Hello,
After using hfsfuse to transfer some files from an HFS+ drive with rsync, I noticed that running ls on some symlinks shows random bytes appearing, appended at the end of the actual destination. For example:
A few more examples can be seen in this rsync output from when I was copying from the HFS+ drive:
Strangely, after remounting, the issue sometimes goes away when using
ls -la
to see what the symlinks point to, but re-running rsync shows that rsync is detecting differnces in what the symlinks point to:This seems like it might be a reading out-of-bounds type of issue - maybe somewhere in the code it reads outside the string or doesn't put a null terminator early enough. Where could this problem be in the code - maybe where link resolution happens like in
hfsfuse_readlink
orhfsfuse_opendir
?