.\" The first line of this file must contain the '"[e][r][t][v] line .\" to tell man to run the appropriate filter "t" for table. .\" .\" $Id$ .\" .\"###################################################################### .\"# # .\"# Copyright (C) 2004 # .\"# Internet2 # .\"# All Rights Reserved # .\"# # .\"###################################################################### .\" .\" File: bwctld.keys.man .\" .\" Author: Jeff Boote .\" Internet2 .\" .\" Date: Fri Feb 13 11:53:48 MST 2004 .\" .\" Description: .\" .TH bwctld.keys 5 "$Date$" .SH NAME bwctld.keys \- \fBB\fRand\fBw\fRidth \fBC\fRon\fBt\fRro\fBl\fR \fBD\fRaemon AES keyfile database .SH DESCRIPTION The \fBbwctld.keys\fR file is used to hold the identity/AES keys pairs needed for \fBbwctld\fR to authenticate users. The format of this file is described in the aespasswd(1) manual page. The location of this file is controlled by the \fB\-c\fR option to \fBbwctld\fR but it must be named \fBbwctld.keys\fR. .PP \fBbwctld\fR uses symmetric AES keys for authentication. Therefore, the \fBbwctl\fR client will have to have access to the exact same AES key for authentication by AES to work. Most likely, the user will simply know the passphrase that generated the AES key in the first place. Additionally, it is important that the system administrator and end user ensure the key is not compromised. .PP If the \fBbwctl\fR client is able to authenticate using the identity and AES key presented, \fBbwctld\fR will use the directives found in the \fBbwctld.limits\fR file to map policy restrictions to this connection. .SH SECURITY CONSIDERATIONS The keys in the \fBbwctld.keys\fR file are not encrypted in any way. The security of these keys is completely dependent upon the security of the system and the discretion of the system administrator. .SH RESTRICTIONS \fBIdentity\fR names are restricted to 16 characters. .SH SEE ALSO aespasswd(1), bwctl(1), bwctld(8), bwctld.limits(5), and the \%http://software/bwctl/ web site. .SH ACKNOWLEDGMENTS This material is based in part on work supported by the National Science Foundation (NSF) under Grant No. ANI-0314723. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the NSF.