This new version is a bugfix version for Python 3 plus I added a new name in the default report: /XFA
pdfid_v0_1_2.zip (https)
MD5: 60FC17757201F014A6ADA0744B74A740
SHA256: 1CF36C50427A2206275C322A8C098CD96A844CAF6077B105ADE9B1974789856F
Thursday 21 March 2013
Update: PDFiD Version 0.1.2
7 Comments »
RSS feed for comments on this post. TrackBack URI
Didier Stevens 
You should change from optparse to docopt.
Comment by henrisalo — Thursday 21 March 2013 @ 10:51
@henrisalo This would make PDFiD (and pdf-parser) dependent on an external module. I want my pdf tools to run on default Python installations, without any additions.
Comment by Didier Stevens — Thursday 21 March 2013 @ 11:00
Excellent point.
Comment by henrisalo — Thursday 21 March 2013 @ 11:01
Nice tools! Do you plan to add them to git, mercurial or svn repo? As you have many updates and I plan to add them to the Matriux distro, it will be simpler for every one who needs/wants up to date versions 🙂
Comment by Tiger-222 — Thursday 21 March 2013 @ 13:58
@Tiger-222 Yes, I plan to setup my own git repo.
Comment by Didier Stevens — Thursday 21 March 2013 @ 22:39
Thank you for making great tools.
I found one problem during the test.
(source info : ver 0.2.1 2014/10/28)
If the file name to be scanned contains the string “[“, “]”, it is not checked.
For example
C: \ python pdfid.py “c:[test]abcd.pdf”
“[Test] abcd.pdf” file is not scanned.
The return value of the “ExpandFilenameArguments” function is blank.
(848 line of pdfid.py source code)
I hope it gets fixed.
Comment by dreamer998 — Friday 14 April 2017 @ 1:01
This is normal behavior. pdfid supports filename wildcards. If you are not familiar with filename wildcards, read this: http://www.linfo.org/wildcard.html
Comment by Didier Stevens — Sunday 16 April 2017 @ 13:05