Andreas J. Koenig [[EMAIL PROTECTED]] quoth: *> *>The default is open house of course as is now. Security is a choice *>and what I describe here is just what I believe is needed to provide *>security for those who want it. I'd welcome soggestions how to make it *>easy to use. But befiore we can make it really easy we must have a *>working prototype. Well, it will be security in a very loose sense of the term but it may be a worthwhile thing. PGP or MD5? Makemaker/PAUSE/manual author addition? What is it that the user and the author will get out of signed code? Will this create useless bloat or useful hurdles? I'm not particularly sold on any particular idea other than some change for CPAN will be a good thing, particularly useful information and features that make CPAN easy to navigate and easier to trust. *>It must be an option item for both producers and consumers, otherwise *>it will do what you say. Did I not make it clear enough that I want *>security as an optional feature? The OSD should help to implement the *>framework that allows security. Currently the options we have are all *>too complicated. Please correct me if I'm wrong. There are people who write complex modules so keep tossing out ideas and possibly the most obviously simple one will be a combination of them or something else entirely. I like the method of making something cool enough and easy/simple enough as to be compelling to both sides of the equation to use it. Optional, yes, but everything in life except for food, water and shelter is optional but the constructs of life make us think we need everything else. We're on the same side so I'd like to think we could offer ideas and opinions here with an open mind. I'll keep a tally of ideas and items and when we have a good list we can sift the good from the not so good and see what works from there. e.
