search

richardlehane / siegfried

signature-based file format identification
http://www.itforarchivists.com/siegfried
Apache License 2.0
224 stars 30 forks source link

Can't detect plan9 platform executable program files. #132

Closed nifflin closed 5 years ago

nifflin commented 5 years ago

env GOOS=plan9 arch=386 go build helloworld.go

sf can't detect anything from this plan9 executable program file.

Great job. thank you!

richardlehane commented 5 years ago

thanks for reporting this, Scrooge.

sf implements file format signatures defined elsewhere: e.g. the PRONOM database or freedesktop.org. In order to get sf to recognise a plan9 executable, you'd need to get one of those projects to publish a signature for it. PRONOM have a web form for proposing new signatures. freedesktop.org have a Bugzilla tracker.

A good place to start if proposing a new file format signature would be the magic bytes at the start of a plan9 executable which are described here: http://man.cat-v.org/plan_9/6/a.out

Another option is to use the roy tool to build your own signature file with a custom extension. This would allow you to define your own signature without going upstream to those projects. The command you need for this is roy build -extend mysig.xml. More info on that here: https://github.com/richardlehane/siegfried/wiki/Building-a-signature-file-with-ROY#customisable

nifflin commented 5 years ago

I have reported to PRONOM database

richardlehane commented 5 years ago

closing, as this now with PRONOM