Package: wnpp The current maintainer of trinity, gustavo panizzo <gfa@zumbi.com.ar>, has retired. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: trinity Binary: trinity Version: 1.9+git20241022.ba2360ed84a8-1 Maintainer: gustavo panizzo <gfa@zumbi.com.ar> Build-Depends: debhelper-compat (= 13), dpkg-dev (>= 1.16.1~), linux-libc-dev Architecture: any Standards-Version: 4.7.0 Format: 3.0 (quilt) Files: fa11633a2ab15c2c7765f776644f1996 1460 trinity_1.9+git20241022.ba2360ed84a8-1.dsc 44a63f4df81b441c93971a3403fa4bdf 203332 trinity_1.9+git20241022.ba2360ed84a8.orig.tar.xz b481a641aea2e8ac2d663df21db663fc 5316 trinity_1.9+git20241022.ba2360ed84a8-1.debian.tar.xz Vcs-Browser: https://salsa.debian.org/debian/trinity Vcs-Git: https://salsa.debian.org/debian/trinity.git Checksums-Sha256: ba2a40a3e9f95a99c7c70626cdd5b09e7d385e6ef95a031dc5d7c99c4cd5a559 1460 trinity_1.9+git20241022.ba2360ed84a8-1.dsc b03cf83b55d6b993b91883f0cba2fc625eddccb75b29eebe9d7bb2df1c58d760 203332 trinity_1.9+git20241022.ba2360ed84a8.orig.tar.xz 5d829f2990af69a91bcb9df62d22780dd268b07b71dc3cd4b7660ccebd3403a4 5316 trinity_1.9+git20241022.ba2360ed84a8-1.debian.tar.xz Homepage: https://github.com/kernelslacker/trinity Package-List: trinity deb utils optional arch=any Testsuite: autopkgtest Directory: pool/main/t/trinity Priority: optional Section: misc Package: trinity Version: 1.9+git20241022.ba2360ed84a8-1 Installed-Size: 10672 Maintainer: gustavo panizzo <gfa@zumbi.com.ar> Architecture: amd64 Depends: libc6 (>= 2.38) Description-en: 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. Description-md5: 0b66b5bef215d4a2e96be23a7eddb2e0 Homepage: https://github.com/kernelslacker/trinity Section: utils Priority: optional Filename: pool/main/t/trinity/trinity_1.9+git20241022.ba2360ed84a8-1_amd64.deb Size: 136076 MD5sum: 9838e24e02a3bf597902ea76924e05a0 SHA256: 95cc7a603d5e52bcfcb4585ea1d0e780aee3e965caf089498404cc2f68668e01
Attachment:
signature.asc
Description: PGP signature