pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2004-08-03	Unfortunately, "mountd" REQUIREs "mountall", causing a circular dependency	tv	1	-2/+1
	here. So it's not possible to mount cfs from "mountall" -- it will have to be mounted by hand later in startup, e.g. rc.local.
2004-08-02	cfsd needs to be before "mountall" in order to be listed in /etc/fstab.	tv	1	-1/+2

2003-07-31	Convert the rc.d script to the rc.subr framework and use RCD_SCRIPTS from	jmmv	1	-95/+11
	bsd.pkg.install.mk to handle its generation and installation. While here, switch to buildlink2. Bump PKGREVISION to 1.
2001-06-09	Add patches from Simon Burge <simonb@wasabisystems.com> to build cfs	jlam	1	-0/+22
	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	* Use NetBSD's getpass() function instead of the homegrown one, as the	jlam	1	-0/+111
	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	Remove files from jlam's cfs package import (on top of agc's) until	wiz	1	-103/+0
	jlam has time to merge them, on request by jlam.
2001-06-05	cfs - Cryptographic File System	jlam	1	-0/+103
	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.