Closed ross-spencer closed 6 years ago
Hi Ross,
tldr try a command like: roy inspect -extend hfs-dev-sig-3.xml hfs/1
Long version: when you use roy inspect
to inspect formats it uses as input the source XML files (normally the droid XML file and/or the harvested PRONOM XML files) rather than your compiled signature (.sig) file. (This is because once signatures are compiled they are kind of shredded up for inserting in the search trees & pretty difficult to reconstruct). So to inspect a custom signature you need to use the same -extend
or -extendc
flags (if a container signature) you would use to build the signature file in order to tell roy where it can find your custom source file.
E.g. like:
p.s. I'll make a change for the next release so that if roy can't find anything to inspect, rather than a blank line, it will return a more meaningful message like "I can't inspect {user input}! See roy inspect -help
"
Thanks Richard - that would work well.
On Thu, Nov 2, 2017 at 12:25 PM, Richard Lehane notifications@github.com wrote:
p.s. I'll make a change for the next release so that if roy can't find anything to inspect, rather than a blank line, it will return a more meaningful message like "I can't inspect {user input}! See roy inspect -help"
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/richardlehane/siegfried/issues/108#issuecomment-341273016, or mute the thread https://github.com/notifications/unsubscribe-auth/AByxXBoJYqLpwZEZtRYZyFklX7Sl-eAVks5syP38gaJpZM4QNy5_ .
Hi Richard,
I tried to inspect this following custom signature I added using Roy (the signature is for identifying HFS disk images):
Should that be possible at all? - Currently in Linux I just get a blank line output. (The signature works well in Siegfried).