Bug#909083: RFP: dsocks -- SOCKS client wrapper for *BSD / MacOS X
Package: wnpp Severity: wishlist * Package name: dsocks Version : 1.7 Upstream Author : Dug Song * URL : https://monkey.org/~dugsong/dsocks/ * License : 2-clause BSD Programming Lang: C Description : SOCKS client wrapper for *BSD / MacOS X It can be used as a Proxy nameserver to relay name lookups to Tor to prevent DNS leaks as described on https://trac.torproject.org/projects/tor/wiki/doc/PreventingDnsLeaksInTor Source also available in git: https://github.com/dugsong/dsocks
Bug#909072: Dependencies
petardfs 0.0.2 by Ben Martin (http://freshmeat.net/users/monkeyiq/) Mon, Mar 19th 2007 10:26 About: petardfs is a FUSE filesystem designed to hoist your applications with errors. With no configuration, petardfs takes a base filesystem and exposes it through FUSE. An XML configuration file is used to tell petardfs which files to report errors for and what error code to use. For example, foo.txt can have an EIO error at bytes 34 to 37. There is explicit support for errors such as EAGAIN and EINTR, where petardfs will only report such transient errors a nominated number of times. This is handy for testing applications that support such I/O conditions gracefully. Changes: Petardfs is now a subclass of fuselagefs. Much filesystem delegating code has now been moved to libfuselagefs. License: GNU General Public License (GPL) URL: http://freshmeat.net/projects/petardfs/ Dependencies - libxerces (0.2.8 or newer) - libfuselage fuselagefs consists of a C++ wrapper class for FUSE called Fuselagefs, as well as Delegatefs, which is a Fuselagefs subclass that delegates all operations to an underlying base filesystem. With Delegatefs, you can expose dir1 at mountpoint dir2 very easily as a FUSE filesystem. Subclasses of Delegatefs can then be created, which add a little extra functionality to the delegation operation but rely on the parent class to perform the work and return errors to FUSE in an appropriate manner. An example subclass is petardfs. License: GPL URL: http://freshmeat.sourceforge.net/projects/fuselagefs/ - libfuselage depends on libpopt, which has a debian package: libpopt-dev/testing 1.16-11 i386 lib for parsing cmdline parameters - development files - libattr1-dev: /usr/include/attr/xattr.h
Bug#909072: RFP: petardfs -- a FUSE filessytem for injecting intentional errors (e.g. for testing)
Package: wnpp Severity: wishlist * Package name: petardfs Version : 0.1 Upstream Author : Ben Martin * URL : https://github.com/jrandall/petardfs * License : GPL 3 Programming Lang: C++ Description : a FUSE filessytem for injecting intentional errors (e.g. for testing) PetardFS - a FUSE filessytem for injecting intentional errors (e.g. for testing) With no configuration petardfs takes a base filesystem and exposes it through FUSE. An XML configuration file is used to tell petardfs which files to report errors for and what error code to use. For example, foo.txt can have an EIO error at bytes 34 to 37. There is explicit support for errors such as EAGAIN and EINTR where petardfs will only report such transient errors a nominated number of times, handy for testing applications support such IO conditions gracefully. original source: http://sourceforge.net/projects/witme/files/petardfs/0.0.2/
Bug#909069: RFP: charybdefs -- fuse based fault injection filesystem with a Thrift RPC interface for instrumentation
Package: wnpp Severity: wishlist * Package name: CharybdeFS Version : 0.1 Upstream Author : ScyllaDB * URL : https://github.com/scylladb/charybdefs * License : Epat Programming Lang: C++ Description : ScyllaDB fault injection filesystem CharybdeFS is a fuse based fault injection filesystem with a Thrift RPC interface for instrumentation. Block devices sometimes do bad things (or just fill up), so sometimes bad things happen to good software. CharybdeFS makes it easy to do integration testing that covers hard-to test filesystem errors. And good error handling is a sign of well-thought-out software. For example, your program will make a much better impression on users if you have it show a nice “insufficient space” message than if it just crashes for no apparent reason. The CharybdeFS filesystem lets you inject arbitrary file errors for testing. This article covers some common examples for getting started. https://www.scylladb.com/2016/05/02/fault-injection-filesystem-cookbook/
