jessek
[Feature] Output Options
Converted from SourceForge issue 1424766, submitted by nobody
Would like to see some Output Options added, similar to those of the ReHash utility (also at SourceForge). E.g. -out:uphex , -out:base64 , etc.
@simsong I was wondering why this issue has been closed? Has the support for base64 been added already and if yes, please provide usage for it.
Sorry. I must have closed this in error.
What is the purpose of this request? How would it improve the functionality of the program? It doesn't appear that this improvement is wroth the added code complexity and testing requirements.
Currently I'm in middle of an implementation which requires base64 encoded hashes only. I've been using hashdeep but couldn't find the specific options for base64 output.
I've since found a workaround which uses xxd to convert the hexdump returned by hashdeep to base64 output.
Still, it would be nice if hashdeep did that on its own.
What xxd option are you Using to convert hex to base64?
Sent from my phone.
On Apr 15, 2017, at 6:36 AM, The Half Blood Prince [email protected] wrote:
Currently I'm in middle of an implementation which requires base64 encoded hashes only. I've been using hashdeep but couldn't find the specific options for base64 output. I've since found a workaround which uses xxd to convert the hexdump returned by hashdeep to base64 output. Still, it would be nice if hashdeep did that on its own.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.
@simsong cat hash_from_hashdeep | xxd -r -p | base64
Results seem to be consistent with those obtained from openssl
That's pretty twisted. Congratulations on getting that to work. Would it be easier to write a small converter in python?
In any event, if you want to submit a patch, I'm happy to look at it.
Sent from my phone.
On Apr 15, 2017, at 7:52 AM, The Half Blood Prince [email protected] wrote:
@simsong cat hash_from_hashdeep | xxd -r -p | base64
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
