Hello community,

here is the log from the commit of package opmsg for openSUSE:Factory checked 
in at 2017-03-31 15:08:04
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/opmsg (Old)
 and      /work/SRC/openSUSE:Factory/.opmsg.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "opmsg"

Fri Mar 31 15:08:04 2017 rev:2 rq:482308 version:1.75s

Changes:
--------
--- /work/SRC/openSUSE:Factory/opmsg/opmsg.changes      2017-03-04 
16:49:15.489469339 +0100
+++ /work/SRC/openSUSE:Factory/.opmsg.new/opmsg.changes 2017-03-31 
15:08:05.696197214 +0200
@@ -1,0 +2,5 @@
+Thu Mar  2 10:15:15 UTC 2017 - jeng...@inai.de
+
+- Update description
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ opmsg.spec ++++++
--- /var/tmp/diff_new_pack.iX8xgm/_old  2017-03-31 15:08:06.428093740 +0200
+++ /var/tmp/diff_new_pack.iX8xgm/_new  2017-03-31 15:08:06.432093174 +0200
@@ -20,7 +20,7 @@
 Name:           opmsg
 Version:        1.75s
 Release:        0
-Summary:        A gpg alternative
+Summary:        File encryption, sign and verify utility
 License:        GPL-3.0+
 Group:          Productivity/Security
 Url:            https://github.com/stealth/opmsg
@@ -36,6 +36,17 @@
 create/verify detached signatures of local files. Even though the opmsg
 output looks similar, the concept is entirely different.
 
+* Perfect Forward Secrecy (PFS) by means of ECDH or DH Kex.
+* Native EC or RSA fallback if no (EC)DH keys left.
+* Signing messages is mandatory.
+* OTR-like deniable signatures if demanded.
+* Support for 1:1 key bindings to auto-select source key per
+  destination.
+* Adds the possibility to (re-)route messages different from mail
+  address to defeat meta data collection.
+* Key format suitable for easy use with QR codes.
+* Optional cross-domain ECDH Kex.
+
 %prep
 %setup -q -n %{name}-%{gittag}
 


Reply via email to