Gabriel Vasile
Gabriel Vasile
[mimetype used `application/octet-stream` until now for these formats](https://github.com/gabriel-vasile/mimetype/blob/c6adf9ad07f1287ec8618b6b709f29cfa5acd0e8/tree.go#L190-L191). Now that `application/vnd.shp` and `application/vnd.shx` have been registered at IANA, they can be used. https://www.iana.org/assignments/media-types/application/vnd.shp https://www.iana.org/assignments/media-types/application/vnd.shx
https://www.iana.org/assignments/media-types/image/jxr https://www.iana.org/assignments/media-types/image/jxs
The algorithm is implemented here: https://github.com/file/file/blob/b56b58d499dbe58f2bed28e6b3c297fe7add992e/src/is_tar.c
https://www.rfc-editor.org/rfc/rfc7303
Given the randomness of fuzzing data, I don't think there is a way to generate and fuzz on valid files (ex: starting from a .docx file, generate other valid .docxs...
Right now they ask for unneeded info.
1) Specify the MIME type and extension for which to add support application/cbor-seq 2) Share an example file ... 3) Optionally, add a reference to the specification of the file...
1) Specify the MIME type and extension for which to add support application/cbor 2) Share an example file ... 3) Optionally, add a reference to the specification of the file...
#158 introduced granular locking at the MIME struct level. Test if the "hand over hand" locking that's happening when traversing the MIME tree is faster than getting a single global...