{"push_id":1968203534,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"6e19806ddd7bc9316aea72b50c08598cd7cc5ad6","before":"736453b1a32a2a1ba351bace33e6a4b1c409f2e1","commits":[{"sha":"539080f96d10404f95836013bab0f87812c9b2dc","author":{"name":"Michael Chisholm","email":"5757b07cd62e3190f1b015dbac2385fcf75cbcfe@mitre.org"},"message":"Initial support for regex matching on binary data.  It's something\nI overlooked in the spec, and hadn't implemented.","distinct":true,"url":"https://api.github.com/repos/oasis-open/cti-pattern-matcher/commits/539080f96d10404f95836013bab0f87812c9b2dc"},{"sha":"00a6be50c7fa0bcea4ff5136d3baa5d67058f6d7","author":{"name":"Michael Chisholm","email":"5757b07cd62e3190f1b015dbac2385fcf75cbcfe@mitre.org"},"message":"Changed how the 'NOT' qualifier works when in front of the\n'MATCHES' operator.  I had misunderstood how it worked:\nbefore, both 'MATCHES' and 'NOT MATCHES' evaled to false on\nincompatible values.  This is changed so that 'MATCHES' evals\nto false, and 'NOT MATCHES' evals to true.\n\nThe above change necessited changes to some unit tests in\ntest_basic_ops.py.\n\nUpdated the test data in test_binary.py to hopefully avoid future\nconfusion: all the property string values are now unicode strings\nso that the pattern matcher treats them as such under python2.\nSome folks expected plain 'str' values to be treated as strings\nunder python2, but that's not the case.\n\nAlso added a few more tests to test_binary.py.","distinct":true,"url":"https://api.github.com/repos/oasis-open/cti-pattern-matcher/commits/00a6be50c7fa0bcea4ff5136d3baa5d67058f6d7"},{"sha":"6e19806ddd7bc9316aea72b50c08598cd7cc5ad6","author":{"name":"Greg Back","email":"8ec6f84c66460f246b6d8c77fbb45302ef9faef7@users.noreply.github.com"},"message":"Merge pull request #44 from chisholm/bin_regex\n\nAdd support for 'MATCHES' on binary data","distinct":true,"url":"https://api.github.com/repos/oasis-open/cti-pattern-matcher/commits/6e19806ddd7bc9316aea72b50c08598cd7cc5ad6"}]}
{"actor":{"display_login":"gtback"}}