|Summary:||[NEW PORT] security/py-pyaxo: Python implementation of the Axolotl ratchet protocol|
|Product:||Ports & Packages||Reporter:||Yuri Victorovich <yuri>|
|Component:||Individual Port(s)||Assignee:||Richard Gallamore <ultima>|
|Severity:||Affects Only Me||CC:||ultima|
|Bug Depends on:|
Description Yuri Victorovich 2017-09-04 00:25:35 UTC
Created attachment 186046 [details] shar QAs: * poudriere 11.1 amd64 * portlint It isn't clear which versions of python are supported. I labeled it as up-to 2.7, and asked upstream to clarify.
Comment 1 Yuri Victorovich 2017-09-04 00:26:44 UTC
Created attachment 186047 [details] shar Moved to security/ section.
Comment 2 Richard Gallamore 2017-09-10 21:37:55 UTC
Looks good, tested with python 3.6 and is buildable so removed the 2.7 label.
Comment 3 commit-hook 2017-09-11 21:14:02 UTC
A commit references this bug: Author: ultima Date: Mon Sep 11 21:13:54 UTC 2017 New revision: 449667 URL: https://svnweb.freebsd.org/changeset/ports/449667 Log: The Double Ratchet Algorithm is a protocol (similar to OTR) that provides for perfect forward secrecy in (a)synchronous communications. It uses triple Diffie-Hellman for authentication and ECDHE for perfect forward secrecy. The protocol is lighter and more robust than the OTR protocol - providing better forward and future secrecy, as well as deniability. The protocol was developed by Trevor Perrin and Moxie Marlinspike. Its chief use currently is in the Open Whisper Systems Signal package. WWW: https://github.com/rxcomm/pyaxo PR: 222040 Submitted by: Yuri Victorovich (maintainer) Reviewed by: lifanov (mentor), matthew (mentor), koobs, sunpoet Approved by: lifanov (mentor), matthew (mentor), koobs Differential Revision: https://reviews.freebsd.org/D12310 Changes: head/security/Makefile head/security/py-pyaxo/ head/security/py-pyaxo/Makefile head/security/py-pyaxo/distinfo head/security/py-pyaxo/pkg-descr
Comment 4 Richard Gallamore 2017-09-11 21:22:57 UTC
There were some build errors in the python36 version so I readded the 2.7. It will probably be best to wait for upstream to clarify as you commented. Committed, thanks!