Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Feature] Don't follow symbolic links #225

Open
simsong opened this issue Dec 7, 2012 · 4 comments
Open

[Feature] Don't follow symbolic links #225

simsong opened this issue Dec 7, 2012 · 4 comments

Comments

@simsong
Copy link
Collaborator

simsong commented Dec 7, 2012

Converted from SourceForge issue 2308881, submitted by jessekornblum

Can you include a new command line option to exclude traversal of symbolic/hardlinks: sth. like '--no-links-followed'

This way moved/backuped data can be properly compared, even when relative directory paths are given in links. Currently the moved/backuped files show a broken destination and the comparison fails.

Using '-o bcpfsd' is not possible, because links should be digested also, but not followed.
@simsong simsong closed this as completed Dec 7, 2012
@argyle77
Copy link

argyle77 commented Feb 1, 2015

Why was this closed? Seems like a good feature. Verify symbolic links, but don't follow.

@simsong
Copy link
Collaborator Author

simsong commented Feb 1, 2015

Sure. Will you implement it?

@simsong simsong reopened this Feb 1, 2015
s-d-adams added a commit to s-d-adams/hashdeep that referenced this issue Feb 20, 2018
@s-d-adams
Implemented Feature jessek#225 - Don't follow symlinks.
d994b4f 
The flag '-R' causes hashdeep to hash the output of readlink instead of
following the file.

Tested on Ubuntu 16.04 and Mac OS X High Sierra.
Not supported on Windows.
@JDLH
Copy link

JDLH commented Dec 1, 2024

Sure. Will you implement it?

It looks like s-d-adams implemented this feature in their fork of hashdeep back in 2018, and offers this fix back here to main hashdeep as PR #382. That PR is still open, awaiting a response.

I am presently using sha256deep on macOS Sonoma 14.7.1, and it is covering way more files than I intended because it is following symlinks. I would really benefit from having the proposed -R flag. I am glad to have sha256deep, so thank you for your work to develop it, but I would be even more glad to have this feature.

@simsong
Copy link
Collaborator Author

simsong commented Dec 1, 2024

It looks like I need to implement GitHub actions on this repo so that we can test and validate pull request before accepting them.

If you want to do a pool request that implements GitHub Actions, I'll take a look at it. Otherwise, I'll add that to my things to do list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@JDLH @simsong @argyle77