Branch: refs/heads/release-2.4

  Home:   https://github.com/seccomp/libseccomp

  Commit: 40758a140793733e8fdd416bff65a14f8c5d5836

      
https://github.com/seccomp/libseccomp/commit/40758a140793733e8fdd416bff65a14f8c5d5836

  Author: Tom Hromatka <[email protected]>

  Date:   2019-04-16 (Tue, 16 Apr 2019)



  Changed paths:

    M src/gen_bpf.c



  Log Message:

  -----------

  bpf: add accumulator state to the instruction block hash



This addresses a problem where dissimilar instruction blocks were

improperly hashed to the same value because we were not taking into

account the accumulator state.



See the GitHub issue below for more information:

 * https://github.com/seccomp/libseccomp/issues/148



Reported-by: Toralf Förster <[email protected]>

Signed-off-by: Paul Moore <[email protected]>

Signed-off-by: Tom Hromatka <[email protected]>





  Commit: fef951a3e7f026bfcfc43191d2ed2074497b89dc

      
https://github.com/seccomp/libseccomp/commit/fef951a3e7f026bfcfc43191d2ed2074497b89dc

  Author: Tom Hromatka <[email protected]>

  Date:   2019-04-16 (Tue, 16 Apr 2019)



  Changed paths:

    M tests/.gitignore

    A tests/50-sim-hash_collision.c

    A tests/50-sim-hash_collision.py

    A tests/50-sim-hash_collision.tests

    M tests/Makefile.am



  Log Message:

  -----------

  tests: Add 50-sim-hash_collision test



libseccomp utilizes a hash table to manage BPF blocks.  It

currently employs MurmurHash3 where the key is the hashed values

of the BPF instruction blocks, the accumulator start, and the

accumulator end.  This test was added because of a mishandled

hash collision reported by Tor in GitHub issue #148.

* https://github.com/seccomp/libseccomp/issues/148



Signed-off-by: Tom Hromatka <[email protected]>

Signed-off-by: Paul Moore <[email protected]>





Compare: 
https://github.com/seccomp/libseccomp/compare/4d6401174137...fef951a3e7f0

-- 
You received this message because you are subscribed to the Google Groups 
"libseccomp" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to