Distributed Object Technology system written entirely in Python, that is
designed to be very easy to use. Never worry about writing network
communication code again, when using Pyro you just write your Python
objects like you would normally. With only a few lines of extra code,
Pyro takes care of the network communication between your objects once
you split them over different machines on the network. All the gory
socket programming details are taken care of, you just call a method on
a remote object as if it were a local object!
Pyro provides an object-oriented form of RPC. You can use Pyro within a
single system but also use it for IPC. For those that are familiar with
Java, Pyro resembles Java's Remote Method Invocation (RMI). It is less
similar to CORBA - which is a system- and language independent
Distributed Object Technology and has much more to offer than Pyro or
RMI. But Pyro is small, simple and free!
WWW: http://pyro.sf.net
PR: ports/130053
Submitted by: Wen Heping <wenheping at gmail.com>
chosen dynamically at runtime in this version.
PR: 128416
Submitted by: Milan Bartos <merlyn500@gmail.com>
Patch by: stefan
Approved by: maintainer timeout (>2 months)
the fix for the following vulnerability: https://www.isc.org/node/373
Description:
Return values from OpenSSL library functions EVP_VerifyFinal()
and DSA_do_verify() were not checked properly.
Impact:
It is theoretically possible to spoof answers returned from
zones using the DNSKEY algorithms DSA (3) and NSEC3DSA (6).
In short, if you're not using DNSSEC to verify signatures you have
nothing to worry about.
While I'm here, address the issues raised in the PR by adding a knob
to disable building with OpenSSL altogether (which eliminates DNSSEC
capability), and fix the configure arguments to better deal with the
situation where the user has ssl bits in both the base and LOCALBASE.
PR: ports/126297
Submitted by: Ronald F.Guilmette <rfg@tristatelogic.com>
interacting with a PostgreSQL database. It supports version 3.0
of the protocol--the current primary version of protocol. The
package also provides a basic protocol transaction class. This
class keeps the state of the protocol in an interrupt safe manner,
and validates the integrity of the communication as messages are
received.
In general, you probably will never use this package directly,
unless you are writing a driver.
WWW: http://python.projects.postgresql.org/
PR: ports/130252
Submitted by: Wen Heping <wenheping at gmail.com>
