[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#699122: marked as done (ITP: python-srp -- Secure Remote Password protocol implementation)

Your message dated Sat, 7 Dec 2013 09:43:04 +1100
with message-id <CA+K2i_2myNt68ny3E_H6NJFB3__LhY0rffOGy04xZOa-Zv4xHg@mail.gmail.com>
and subject line 
has caused the Debian Bug report #699122,
regarding ITP: python-srp -- Secure Remote Password protocol implementation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
699122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699122
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist

* Package name    : python-srp
  Version         : 1.0.2
  Upstream Author : Tom Cocagne
* URL             : http://code.google.com/p/pysrp/
* License         : New BSD
  Programming Lang: Python
Download URL : http://pypi.python.org/packages/source/s/srp/srp-1.0.2.tar.gz#md5=8bcf643edd3f10d8f125fb91bd828c5d 
  Documentation   : http://packages.python.org/srp/
  Description     : secure remote password implementation

Description
-----------
This package provides an implementation of the Secure Remote Password protocol (SRP). SRP is a cryptographically strong authentication protocol for password-based, mutual authentication over an insecure network connection.
Unlike other common challenge-response autentication protocols, such as Kerberos and SSL, SRP does not rely on an external infrastructure of trusted key servers or certificate management. Instead, SRP server applications use verification keys derived from each user's password to determine the authenticity of a network connection.
SRP provides mutual-authentication in that successful authentication requires both sides of the connection to have knowledge of the user's password. If the client side lacks the user's password or the server side lacks the proper verification key, the authentication will fail.
Unlike SSL, SRP does not directly encrypt all data flowing through the authenticated connection. However, successful authentication does result in a cryptographically strong shared key that can be used for symmetric-key encryption.
--- End Message ---
--- Begin Message ---


--- End Message ---
Reply to: