Date: Sat, 9 Jan 1999 01:39:10 -0700 (MST)
From: mea culpa <jericho@dimensional.com>
To: InfoSec News <isn@repsec.com>
Subject: [ISN] ANNOUNCE: OpenSSL (Take 2)



Forwarded From: Ben Laurie <ben@algroup.co.uk>

    ___                  ____ ____  _     
   / _ \ _ __  ___ _ __ / ___/ ___|| |     OpenSSL
  | | | | '_ \/ _ \ '_ \\___ \___ \| |     The Open Source toolkit for SSL/TLS
  | |_| | |_) | __/ | | |___) |__) | |___  http://www.openssl.org/
   \___/| .__/\___|_| |_|____/____/|_____|
  _____ |_| __________________________________________________________________ 

  The OpenSSL Project is a collaborative effort to develop a robust,
  commercial-grade, fully featured, and Open Source toolkit implementing the
  Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1)
  protocols with full-strength cryptography world-wide. The project is managed
  by a worldwide community of volunteers that use the Internet to communicate,
  plan, and develop the OpenSSL tookit and its related documentation.

  OpenSSL is based on the excellent SSLeay library developed by Eric A. Young
  and Tim J. Hudson. The OpenSSL toolkit is licensed under an Apache-style
  licence, which basically means that you are free to get and use it for
  commercial and non-commercial purposes subject to some simple license
  conditions.

o Due to some unfortunate coincidences and misunderstandings Ben and Stephen
  launched an effort to maintain and improve SSLeay shortly before the OpenSSL
  effort was announced. These were seen as competing efforts - this was never
  really true, so the two efforts have been merged together in the interests
  of the user community.

o The core participants in the joint effort are currently (in alphabetical
  order):

  Ben Laurie
  Mark Cox
  Paul Sutton
  Ralf Engelschall
  Stephen Henson

  This group jointly control the direction of the OpenSSL project in a way
  similar to the way the Apache Group works. Others may be invited to join in
  the future on the basis of merit.

o Contributions are welcome, and will be appropriately credited. The source is
  in a CVS repository which can be mirrored through
  rsync://dev.openssl.org/openssl-cvs/ or browsed interactively through a Web
  interface under http://www.openssl.org/source/cvs/. Contributors are
  encouraged to generate patches based on the latest available version.

o The original announcement left some doubt as to the role of C2Net in the
  OpenSSL project. They donated the code which we used as a basis. This code
  was developed by Eric Young and Tim Hudson when they worked for C2Net. They
  do not manage the OpenSSL project, and are only involved to the extent that
  some of their staff (Mark and Paul) are participants.

o The OpenSSL project's code will be published under an Open Source license.
  This license will apply only to the modifications made by the OpenSSL team
  and contributors. Eric's original license will apply to the underlying SSLeay
  code base. The CVS tree will be available to anyone who wants it, and we will
  be endeavouring to release much more frequently than SSLeay was.

o There are a number of mailing lists (openssl-XXX@openssl.org) available:

  openssl-announce       Announcements
  openssl-cvs            CVS Commit Messages
  openssl-dev            Developer Forum
  openssl-users          User Support Forum

  Subscribe to these by sending mail to majordomo@openssl.org with:

  subscribe <list name> <your email address>

  as the body.

o We hope to make the next release of OpenSSL available in the next few weeks.
  In the meantime, please do pick up a snapshot and report any bugs you find.

o If you have fixes or improvements, send them to us!

  Yours,

  The OpenSSL Project Team...               Mark J. Cox           
                                            Ralf S. Engelschall   
                                            Dr. Stephen Henson
                                            Ben Laurie
                                            Paul C. Sutton  


-o-
Subscribe: mail majordomo@repsec.com with "subscribe isn".
Today's ISN Sponsor: Internet Security Institute [www.isi-sec.com]