diff options
author | Ben Carrillo <ben@futeisha.org> | 2013-01-28 09:09:07 +0900 |
---|---|---|
committer | Ben Carrillo <ben@futeisha.org> | 2013-01-28 09:09:07 +0900 |
commit | 7761b24a526987fad55af130e20417503d2cea51 (patch) | |
tree | abdb5628bb63b3937f4242b7f4a01487d321e33a /debian/control |
initial packaging attempt
Diffstat (limited to 'debian/control')
-rw-r--r-- | debian/control | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/debian/control b/debian/control new file mode 100644 index 0000000..53996fd --- /dev/null +++ b/debian/control @@ -0,0 +1,35 @@ +Source: srp +Maintainer: Ben Carrillo <ben@futeisha.org> +Section: python +Priority: optional +Build-Depends: python-all-dev (>= 2.6.6-3), debhelper (>= 9) +Standards-Version: 3.9.4 +Vcs-Hg: https://code.google.com/p/pysrp/ +Vcs-Browser: http://code.google.com/p/pysrp/source/browse/ +Homepage: http://code.google.com/p/pysrp/ + +Package: python-srp +Architecture: any +Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends} +Description: Secure Remote Password protocol implementation + 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 Kereros 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. |