Date: Sun, 9 Jul 2000 05:56:46 -0400 (EDT) From: Trevor Johnson <trevor@jpj.net> To: gnats-admin@FreeBSD.org, freebsd-ports@FreeBSD.org Cc: xercist <xercist@lammah.com> Subject: Re: ports/19778: new port: security/pad Message-ID: <Pine.BSI.4.21.0007090541340.4521-100000@blues.jpj.net> In-Reply-To: <200007080440.VAA97068@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
The author has prepared a new release. Here's an update to the proposed port. Highlights: - remove patches/patch-pad_c, because the author incorporated it - don't munge the README as much, because the author has reformatted it - check OSVERSION and depend on OpenSSL port for old systems that don't have it in the base system # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # pad # pad/files # pad/files/md5 # pad/patches # pad/patches/patch-README # pad/pkg # pad/pkg/COMMENT # pad/pkg/DESCR # pad/pkg/PLIST # pad/Makefile # echo c - pad mkdir -p pad > /dev/null 2>&1 echo c - pad/files mkdir -p pad/files > /dev/null 2>&1 echo x - pad/files/md5 sed 's/^X//' >pad/files/md5 << 'END-of-pad/files/md5' XMD5 (pad-0.6.tgz) = 77b8635f795196bff58c8d02a242d431 END-of-pad/files/md5 echo c - pad/patches mkdir -p pad/patches > /dev/null 2>&1 echo x - pad/patches/patch-README sed 's/^X//' >pad/patches/patch-README << 'END-of-pad/patches/patch-README' X--- README.orig Sat Jul 8 21:43:28 2000 X+++ README Sun Jul 9 04:56:10 2000 X@@ -1,24 +1,27 @@ X-PAD is a small command-line utility to seperate one file into two- each X-indistinguishable from white noise, and put them back together into X-the original. X+PAD is a small command-line utility to separate one file into two, each X+indistinguishable from white noise, and put them back together into the X+original. X X Usage: pad <input 1> [<input 2> [output]] X X Where input1 is the name of the file to be broken up, pad will name X-write <filename>.pad1 and <filename>.pad2. X+the output files <filename>.pad1 and <filename>.pad2. X X If <input2> is given, pad will combine the two into one file, and store X the result in <output>. If <output> is omitted, the file will be written X to stdout. X X X-Example: X+Examples: X X-pad myfile.txt # you now have myfile.txt.pad1 and myfile.txt.pad2. X-pad myfile.txt.pad1 myfile.txt.pad2 outputfile # you now have outputfile, X-which is identical to the original myfile.txt, built from your two X-pad files. X+ pad myfile.txt X+ X+You now have myfile.txt.pad1 and myfile.txt.pad2. X X+ pad myfile.txt.pad1 myfile.txt.pad2 outputfile X+ X+You now have outputfile, which is identical to the original myfile.txt, built X+from your two pad files. X X The interesting thing about the .padx files are that they both look like X random data (in fact, one actually is random data generated by OpenSSL), X@@ -33,7 +36,7 @@ X unrelated systems, and tell people where to get each (and how X to re-assemble them). Should someone go to one (or both) of the X hosting systems and pressure them to remove it, each can claim X- they're only hosting harmless, random data. It is methematically X+ they're only hosting harmless, random data. It is mathematically X impossible to prove that either one is the random one and the X other was derived from the original file. X X@@ -44,8 +47,8 @@ X want to share data with, and simply transmit messages that have X been merged with this pad, via any medium. OTP encryption is as X secure as your random source (in this case, from OpenSSL), and X- the pad itself. Keep in mind it's called <b>One</b>-time pad for X- a reason -- If you use the same pad on two different plaintexts, X+ the pad itself. Keep in mind it's called a "one-time pad" for a X+ reason: if you use the same pad on two different plaintexts, X the messages (either one) can no longer be considered secure. X X END-of-pad/patches/patch-README echo c - pad/pkg mkdir -p pad/pkg > /dev/null 2>&1 echo x - pad/pkg/COMMENT sed 's/^X//' >pad/pkg/COMMENT << 'END-of-pad/pkg/COMMENT' XEncrypt files END-of-pad/pkg/COMMENT echo x - pad/pkg/DESCR sed 's/^X//' >pad/pkg/DESCR << 'END-of-pad/pkg/DESCR' Xfrom the README: X XThis is a small command-line utility to turn one file into two, each Xindistinguishable from noise, and put them back together into Xthe original. X Xfrom the maintainer: X XNote that the resulting files are the same size as the original. X XWWW: http://www.lammah.com/pad/ X XTrevor Johnson Xtrevor@jpj.net END-of-pad/pkg/DESCR echo x - pad/pkg/PLIST sed 's/^X//' >pad/pkg/PLIST << 'END-of-pad/pkg/PLIST' Xbin/pad Xshare/doc/pad/README X@dirrm share/doc/pad END-of-pad/pkg/PLIST echo x - pad/Makefile sed 's/^X//' >pad/Makefile << 'END-of-pad/Makefile' X# New ports collection makefile for: pad X# Date created: 2000-07-08 X# Whom: Trevor Johnson X# X# $FreeBSD$ X# X XPORTNAME= pad XPORTVERSION= 0.6 XCATEGORIES= security XMASTER_SITES= http://www.lammah.com/pad/ XEXTRACT_SUFX= .tgz X XMAINTAINER= trevor@jpj.net X X.include <bsd.port.pre.mk> X.if ${OSVERSION} < 400014 XLIB_DEPENDS= crypto.1:${PORTSDIR}/security/openssl X.endif X XGNU_CONFIGURE= yes X Xpost-install: X.if !defined(NOPORTDOCS) X @${MKDIR} ${PREFIX}/share/doc/pad X @${INSTALL_DATA} ${WRKSRC}/README ${PREFIX}/share/doc/pad X.endif X X.include <bsd.port.post.mk> END-of-pad/Makefile exit -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.4.21.0007090541340.4521-100000>