What kind of platforms are we looking to have this on? I have somewhat access to a large set of machines including the following:
Compilers: ---------- Visual C++ 6.0 Visual C++ .NET SunCC 5.2 gcc (of course.. ) Platforms: ---------- Windows NT 4.0 Windows 2000 Windows 2000 Advanced Server Windows XP Professional Sparc Solaris 7 Sparc Solaris 8 Any version of linux, because ofcourse the distro's are free. What kind of support would everyone expect from this? I would like to know what all would Be involved or better yet, what the people from this group would _expect_. Would anyone be Oposed to a small fee for these? Maybe a subscription type fee that would be very minimal in the range of $5/month , or something like that just so the machine's hosting this can be paid for and the time doing this Is paid for. As everyone knows bandwidth is not free nowadays and depending on the traffic received it can cost A pretty penny. I would like some ideas as to what could be done with this and what people would/wouldn't do for These binaries. This could become a great way to alleviate the build pain some people experience. - Andrew T. Finnell Active Solutions L.L.C [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Richard > Levitte - VMS Whacker > Sent: Wednesday, March 27, 2002 6:43 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: binaries > > > A note on this: if someone wants to produce OpenSSL binaries > in a consistent way and put them out somewhere, I'd be happy > to link to them or the directory they're in. > > Note that consistently means that there should be some kind > of note saying exactly how the binaries were produced and > what is required to install them. It also means that the > production of binaries shouldn't just be on a one-time basis, > I don't think that several links to various versions of the > otherwise same binary is very useful. Basically, I'm looking > for people to commit themselves for some time, and to handle > it nicely when they need to do something else (basically, > hand it off to someone else that can commit in the same manner). > > Another note: neither me nor the rest of the OpenSSL team will take > *any* responsability for the quality of the binaries. All > we'll do is to set up the links. If there are viruses coming > with the binaries, blame the one who produced them, not us, > or blame yourself for not having an updated virus scanner. I > know this sounds harsh, I just don't want the middle man to > be attacked. > > -- > Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED] > Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47 > \ SWEDEN \ or +46-708-26 53 44 > Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED] > Member of the OpenSSL development team: http://www.openssl.org/ > > Unsolicited commercial email is subject to an archival fee of > $400. See <http://www.stacken.kth.se/> ~levitte/mail/> for more > info. > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
