Log message:
Update to 1.06:

v1.06
        - instead of setting undef args to '' in configure_SSL drop
          them. This makes Net::SMTP::SSL working again because it
          does not give LocalPort of '' to IO::Socket::INET any more

Log message:
Update to 1.05:
v1.05
        - make session cache working even if the IO::Socket::SSL object
          was not created with IO::Socket::SSL->new but with
          IO::Socket::SSL->start_SSL on an established socket

Log message:
Update to 1.04:

v1.04
        - added way to create SSL object with predefined session
	  cache, thus making it possible to share the cache between
	  objects even if the rest of the context is not shared
          key SSL_session_cache
          Note that the arguments of IO::Socket::SSL::SessionCache::new
          changed (but you should never have used this class directly
          because it's internal to IO::Socket::SSL)

Log message:
Update to 1.03:

v1.03
        - add CLONE_SKIP as proposed by
          Jarrod Johnson jbjohnso at us dot ibm dot com

Log message:
Update to 1.02:

v1.02
	- added some info to BUGS and to BUGS section of pod
	- added TELL and BINMODE to IO::Socket::SSL::SSL_HANDLE, even
          if they do nothing useful.
	- all tests allocate now the ports dynamically, so there should
          be no longer a conflict with open ports on the system where
          the tests run
v1.01
	- work around Bug in Net::HTTPS where it defines sub blocking
          as {}, e.g. force scalar context when calling sub blocking
          (in IO::Socket::SSL::write)
          see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383106
v1.0
	- fix depreciated and practically undocumented function
          get_peer_certificate so that LWP Net::HTTPS works again
        - set arg 'Blocking' while calling SUPER::configure only
          if it was set by the caller to work around Problem in LWP
          Net::HTTPS

Log message:
DESTDIR support.

Log message:
Update security/p5-IO-Socket-SSL from 0.998 to 0.999
- If SSL_cipher_list is not given it uses the openssl default
  instead of setting it to 'ALL:!LOW:!EXP' like before. The old
  value included ADH and this might be a bad idea, see BUGS why.
Resolves PR pkg/34392 by Martin Wilke

Log message:
Update security/p5-IO-Socket-SSL from 0.997 to 0.998.
v0.998
        - declare socket as opened before calling fatal_ssl_error
          because the SSL_error_trap set up from HTTP::Daemon
          needs this
        - accept_SSL sets errors on $socket (the accepted socket)
          not $self (the listening socket if called from accept)
          so it can be queried from SSL_error_trap
        - note in BUGS section that IO::Socket::SSL is not thread-safe

Note: The previous update from 0.97 broke all https:// URLs in p5-libwww,
will address that in next commit (to p5-libwww)

Log message:
Update to 0.997:

v0.997
        - fix readline (e.g. getline,getlines,<>) so that it behaves
          regarding $/ like written in the $/ dokumentation.
v0.996
        - removed links and comments to inofficial release of
          Net::SSLeay, because there is a newer version already
v0.995
        - add support for Diffie Hellman Key Exchange.
          See parameter SSL_dh_file and SSL_dh.
v0.994
        - hide DEBUG statements and remove test to load Debug.pm
          because packets like Spamassisin cannot cope with it
          (at least the OpenBSD port)
v0.993
        - added SSL_cert and SSL_key parameter which do not take
          a file name like SSL_cert_file and SSL_key_file but
          an internal X509* resp. EVP_PKEY* value. Useful for
          dynamically created certificates and keys.
        - added test for sysread/syswrite behavior (which was changed
          in v0.991)
v0.992
        - _set_rw_error does $!||=EAGAIN only if error is one of
          SSL_WANT_READ|SSL_WANT_WRITE (patch from Mike Smith
          <mike at mailchannels dot com>)
        - Fix Makefile.PL to allow detectection of failures in PREREQ_PM
          (http://rt.cpan.org/Public/Bug/Display.html?id=20563, patch
          by alexchorny at gmail dot com)
v0.991
        - sysread and syswrite ar no longer the same as read and write,
          but can return already if only parts of the data are read
          or written (which is the usual semantic for sysread and syswrite)
          This should fix problems with HTTP::Daemon::SSL
v0.99
        - just upgrade Version number because I've screwed up upload
	  of v0.98 to cpan
v0.98
	- Maintainer changed to <Steffen_Ullrich at genua dot de>
	- Better support for nonblocking sockets:
	  . exports $SSL_ERROR which contains the latest error from
	    the openssl library. Exports constants SSL_WANT_READ and
	    SSL_WANT_WRITE es special errors which will be set if
	    openssl wants to write or read during nonblocking connects,
	    accepts, reads or writes.
	  . accept,accept_SSL,connect and connect_SSL don't block
	    anymore if the socket is nonblocking.
	    Instead $! will be set from the underlying IO::Socket::INET
	    connect or accept if it failed there (usually EAGAIN or
	    EINPROGRESS) or if the underlying openssl needs to read or
	    write $! will be set to EAGAIN and $SSL_ERROR will be set
	    to SSL_WANT_READ or SSL_WANT_WRITE
	  . syswrite returns undef and sets $!,$SSL_ERROR if it fails
	    to write instead of returning 0.
	- Bugfixes (http://rt.cpan.org/Public/Bug/Display.html?id=Bugid)
	  . Bug 18439: fileno 0 should be valid
	  . Bug 15001: sysread interpretes buffer "0" as ""
	- peer_certifcate returns X509 struct string if no field
	  for extraction was specified
	- get_peer_certificate returns the certificate instead of the
	  IO::Socket::SSL object

Log message:
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to \ 
"pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.