A Linux System call fuzz tester
The basic idea is fairly simple. As 'fuzz testing' suggests, we call syscalls at random, with random arguments. Not an original idea, and one that has been done many times before on Linux, and on other operating systems. Where Trinity differs is that the arguments it passes are not purely random.
- Developed at devel:tools
- Sources inherited from project openSUSE:Factory
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:seife:Factory/trinity && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| _service | 0000000511 511 Bytes | |
| _servicedata | 0000000228 228 Bytes | |
| trinity-1.7+git.20170612.tar.xz | 0000204184 199 KB | |
| trinity.changes | 0000028889 28.2 KB | |
| trinity.spec | 0000001756 1.71 KB |
Revision 40 (latest revision is 77)
Dominique Leuenberger (dimstar_suse)
accepted
request 504038
from
Martin Pluskal (pluskalm)
(revision 40)
- Update to version 1.7+git.20170612: * mark the sync syscalls as expensive * reduce the likelyhood that we call expensive syscalls. - Update to version 1.7+git.20170525: * add incoming packets to the correct place in the list. * add the last op_nr to the childexited message * add a flag to mark when we're expecting a spawn message. * only process CHILD_EXITED messages if the opnr is current * maintain a count of packets processed each scan of the child list. * childhdr is already set at this point. * use a single thread to process all child packets * optimize packet rx list walk * drop duplicate packets instead of adding them to the list. * fix up cppcheck signedness warnings * replace state machine with simpler drain logic
Comments 0