head	1.3;
access;
symbols;
locks; strict;
comment	@# @;


1.3
date	97.01.04.20.42.43;	author morgan;	state Exp;
branches;
next	1.2;

1.2
date	96.07.08.00.02.31;	author morgan;	state Exp;
branches;
next	1.1;

1.1
date	96.06.24.05.05.35;	author morgan;	state Exp;
branches;
next	;


desc
@here is the first effort at some help for configuring pam_time
@


1.3
log
@I want email on parc now
@
text
@$Id: README,v 1.2 1996/07/08 00:02:31 morgan Exp morgan $

This is a help file for the pam_time module. It explains the need for
pam_time and also the syntax of the /etc/security/time.conf file.
[a lot of the syntax is freely adapted from the porttime file of the
shadow suite.]

1. Introduction
===============

It is desirable to restrict access to a system and or specific
applications at various times of the day and on specific days or over
various terminal lines.

The pam_time module is intended to offer a configurable module that
satisfies this purpose, within the context of Linux-PAM.

2. the /etc/security/time.conf file
===================================

This file is the configuration script for defining time/port access
control to the system/applications.

Its syntax is described in the sample ./time.conf provided in this
directory.

unrecognised rules are ignored (but an error is logged to syslog(3))

--------------------
Bugs to Andrew <morgan@@parc.power.net> or the list <pam-list@@redhat.com>

########################################################################
# $Log: README,v $
#@


1.2
log
@rewritten syntax for pam_time's config file
@
text
@d1 1
a1 1
$Id: README,v 1.1 1996/06/24 05:05:35 morgan Exp morgan $
d30 1
a30 1
Bugs to Andrew <morgan@@physics.ucla.edu> or the list <pam-list@@redhat.com>
a32 1
#
a33 3
# Revision 1.1  1996/06/24 05:05:35  morgan
# Initial revision
#
@


1.1
log
@Initial revision
@
text
@d1 1
a1 1
$Id$
d24 2
a25 35
Its syntax is the following:

each separate line is a rule. Lines are terminated by either a newline
or a '#' but may be extended with \'\n'. In order to get access to the
desired service the current user/terminal/time/service must *pass*
every rule in this file. If a rule does not specify the user/service
it is deemed to have passed.

rules have the following form:

	SERVICES:TERMINALS:USERS:TIMES

SERVICES	a comma (or blank) separated list of "service-name"s of
		applications as gotten as the item PAM_SERVICE.

TERMINAL	the "terminal" devices as given in PAM_TTY or as
		returned by ttyname(STDIN_FILENO), a comma  (or blank)
		separated list

USERS		a comma (or blank) separated list of usernames

TIMES		a comma (or blank) separated list of times.. the 
		individual times being written in the following form:

			DyFROM-xTOx

		Dy can be one or more of the following: Wd Wk Al Mn Tu
		We Th Fr Sa Su (Wd=WeekenD, Wk=Week, Al=All) Note,
		if more than a single "day" prefix is supplied they
		are logically exclusively-or'd (MoMo = no day).


		'FROM' is a 24hr time on Day 'Dy'
		'xTOx' is a 24hr time following 'FROM' (might be on the
			following day)
a29 1

d34 4
a37 1
# $Log$
@
