Re: [OVC-demo-team] Latest update for BRP

From: Eron Lloyd <elloyd_at_lancaster_dot_lib_dot_pa_dot_us>
Date: Fri Mar 12 2004 - 10:50:18 CST

On Thursday 11 March 2004 11:51 pm, Fred McLain wrote:
> We do still need the missing files as well:
> > > It also appears I am short some files:
> > >
> > > [mclain@glowtoy bva]$ python wizard.py
> > > Traceback (most recent call last):
> > > File "wizard.py", line 703, in ?
> > > wizard = BRPWizard()
> > > File "wizard.py", line 251, in __init__
> > > self.authHandler = AuthenticationHandler('acl.txt') # Right now we
> > > assume acl.txt exists
> > > File "wizard.py", line 155, in __init__
> > > self.loadAccessControlList(fileName)
> > > File "wizard.py", line 159, in loadAccessControlList
> > > self.__acl = dict([acct.strip().split(';') for acct in
> > > file(fileName, 'r').readlines()])
> > > IOError: [Errno 2] No such file or directory: 'acl.txt'

I guess I assumed you knew Python... below was the explanation of what is
going on here. Back on 3/5, I included an example file (acl.txt), but will
attach it again. I wonder if I should create another wizard to produce the
setup files...

> > acl.txt is a simple text file that holds the Access Control List. This is
> > the basic authentication source for the BRP. There is no encryption or
> > anything, but I could easy plug that in if demanded. This is supposed to
> > just be a simple demo, so please don't judge my security-consciousness
> > solely on the code :-). To make it work, simply create a acl.txt file in
> > the same directory wizard.py will be run from. Populate it with a list of
> > potential BRP operators/witnesses, using the username;password<line
> > break> convention.
> >
> > The code also looks for a votestations.txt file, which list the serials
> > of each vote station, each on a separate line. Add this to ensure proper
> > operation as well.
> >
> > I don't have many integrity or error checks in place yet either; I will
> > add robustness as seen fit. If the program crashes from some reason
> > during the process (I can't imagine it would if ran normally), all is
> > lost; nothing is transaction-based, and won't be for the demo.
> > Essentially, the code is about as simple and straightforward as I could
> > make it. It's really hard *trying* not to write good, solid,
> > well-designed code when I try to make it a habit.

Cheers,

Eron

-- 
Eron Lloyd
Technology Coordinator
Lancaster County Library
elloyd@lancaster.lib.pa.us
Phone: 717-239-2116
Fax: 717-394-3083
---
[This E-mail scanned for viruses by Declude Virus]
==================================================================
= The content of this message, with the exception of any external 
= quotations under fair use, are released to the Public Domain    
==================================================================
Received on Thu Apr 1 02:40:27 2004

This archive was generated by hypermail 2.1.8 : Thu Apr 01 2004 - 02:40:36 CST