Your Own Privacy)
last updated on 20060104
[ links to the downloadables
are at the bottom of this page.]
BYOP (Build Your Own
is a toolkit. Judicious use of it can improve the efficiency of
e-mail activity, by improving bandwidth utilisation. It can also
enhance the security of all your point-to-point communication, against
attack by terrorists, crackers, and other unlawful and/or unscrupulous
is a collection of
and simple component modules. Each pair-of-users can easily
these components into a unique concoction, so that even the creatrix of
BYOP can't crack their mails.
is suitable for
by persons who are familiar with basic computer operation from the
and who value efficiency and privacy sufficiently to invest some
time, and labour in their pursuit of it.
is not a
system; it contains its own privacy devices.
The entire BYOP sourcecode is
And it is small. So, it may also prove useful to persons desiring
familiarity with assembly language programming, using the NASM
is not intended to
excessively `user-friendly', and we do not `package' it for any GUI. In
fact, we do not really package it at all; each pair-of-users should
the important task of combining the modules using scripts. This
them a wide choice as to the manner of doing it. (See the sample
in this distro.) This policy is built on the premise that a
is inherent in trusting any pre-built package, or any privacy system
with a huge OS. Excessive standardisation and automation of
protection will allow the snoops to employ automated schemes of
BYOP, with its highly individualisable scripts, will at least
the work of the snoops by de-automating and `humanising' it.
is licensed to you
the GNU General Public Licence, GPL.
The component modules
BYOP are briefly described below. Each module forms a
in your BYOP installation. More detailed description will be
within each module after installation on your machine.
1. taaschg is
a small utility for breaking a large file into a number of pieces, and
for re-combining the pieces to recover the file.
is a utility for improving bandwidth utilisation whenever you attach a
pcm-coded sound file with your e-mail. This is achieved by
multiplexing(LSB) a message, or any other small file (e.g., a list of
sound cuts in the sound file), with the .wav file
So now, the user sends only one file (a .wav file), instead of two
(the .wav file PLUS the message file). Not all .wav
formats are suitable; aavaazg can currently use simple, uncompressed,
bit, mono/stereo files. (The <data> chunk must follow
after the <fmt> chunk.)
is similar to aavaazg, except that it is designed for e-mail
in the form of simple, uncompressed,
(8 or 24 bit) .bmp files.
is a programme-generating module. It will quickly create a
pair of small coding-and-decoding
programmes. A large
number of such matched pairs are possible. Each pair-of-users can
easily choose which of those possible pairs they want to create and use.
is a directory containing files needed by the other modules. The
Network Assembler, NASM v0.98, is included in this module. NASM
be needed for generating executables from assembly language source
is a directory containing sample bash-scripts. These simple
demonstrate the kind of variability and versatility available to each
through combinations of the four modules taaschg, aavaazg, tussvirg,
are only for informational purposes and for testing. They should
not be overused, in their present form, for real communication
Rather, each pair-of-users should study these scripts, and then create
their own unique scripts for their own use.
no one has written before.
above form the `secret key' for communication among each particular
They will need a means of securely exchanging their new scripts.
We have now developed a separate, self-contained, keyless protocol for
this purpose. This protocol, called `keylilla', is also
It is available, as an item for download, at
future depends on
you value." -- Richard Stallman
Download : download
version 0.3g for gnu / linux
--- Chanda Hedvikar-Hedvikar
and the 84's
download version 0.3d for dos
two versions are
to bindhast : home