Hello community,

here is the log from the commit of package perl-IO-Socket-SSL for 
openSUSE:Factory checked in at 2014-07-28 06:31:02
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/perl-IO-Socket-SSL (Old)
 and      /work/SRC/openSUSE:Factory/.perl-IO-Socket-SSL.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "perl-IO-Socket-SSL"

Changes:
--------
--- /work/SRC/openSUSE:Factory/perl-IO-Socket-SSL/perl-IO-Socket-SSL.changes    
2014-03-27 06:08:53.000000000 +0100
+++ 
/work/SRC/openSUSE:Factory/.perl-IO-Socket-SSL.new/perl-IO-Socket-SSL.changes   
    2014-07-28 06:31:03.000000000 +0200
@@ -1,0 +2,5 @@
+Fri Jul 25 09:32:05 UTC 2014 - [email protected]
+
+- updated to 1.997, huge Changes 
+
+-------------------------------------------------------------------

Old:
----
  IO-Socket-SSL-1.970.tar.gz

New:
----
  IO-Socket-SSL-1.997.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ perl-IO-Socket-SSL.spec ++++++
--- /var/tmp/diff_new_pack.QkoBiE/_old  2014-07-28 06:31:04.000000000 +0200
+++ /var/tmp/diff_new_pack.QkoBiE/_new  2014-07-28 06:31:04.000000000 +0200
@@ -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 @@
 %{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.
-
-If you have never used SSL before, you should read the section 'Using SSL'
-before attempting to use this module.
-
-If you used IO::Socket before you should read the following section
-'Differences to IO::Socket'.
-
-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.
+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 are trying to use it with threads see the BUGS section.
+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.
+
+The documentation consists of the following parts:
+
+* * the /"Essential Information About SSL/TLS" manpage
+
+* * 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}

++++++ IO-Socket-SSL-1.970.tar.gz -> IO-Socket-SSL-1.997.tar.gz ++++++
++++ 16880 lines of diff (skipped)

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to