trinity 1.8-3ubuntu1 source package in Ubuntu
Changelog
trinity (1.8-3ubuntu1) bionic; urgency=medium * Add pthread.patch to fix build on Ubuntu -- Jeremy Bicha <email address hidden> Mon, 02 Apr 2018 13:58:10 -0400
Upload details
- Uploaded by:
- Jeremy BĂcha
- Uploaded to:
- Bionic
- Original maintainer:
- Ubuntu Developers
- Architectures:
- any
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
trinity_1.8.orig.tar.xz | 209.0 KiB | 8cadc4221660b7accc4728311ce1a130ac9b9d1f3b04e35508ba0cc80d9c3f94 |
trinity_1.8-3ubuntu1.debian.tar.xz | 274.3 KiB | 4057842895176c18f7256c3b1e6d79d35fd56bcbb5d14002079e0cbe6eb42b62 |
trinity_1.8-3ubuntu1.dsc | 1.9 KiB | bbc93bbb5f381d67906f7dc1ea85a45257c78629b7a000fdfd8602d76a9a6f5f |
Available diffs
- diff from 1.7-1 (in Debian) to 1.8-3ubuntu1 (104.8 KiB)
- diff from 1.8-3 (in Debian) to 1.8-3ubuntu1 (1021 bytes)
Binary packages built by this source
- trinity: system call fuzz tester
As 'fuzz testing' suggests, trinity calls syscalls at random, with random
arguments. Where Trinity differs is that the arguments it passes are not
purely random.
.
If a syscall took, for example, a file descriptor as an argument,
one of the first things kernels does is validate that fd, if is not valid the
kernel would just reject it as -EINVAL.
.
So on startup, Trinity creates a list of file descriptors, by opening pipes,
scanning sysfs, procfs, /dev, and creates a bunch of sockets using random
network protocols. Then when a syscall needs an fd, it gets passed one of
these at random.
.
Trinity also shares those file descriptors between multiple threads, which
causes havoc sometimes.
.
Warning: This program may seriously corrupt your files, including any of those
that may be writable on mounted network file shares. It may create network
packets that may cause disruption on your local network.
Run at your own risk.
- trinity-dbgsym: debug symbols for trinity