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]

Reply via email to