-
Prevent parsing of escape characters
-
By replacing the escape character with \e, user defined escape sequences wont be rendered in the output. This prevents malicious actors from performing anti-analysis.
-
Fix CAPE link
-
Remove imp import from xxxswf for python 3.12 compatability
-
Fix unittests
-
Should help debugging unexpected results.
-
Another recent pull request changed the outcome of 2 tests for one sample. However, those results do not appear on my system or the github integrated unittest systems. Maybe detection is dependent on system encoding? Need to investigate, exclude sample for now.
-
Introduced an error when silencing pylint warnings. This should fix it.
-
rtfobj.py syntax error
-
oleobj.py syntax error
-
Run unittests automatically on github
-
In python 3.12+ this escaping is reported as syntax error. Moving the dash to the end of the regex avoids the need for escaping it. oletools/oleobj.py:537 /rpmbuild/BUILD/oletools-78b2d459a33df378a4f69ffc6c33313509cecfe4/oletools/oleobj.py:537: SyntaxWarning: invalid escape sequence '\-' sane_fname = re.sub(u'[^a-zA-Z0-9.\-_ ]', replacement, basepath)
-
In python 3.12+ it is reporting the syntax error oletools/rtfobj.py:272 /rpmbuild/BUILD/oletools-78b2d459a33df378a4f69ffc6c33313509cecfe4/oletools/rtfobj.py:272: SyntaxWarning: invalid escape sequence '\d' DECIMAL_GROUP = b'(\d{1,250})'
-
Relax pyparsing requirement.
-
# Conflicts: # tests/olevba/test_basic.py
-
This was removed by github in June 2023
-
Decrypting test samples "on the fly" using a generator causes trouble when removing the temp file, PyPy/Windows thinks the file is still being used.
-
I do not see how I could keep the code clean for both for pylint2 and pylint3 at the same time, so do not even try.