[Top][All Lists]

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

[debbugs-tracker] bug#32399: closed ([PATCH] gnu: Add asignify.)

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#32399: closed ([PATCH] gnu: Add asignify.)
Date: Mon, 10 Sep 2018 00:08:02 +0000

Your message dated Sun, 9 Sep 2018 20:07:06 -0400
with message-id <address@hidden>
and subject line Re: bug#32399: Acknowledgement ([PATCH] gnu: Add asignify.)
has caused the debbugs.gnu.org bug report #32399,
regarding [PATCH] gnu: Add asignify.
to be marked as done.

(If you believe you have received this mail in error, please contact

32399: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32399
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: [PATCH] gnu: Add asignify. Date: Wed, 8 Aug 2018 10:34:19 -0400
I wonder if we should mark this program as "experimental" or "not
audited?" It includes the features I'd like to have in a tool for
signing and authenticated encryption, but it hasn't received much
cryptanalytic attention, from what I can tell.

* gnu/packages/crypto.scm (asignify): New variable.
 gnu/packages/crypto.scm | 37 +++++++++++++++++++++++++++++++++++++
 1 file changed, 37 insertions(+)

diff --git a/gnu/packages/crypto.scm b/gnu/packages/crypto.scm
index 730895efd..00fa1e8d2 100644
--- a/gnu/packages/crypto.scm
+++ b/gnu/packages/crypto.scm
@@ -813,3 +813,40 @@ which is also used in the Advanced Encryption Standard 
(AES, see
 @url{http://www.nist.gov/aes}).  This cipher is believed to provide very strong
     (license license:gpl2)))
+(define-public asignify
+  (let ((commit "f58e7977a599f040797975d649ed318e25cbd2d5")
+        (revision "0"))
+    (package
+      (name "asignify")
+      (version (git-version "1.1" revision commit))
+      (source (origin
+                (method git-fetch)
+                (uri (git-reference
+                       (url "https://github.com/vstakhov/asignify.git";)
+                       (commit commit)))
+                (sha256
+                 (base32
+                  "1zl68qq6js6fdahxzyhvhrpyrwlv8c2zhdplycnfxyr1ckkhq8dw"))))
+      (build-system gnu-build-system)
+      (arguments
+       `(#:configure-flags
+         (list "--enable-openssl"
+               (string-append "--with-openssl="
+                              (assoc-ref %build-inputs "openssl")))))
+      (native-inputs
+       `(("autoconf" ,autoconf)
+         ("automake" ,automake)
+         ("libtool" ,libtool)))
+      (inputs
+       `(("openssl" ,openssl-next)))
+      (home-page "https://github.com/vstakhov/asignify";)
+      (synopsis "Cryptographic authentication and encryption tool and library")
+      (description "Asignify offers public cryptographic signatures and
+encryption with a library or a command-line tool.  The tool is heavily inspired
+by signify as used in OpenBSD.  The main goal of this project is to define a
+high level API for signing files, validating signatures and encrypting using
+public-key cryptography.  Asignify is designed to be portable and 
+with zero external dependencies.  Asignify can verify OpenBSD signatures, but 
+cannot sign messages in OpenBSD format yet.")
+      (license license:bsd-2))))

--- End Message ---
--- Begin Message --- Subject: Re: bug#32399: Acknowledgement ([PATCH] gnu: Add asignify.) Date: Sun, 9 Sep 2018 20:07:06 -0400 User-agent: Mutt/1.10.1 (2018-07-13)
Pushed as de15ff1a6c319a46046093d26baa6117c6a22e73

Attachment: signature.asc
Description: PGP signature

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]