A long time ago a library package was written to help secure connections on a server. It worked very well and was used on many systems. The author (Hi Phil) of the package included it as part of a tutorial he used at a number of conferences. By the time the tutorial was available I had already deployed this library on my network and really cranked down on a number of settings.
I attended one of the tutorials just to see if I could pick up some additional pointers both in using this tool and some other security and tuning issues being presented. When it came to the Q&A portion, a number of people had questions on how to use the library to help secure their system. In a couple cases the author indicated he didn't think his library could help. This is where I pitched in and told people how they could use the library to do exactly what they wanted, plus explained how it could be used to do several things most people didn't really think about. In a couple of those cases, the free tool solved limitation problems that the vender software was unable to provide. The examples I added quickly became part of the tutorial and the example setup and configurations on using the library. Many others learned from what was provided. The OS software developers became interested in this as a solution as well. Though they implemented this in a different manner, this provided them a wake-up-call that it was needed. Bottom line.. If you author a piece of software, do not be suprised at how others may use or in some cases abuse your software to do more than you ever expected. As a user of that software, don't be afraid to tell others how you are using it. Even just the ideas can go a long way in steering the next release to doing more of what you want/need. --Gene _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
