| Name : perl-Net-SSLeay-OO
| |
| Version : 0.02
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : 1.1
| Date : 2016-06-24 07:45:41
|
| Group : Development/Libraries/Perl
| Source RPM : perl-Net-SSLeay-OO-0.02-1.1.src.rpm
|
| Size : 0.13 MB
| |
| Packager : (none)
| |
| Summary : OO Calling Method for Net::SSLeay
|
Description :
This set of modules adds an OO calling convention to the the Net::SSLeay
manpage module. It steers away from overly abstracting things, or adding
new behaviour, instead just making the existing functionality easier to
use.
What does this approach win you over the Net::SSLeay manpage?
* *Object Orientation*
For a start, you get a blessed object rather than an integer to work
with, so you know what you are dealing with. All of the functions which
were callable with \'Net::SSLeay::foo($ssl, AATTargs)\' will then be callable
as plain \'$ssl->foo(AATTargs)\'.
* *Namespaces*
The OpenSSL functions use a C-style namespace convention, where functions
are prefixed by the type of the object that they operate on. OpenSSL has
several types of objects, such as a \"Context\" (this is a bit like a bunch
of pre-defined connection settings), and various classes relating to
X509, sessions, etc.
This module splits up the functions which the Net::SSLeay manpage binds
into Perl based on the naming convention, then sets up wrappers for them
so that you can just call methods on objects.
* *Exceptions*
If an error is raised by the OpenSSL library, an exception is immediately
raised (trappable via \'eval\') which pretty-prints into something
presented a little less cryptic than OpenSSL\'s \':\'-delimited error string
format.
* *fewer segfaults*
This is currently more of a promise than a reality; but eventually each
of the access methods for the various objects will be able to know their
lifetime in a robust fashion, so you should get less segfaults. Eg, some
SSL functions don\'t return object references which are guaranteed to last
very long, so if you wait too long before getting properties from them
you will get a segfault.
On the flip side, what does this approach win you over other simpler APIs
such as the IO::Socket::SSL manpage? Well, I guess it comes down to \"Make
things as simple as possible, but no simpler\".
Most SSL socket libraries tend to try to hide complexity from you, but
there really are things that you should consider; such as, shouldn\'t you be
validating the other end of your SSL connection has a valid certificate?
Which SSL versions do you wish to allow?
the IO::Socket::SSL manpage lets you specify a lot of this stuff, but it\'s
not a very earnest implementation; it\'s just treated as a few extra options
passed to the constructor, a bit of magic at socket setup time, and then
hope that this will be enough. The support for verifying client
certificates didn\'t even work when I tested it.
On the other hand, using the OpenSSL API fully means you are taken through
the stages of setup piece by piece. You can easily do things like check
that your SSL configuration (eg server certificate) is valid _before_ you
start daemonize or start accepting real sockets.
I\'ll try to keep the documentation as complete as possible - there\'s
nothing more annoying than thin wrapper libraries which don\'t help much
people trying to use them. But in general, most functions available in the
OpenSSL manual will be available.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl/SLE_12_SP1/noarch |
Hmm ... It's impossible ;-) This RPM doesn't exist on any FTP server
Provides :
perl(Net::SSLeay::OO)
perl(Net::SSLeay::OO::Constants)
perl(Net::SSLeay::OO::Context)
perl(Net::SSLeay::OO::Error)
perl(Net::SSLeay::OO::Functions)
perl(Net::SSLeay::OO::SSL)
perl(Net::SSLeay::OO::Session)
perl(Net::SSLeay::OO::X509)
perl(Net::SSLeay::OO::X509::Context)
perl(Net::SSLeay::OO::X509::Name)
perl(Net::SSLeay::OO::X509::Store)
perl-Net-SSLeay-OO
Requires :
