Page MenuHomeFreeBSD

[NEW PORT] net-im/py-unmessage: Privacy enhanced instant messenger
ClosedPublic

Authored by ultima on Sep 10 2017, 10:03 PM.
Tags
None
Referenced Files
F79493826: D12312.diff
Tue, Mar 19, 4:02 AM
Unknown Object (File)
Wed, Mar 6, 8:50 AM
Unknown Object (File)
Wed, Mar 6, 8:49 AM
Unknown Object (File)
Wed, Mar 6, 8:49 AM
Unknown Object (File)
Tue, Mar 5, 9:36 AM
Unknown Object (File)
Feb 7 2024, 7:45 PM
Unknown Object (File)
Feb 1 2024, 12:27 PM
Unknown Object (File)
Jan 4 2024, 12:25 AM
Subscribers

Details

Summary

unMessage is a peer-to-peer instant messaging application designed to enhance
privacy and anonymity.

Features:

  • Transport makes use of Twisted, Tor Onion Services and txtorcon
  • Encryption is performed using the Double Ratchet Algorithm implemented in pyaxo (using PyNaCl)
  • Authentication makes use of the Socialist Millionaire Protocol implemented in Cryptully
  • Transport metadata is minimized by Tor and application metadata by the unMessage protocol
  • User interfaces are created with Tkinter (graphical) and curses (command-line)

WWW: https://github.com/AnemoneLabs/unmessage

PR\: 222043
Submitted by\: Yuri Victorovich (maintainer)
Reviewed by\: lifanov (mentor), matthew (mentor)
Approved by\: lifanov (mentor), matthew (mentor)
Differential Revision\: https://reviews.freebsd.org/DXXXXX

Test Plan

portlint:
WARN: Makefile: no port directory /usr/ports/audio/py-opuslib found, even though it is listed in RUN_DEPENDS.
WARN: Makefile: no port directory /usr/ports/security/py-pyaxo found, even though it is listed in RUN_DEPENDS.
WARN: Makefile: no port directory /usr/ports/security/py-txtorcon found, even though it is listed in RUN_DEPENDS.
0 fatal errors and 3 warnings found.

Wont be committed till after D12309 D12310 and D12311 which will resolve these.

poudriere:
103i386
103amd64
110i386
110amd64
12i386
12amd64

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

koobs requested changes to this revision.Sep 11 2017, 5:51 AM
koobs added a subscriber: koobs.

Missing SUBDIR addition to category/Makefile in changeset

This revision now requires changes to proceed.Sep 11 2017, 5:51 AM

New port needs entries in the category Makefile. Other than that, this looks fine.

Missing SUBDIR addition to category/Makefile in changeset

New port needs entries in the category Makefile. Other than that, this looks fine.

I was planning on using the Tools/scripts/addport script to add the port which automatically adds this bit. Is this acceptable or does it require to be in the Phabricator differential?

Missing SUBDIR addition to category/Makefile in changeset

New port needs entries in the category Makefile. Other than that, this looks fine.

I was planning on using the Tools/scripts/addport script to add the port which automatically adds this bit. Is this acceptable or does it require to be in the Phabricator differential?

I (personally) prefer to see it in reviews, as reviewers assume nothing and cant know that it wasn't just accidentally forgotten, which goes for anything else.

Missing SUBDIR addition to category/Makefile in changeset

New port needs entries in the category Makefile. Other than that, this looks fine.

I was planning on using the Tools/scripts/addport script to add the port which automatically adds this bit. Is this acceptable or does it require to be in the Phabricator differential?

I (personally) prefer to see it in reviews, as reviewers assume nothing and cant know that it wasn't just accidentally forgotten, which goes for anything else.

Using the addport script is definitely the way to go. I'm happy for you to add this port that way without needing to see a diff of the changes to the category Makefile. However, as @koobs said: if it wasn't mentioned in the review, then the reviewers have no way of knowing if you had actually forgotten about that part, or not.

I'm good with this revision. Make sure you commit the dependencies in order or at the same time so that the tree is consistent.

I personally prefer to see the entire change, including the category file update, but I don't feel strongly about it.

This revision was automatically updated to reflect the committed changes.