head	1.6;
access;
symbols
	RELEASE_7_4_0:1.5
	RELEASE_8_2_0:1.5
	RELEASE_6_EOL:1.5
	RELEASE_8_1_0:1.5
	RELEASE_7_3_0:1.5
	RELEASE_8_0_0:1.4
	RELEASE_7_2_0:1.4
	RELEASE_7_1_0:1.4
	RELEASE_6_4_0:1.4
	RELEASE_5_EOL:1.4
	RELEASE_7_0_0:1.4
	RELEASE_6_3_0:1.4
	PRE_XORG_7:1.4
	RELEASE_4_EOL:1.4
	RELEASE_6_2_0:1.4
	RELEASE_6_1_0:1.4
	RELEASE_5_5_0:1.4
	RELEASE_6_0_0:1.4
	RELEASE_5_4_0:1.2
	RELEASE_4_11_0:1.2
	RELEASE_5_3_0:1.2
	RELEASE_4_10_0:1.2
	RELEASE_5_2_1:1.2
	RELEASE_5_2_0:1.2
	RELEASE_4_9_0:1.2
	RELEASE_5_1_0:1.1.1.1
	RELEASE_4_8_0:1.1.1.1
	RELEASE_5_0_0:1.1.1.1
	RELEASE_4_7_0:1.1.1.1
	RELEASE_4_6_2:1.1.1.1
	RELEASE_4_6_1:1.1.1.1
	RELEASE_4_6_0:1.1.1.1
	RELEASE_5_0_DP1:1.1.1.1
	RELEASE_4_5_0:1.1.1.1
	RELEASE_4_4_0:1.1.1.1
	RELEASE_4_3_0:1.1.1.1
	RELEASE_4_2_0:1.1.1.1
	RELEASE_4_1_1:1.1.1.1
	RELEASE_4_1_0:1.1.1.1
	RELEASE_3_5_0:1.1.1.1
	RELEASE_4_0_0:1.1.1.1
	RELEASE_3_4_0:1.1.1.1
	RELEASE_3_3_0:1.1.1.1
	RELEASE_3_2_0:1.1.1.1
	RELEASE_3_1_0:1.1.1.1
	RELEASE_2_2_8:1.1.1.1
	RELEASE_3_0_0:1.1.1.1
	RELEASE_2_2_7:1.1.1.1
	RELEASE_2_2_6:1.1.1.1
	RELEASE_2_2_5:1.1.1.1
	jdp_1_0:1.1.1.1
	JDP:1.1.1;
locks; strict;
comment	@# @;


1.6
date	2011.10.04.23.16.30;	author rene;	state dead;
branches;
next	1.5;

1.5
date	2009.12.21.02.18.21;	author dougb;	state Exp;
branches;
next	1.4;

1.4
date	2005.06.08.11.11.08;	author jylefort;	state Exp;
branches;
next	1.3;

1.3
date	2005.04.12.09.06.25;	author flz;	state Exp;
branches;
next	1.2;

1.2
date	2003.07.09.00.39.32;	author jdp;	state Exp;
branches;
next	1.1;

1.1
date	97.07.30.22.10.20;	author jdp;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	97.07.30.22.10.20;	author jdp;	state Exp;
branches;
next	;


desc
@@


1.6
log
@Remove expired port:
2011-10-04 security/cfs: Locks don't work, ports/137378, unmaintained, dead upstream, insecure
@
text
@This is CFS, Matt Blaze's Cryptographic File System.  It provides
transparent encryption and decryption of selected directory trees.
It is implemented as a user-level NFS server and thus does not
require any kernel modifications.

For an overview of how to use it, read "${PREFIX}/share/doc/cfs/notes.ms"
and the manual pages.  There is a paper describing CFS at:

    http://www.crypto.com/papers/cfs.pdf

WWW: http://www.crypto.com/software/
@


1.5
log
@For ports maintained by ports@@FreeBSD.org, remove names and/or
e-mail addresses from the pkg-descr file that could reasonably
be mistaken for maintainer contact information in order to avoid
confusion on the part of users looking for support. As a pleasant
side effect this also avoids confusion and/or frustration for people
who are no longer maintaining those ports.
@
text
@@


1.4
log
@- convert cfsd.sh to rcNG
- add a CFS bootstrap directory to the port (${PREFIX}/cfsd-bootstrap)
- mount that CFS bootstrap directory in cfsd.sh (default mountpoint is /crypt,
  configurable in /etc/rc.conf)
- explain how to quickly setup cfsd in pkg-message
- do display pkg-message
- while here, use USE_RC_SUBR

PR:		ports/18800
Submitted by:	Louis Mamakos <louie@@TransSys.COM>, myself
Approved by:	green (maintainer)
@
text
@a11 2

John Polstra <jdp@@polstra.com>
@


1.3
log
@- Merge and split existing patch-a[a-f] files.
- Fix types issues on 64-bits architectures.

PR:		ports/75878
Submitted by:	Ville-Pertti Keinonen <will@@exomi.com>
Approved by:	maintainer timeout (3 months)
@
text
@a10 3
Under FreeBSD, the mount command for the CFS tree must include
"-o port=3049,nfsv2".

@


1.2
log
@Update the link to Matt Blaze's CFS paper.
@
text
@d14 2
@


1.1
log
@Initial revision
@
text
@d9 1
a9 1
    ftp://research.att.com/dist/mab/cfs.ps
@


1.1.1.1
log
@New port of CFS, the Cryptographic File System.
@
text
@@
