pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2003-07-31	Convert the rc.d script to the rc.subr framework and use RCD_SCRIPTS from	jmmv	2	-101/+18
	bsd.pkg.install.mk to handle its generation and installation. While here, switch to buildlink2. Bump PKGREVISION to 1.
2003-07-21	COMMENT should start with a capital letter.	martti	1	-2/+2

2003-07-17	s/netbsd.org/NetBSD.org/	grant	1	-2/+2

2003-06-02	Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.	jschauma	1	-2/+2
	Should anybody feel like they could be the maintainer for any of thewe packages, please adjust.
2002-12-23	Whitespace fix	cjep	1	-2/+2

2002-09-24	Complete standardization of messages according to latest pkglint.	wiz	1	-3/+3

2002-07-15	Add a pointer to Steve Bellovin's mail in	agc	1	-0/+42
	http://mail-index.netbsd.org/current-users/2002/07/15/0006.html about NFS blocksizes when using mount(8) and cfs
2001-11-01	Move pkg/ files into package's toplevel directory	zuntum	2	-1/+1

2001-07-24	Re-add accidentally removed do-build target. -current doesn't need it, but	jlam	1	-1/+5
	1.5.x does.
2001-06-09	Remove trailing whitespace.	wiz	1	-14/+14

2001-06-09	Add patches from Simon Burge <simonb@wasabisystems.com> to build cfs	jlam	6	-18/+94
	without needing -traditional. This fixes socklen_t lossage mentioned in the README.netbsd file. This was tested on i386 NetBSD-1.5 and -current.
2001-06-07	Add patches missing from commit that did the following modifications:	jlam	3	-0/+46
	* Use NetBSD's getpass() function instead of the homegrown one, as the homegrown one doesn't seem to hide the password when it is being entered. * Add a rc.d style script to start cfsd, and also install the documentation for the filesystem. * Rename c* commands to cfs_* to avoid conflicts with coda programs with a similar name.
2001-06-07	* Use NetBSD's getpass() function instead of the homegrown one, as the	jlam	5	-78/+216
	homegrown one doesn't seem to hide the password when it is being entered. * Add a rc.d style script to start cfsd, and also install the documentation for the filesystem. * Rename c* commands to cfs_* to avoid conflicts with coda programs with a similar name.
2001-06-06	Back out the socklen_t Makefile magic - causes core dumps on 1.5 i386	simonb	1	-2/+1
	and alpha. Discussed with agc.
2001-06-06	Remove files from jlam's cfs package import (on top of agc's) until	wiz	3	-136/+0
	jlam has time to merge them, on request by jlam.
2001-06-05	cfs - Cryptographic File System	jlam	5	-27/+170
	CFS pushes encryption services into the UNX file system. It supports secure storage at the system level through a standard UNX file system interface to encrypted files. Users associate a cryptographic key with the directories they wish to protect. Files in these directories (as well as their pathname components) are transparently encrypted and decrypted with the specified key without further user intervention; cleartext is never stored on a disk or sent to a remote file server. CFS employs a novel combination of DES stream and codebook cipher modes to provide high security with good performance on a modern workstation. CFS can use any available file system for its underlying storage without modification, including remote file servers such as NFS. System management functions, such as file backup, work in a normal manner and without knowledge of the key.
2001-06-05	Define RINCLUDES, since otherwise cc -I will eat the next argument,	agc	2	-4/+4
	which is not TRT.
2001-06-05	Install a workaround for socklen_t definition woes on 1.5	agc	1	-2/+4

2001-06-05	Initial import of Steve Bellovin's port of Matt Blaze's CFS into the	agc	5	-0/+148
	packages collection. CFS is an encrypting file system for Unix-like OSs. It uses NFS as its interface, and so is reasonably portable. The FS code dates back to 1989, and the crypto to 1992, so it is showing signs of age. This code should be regarded as completely unsupported; a complete rewrite will follow eventually. Please don't download this code if you're in a place that's forbidden (under US or local law) to export cryptographic software from the US to, or if you're on the State Department's "Denied Persons List." If you aren't sure, ask a good lawyer.