Laurence Parry wrote...
> Perhaps, though the SWF format does not make it easy . . .
Thanks a lot for your input, and sorry for the long delay. I'll try to
find a solution that covers at least the vast majority of the files that
are around there. Frankly speaking, file(1) cannot be perfect and
Should this be submitted upstream via https://bugs.gw.com? I have not done
so myself because the FAQ suggests that the maintainer should, if necessary.
I appreciate that it'd be nice to have a Debian-developed resolution, as
this issue was triggered by a fix for another Debian issue. However,
Perhaps, though the SWF format does not make it easy . . .
== FWS ==
https://www.adobe.com/content/dam/Adobe/en/devnet/swf/pdf/swf-file-format-spec.pdf
(See Appendix A for another walkthrough)
All integer values are little-endian byte order, but big-endian bit order
within bytes. Signed
Laurence Parry wrote...
> It was assumed that the version number would remain below 32 "for the time
> being". This time has passed. Version 32 was published in May 2016, and it
> is already up to 34:
> http://www.adobe.com/devnet/articles/flashplayer-air-feature-list.html
> We detected this
Package: file
Version: 1:5.22+15-2+deb8u2
Tags: upstream
Flash files compiled with -swf-version=32 or above are being recognized as
'application/octet-stream' (data) rather than
'application/x-shockwave-flash' due to a restriction in the magic
definition file.
Command:
file -b --mime-type
5 matches
Mail list logo
