>1. I provided them with a small display saying >" Checked for viruses but No warranty"
In general, requirements are probably going to have to be defined with the purpose of meeting the library's security policy; anti-virus is only a small part of the total plan. That may include restricted local system access, access to only a limited number of programs and/or options, required proxy software/settings for content filtering, etc., etc.. These are just a few examples that might be pertinent in a public library. Now, part of the glory of Linux/OSS is that it is likely possible to meet those requirements without necessarily investing in a huge legacy infrastructure first. The same custom-built bootable Knoppix CD (for discussion's sake only) could be pared down and secured to meet standards while maintaining interoperability and providing a stable platform. But it would depend on exactly what specs needed to be met to know for sure. What goes through my mind as a security-aware Linux user is this: not only does a fat distro provide great applications to the average user, but also provides tremendously powerful utilities that could be used for evil instead of good. Anyone with a little Linux knowledge and a bad attitude could be a potential threat to the services and reputation of the library. I'm not saying that this makes it a bad idea; only that there may be more considerations that come into play when viewed from the corporate perspective of the library. If it is feasible to meet library requirements, whatever they may be (security and otherwise) without necessitating a large, co-ordinated long-term project, I would be willing to volunteer some of my time to ensuring that whatever distro is chosen does align with security policy. I would also open the invitation to others who might have an interest and/or knowledge in security-related aspects to contribute or audit any changes/recommendations. I certainly don't know it all, and many eyes make fewer oversights. Late night 2 cents on one aspect of it all. :-P Curtis -----Original Message----- From: Graham Monk [mailto:[EMAIL PROTECTED] Sent: October 2, 2003 9:22 PM To: [EMAIL PROTECTED] Subject: Re: (clug-talk) Linux etc in the Library On Thursday 02 October 2003 20:11, you wrote: > On October 2, 2003 07:02 pm, Bogi wrote: > > Hi. > > The simple problem here, they will think, it is proprietary and clug > > donated it. You tell them it is not, and let them take it. Then they > > know, and that is , i think is important ... > > Cheers > > Szemir > > > > On Wednesday 01 October 2003 13:45, you wrote: > > > This is one of those "why didn't I think of that" things > > > http://newsvac.newsforge.com/newsvac/03/10/01/1850221.shtml?tid=11 > > > Has anybody tried this locally? I'm going to make up some OOo and > > > SuSE discs for my local and try it. I will mark the discs " Donated by > > > CLUGG" unless anyone has a problem? > > If it helps, e.g. by lending an air of credibility etc, I can print some > CDs directly with an inkjet printer. The ink-jet-printable blanks do cost > more than ordinary ones, and I don't want to do a whole load because it's > labour-intensive, but 50 or so is doable. I'd need a print-ready graphic. Some good ideas guys. we were talking about this last night and I think it was Marcel? said that the Library was cautious about burned CDs generally. I have thinking about this and I wonder if they would go for it if 1. I provided them with a small display saying " Checked for viruses but No warranty" 2. Locked the disc so that it cant be added to ( Is this Possible? ) or filled up all the unused space with filler. Anyway when I get a minute I'll go in and talk to them. Graham
