Stephan Kulow 2014-07-25 09:50:24 +00:00 committed by Git OBS Bridge
parent db88179956
commit 3360ccea26
4 changed files with 44 additions and 20 deletions

View File

@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:050d9ad4668dec38a627938e9aa7e5dd94613f629a53ef812d10514fb206c88a
size 100385

View File

@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:acdb67b5b63aea5b7e70c3e4c70a16128810329592b63753a38c794aff76a1dd
size 186642

View File

@ -1,3 +1,8 @@
-------------------------------------------------------------------
Fri Jul 25 09:32:05 UTC 2014 - coolo@suse.com
- updated to 1.997, huge Changes
-------------------------------------------------------------------
Sat Mar 22 19:05:20 UTC 2014 - coolo@suse.com

View File

@ -17,7 +17,7 @@
Name: perl-IO-Socket-SSL
Version: 1.970
Version: 1.997
Release: 0
%define cpan_name IO-Socket-SSL
Summary: Nearly transparent SSL encapsulation for IO::Socket::INET.
@ -34,26 +34,45 @@ Requires: perl(Net::SSLeay) >= 1.46
%{perl_requires}
%description
This module provides an interface to SSL sockets, similar to other
IO::Socket modules. Because of that, it can be used to make existing
programs using IO::Socket::INET or similar modules to provide SSL
encryption without much effort. IO::Socket::SSL supports all the extra
features that one needs to write a full-featured SSL client or server
application: multiple SSL contexts, cipher selection, certificate
verification, Server Name Indication (SNI), Next Protocol Negotiation
(NPN), SSL version selection and more.
IO::Socket::SSL makes using SSL/TLS much easier by wrapping the necessary
functionality into the familiar the IO::Socket manpage interface and
providing secure defaults whenever possible. This way existing applications
can be made SSL-aware without much effort, at least if you do blocking I/O
and don't use select or poll.
If you have never used SSL before, you should read the section 'Using SSL'
before attempting to use this module.
But, under the hood SSL is a complex beast. So there are lots of methods to
make it do what you need if the default behavior is not adequate. Because
it is easy to inadvertently introduce critical security bugs or just
getting hard to debug problems, I would recommend to study the following
documentation carefully.
If you used IO::Socket before you should read the following section
'Differences to IO::Socket'.
The documentation consists of the following parts:
If you want to use SSL with non-blocking sockets and/or within an event
loop please read very carefully the sections about non-blocking I/O and
polling of SSL sockets.
* * the /"Essential Information About SSL/TLS" manpage
If you are trying to use it with threads see the BUGS section.
* * the /"Basic SSL Client" manpage
* * the /"Basic SSL Server" manpage
* * the /"Common Usage Errors" manpage
* * the /"Common Problems with SSL" manpage
* * the /"Using Non-Blocking Sockets" manpage
* * the /"Advanced Usage" manpage
* * the /"Integration Into Own Modules" manpage
* * the /"Description Of Methods" manpage
Additional documentation can be found in
* * the IO::Socket::SSL::Intercept manpage - Doing Man-In-The-Middle with
SSL
* * the IO::Socket::SSL::Utils manpage - Useful functions for certificates
etc
%prep
%setup -q -n %{cpan_name}-%{version}