Open AryaUN opened 7 years ago
jessek
commented
7 years ago You definitely want to be using the -l flag to ensure relative file paths. You'll also want to start each audit run inside of the target directory, e.g.
cd src hashdeep -rl . > ../known.txt cd ../dest hashdeep -rlak ../known.txt .
AryaUN
commented
7 years ago Thank you for your response.
Arya
On Mon, Mar 27, 2017 at 2:00 PM, Jesse Kornblum notifications@github.com wrote:
You definitely want to be using the -l flag to ensure relative file paths. You'll also want to start each audit run inside of the target directory, e.g.
cd src hashdeep -rl . > ../known.txt cd ../dest hashdeep -rlak ../known.txt .
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jessek/hashdeep/issues/369#issuecomment-289534021, or mute the thread https://github.com/notifications/unsubscribe-auth/AZXqRB6fb5xDPAlLccfWcnMzg3OzdHVwks5rp_lGgaJpZM4MlS20 .
-- Arya Ananda Ranasinghe Cell: 646-541-0002 email: ananda888@gmail.com
AryaUN
commented
4 years ago Hello Jesse,
Hope you are doing fine.
Question: My understanding is that hashdeep will not hash and error out any windows file names over 256 characters. Wanted to check with you and see if you have a fix for it by now please?
Thank you
Arya Ransinghe
On Mon, Mar 27, 2017 at 10:57 PM Arya Ananda Ranasinghe ananda888@gmail.com wrote:
Thank you for your response.
Arya
On Mon, Mar 27, 2017 at 2:00 PM, Jesse Kornblum notifications@github.com wrote:
You definitely want to be using the -l flag to ensure relative file paths. You'll also want to start each audit run inside of the target directory, e.g.
cd src hashdeep -rl . > ../known.txt cd ../dest hashdeep -rlak ../known.txt .
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jessek/hashdeep/issues/369#issuecomment-289534021, or mute the thread https://github.com/notifications/unsubscribe-auth/AZXqRB6fb5xDPAlLccfWcnMzg3OzdHVwks5rp_lGgaJpZM4MlS20 .
-- Arya Ananda Ranasinghe Cell: 646-541-0002 email: ananda888@gmail.com
-- Arya Ananda Ranasinghe Cell: 646-541-0002 email: ananda888@gmail.com
jessek
commented
4 years ago Hi Arya,
I regret to say I have not worked on Hashdeep in some time and this issue has not been fixed.
sorry,
On Fri, Sep 13, 2019 at 7:46 PM AryaUN notifications@github.com wrote:
Hello Jesse,
Hope you are doing fine.
Question: My understanding is that hashdeep will not hash and error out any windows file names over 256 characters. Wanted to check with you and see if you have a fix for it by now please?
Thank you
Arya Ransinghe
On Mon, Mar 27, 2017 at 10:57 PM Arya Ananda Ranasinghe ananda888@gmail.com wrote:
Thank you for your response.
Arya
On Mon, Mar 27, 2017 at 2:00 PM, Jesse Kornblum notifications@github.com wrote:
You definitely want to be using the -l flag to ensure relative file paths. You'll also want to start each audit run inside of the target directory, e.g.
cd src hashdeep -rl . > ../known.txt cd ../dest hashdeep -rlak ../known.txt .
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jessek/hashdeep/issues/369#issuecomment-289534021, or mute the thread https://github.com/notifications/unsubscribe-auth/AZXqRB6fb5xDPAlLccfWcnMzg3OzdHVwks5rp_lGgaJpZM4MlS20 .
-- Arya Ananda Ranasinghe Cell: 646-541-0002 email: ananda888@gmail.com
-- Arya Ananda Ranasinghe Cell: 646-541-0002 email: ananda888@gmail.com
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
-- Jesse Kornblum jessekornblum@gmail.com
AryaUN
commented
4 years ago Thank you Jesse so much for your response. Much appreciated!
Arya
On Sun, Sep 15, 2019 at 3:15 AM Jesse Kornblum notifications@github.com wrote:
Hi Arya,
I regret to say I have not worked on Hashdeep in some time and this issue has not been fixed.
sorry,
On Fri, Sep 13, 2019 at 7:46 PM AryaUN notifications@github.com wrote:
Hello Jesse,
Hope you are doing fine.
Question: My understanding is that hashdeep will not hash and error out any windows file names over 256 characters. Wanted to check with you and see if you have a fix for it by now please?
Thank you
Arya Ransinghe
On Mon, Mar 27, 2017 at 10:57 PM Arya Ananda Ranasinghe < ananda888@gmail.com> wrote:
Thank you for your response.
Arya
On Mon, Mar 27, 2017 at 2:00 PM, Jesse Kornblum < notifications@github.com> wrote:
You definitely want to be using the -l flag to ensure relative file paths. You'll also want to start each audit run inside of the target directory, e.g.
cd src hashdeep -rl . > ../known.txt cd ../dest hashdeep -rlak ../known.txt .
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/jessek/hashdeep/issues/369#issuecomment-289534021 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AZXqRB6fb5xDPAlLccfWcnMzg3OzdHVwks5rp_lGgaJpZM4MlS20
.
-- Arya Ananda Ranasinghe Cell: 646-541-0002 email: ananda888@gmail.com
-- Arya Ananda Ranasinghe Cell: 646-541-0002 email: ananda888@gmail.com
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
-- Jesse Kornblum jessekornblum@gmail.com
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jessek/hashdeep/issues/369?email_source=notifications&email_token=AGK6URGW2S43OTMTWYIN3RLQJXOIPA5CNFSM4DEVFW2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6XKZYI#issuecomment-531541217, or mute the thread https://github.com/notifications/unsubscribe-auth/AGK6URFL44AGOZ6VQ6E6KPLQJXOIPANCNFSM4DEVFW2A .
-- Arya Ananda Ranasinghe Cell: 646-541-0002 email: ananda888@gmail.com
Hi, Hope someone can assist me here.
Using Hashdeep64 to generate hash (.txt file) and using the .txt file on audit mode to verify. I've created 2 similar folders (using copy) with the same exact set of files. Generated hash with -e -r -b options on folder1. Next on audit mode on folder2 to audit against the .txt, I use -r -b -a -k options. I get audit failed. Did the same again with -l instead of -b option. Same results: audit failed. Can someone assist me and tell me what I am doing wrong here please? Thank you for your help...