Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

Virtual Ideal Functionality Framework 0.7.1 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Virtual Ideal Functionality Framework 0.7.1 (Default branch)
# 1  
Old 10-09-2008
Virtual Ideal Functionality Framework 0.7.1 (Default branch)
Virtual Ideal Functionality Framework is a framework for creating efficient and secure multi-party computations (SMPC). Players, who do not trust each other, participate in a joint computation based on their private inputs. The computation is done using a cryptographic protocol which allows them to obtain a correct answer without revealing their inputs. Operations supported include addition, multiplication, and comparison, all with Shamir secret shared outputs. License: GNU Lesser General Public License (LGPL) Changes:
A major bug was fixed in the passive multiplication protocol in the case where 2t + 1 != n. Unit tests were updated for Python 2.6. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

class::virtually::abstract

Class::Virtually::Abstract(3pm) 			User Contributed Perl Documentation			   Class::Virtually::Abstract(3pm)

NAME

       Class::Virtually::Abstract - Compile-time enforcement of Class::Virtual

SYNOPSIS

	 package My::Virtual::Idaho;
	 use base qw(Class::Virtually::Abstract);

	 __PACKAGE__->virtual_methods(qw(new foo bar this that));

	 package My::Private::Idaho;
	 use base qw(My::Virtual::Idaho);

	 sub new { ... }
	 sub foo { ... }
	 sub bar { ... }
	 sub this { ... }
	 # oops, forgot to implement that()!!  Whatever will happen?!

	 # Meanwhile, in another piece of code!
	 # KA-BLAM!  My::Private::Idaho fails to compile because it didn't
	 # fully implement My::Virtual::Idaho.
	 use My::Private::Idaho;

DESCRIPTION

       This subclass of Class::Virtual provides compile-time enforcement.  That means subclasses of your virtual class are required to implement
       all virtual methods or else it will not compile.

BUGS and CAVEATS
       Because this relies on import() it is important that your classes are used instead of required.	This is a problem, and I'm trying to
       figure a way around it.

       Also, if a subclass defines its own import() routine (I've done it) Class::Virtually::Abstract's compile-time checking is defeated.

       Got to think of a better way to do this besides import().

AUTHOR

       Original idea and code from Ben Tilly's AbstractClass http://www.perlmonks.org/index.pl?node_id=44300&lastnode_id=45341

       Embraced and Extended by Michael G Schwern <schwern@pobox.com>

SEE ALSO

       Class::Virtual

perl v5.10.1							    2007-10-23					   Class::Virtually::Abstract(3pm)