From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: libnettle/libhogweed WIP Date: Fri, 14 Apr 2017 16:48:39 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87wpamww9k.fsf@lifelogs.com> References: <83a89gq3us.fsf@gnu.org> <87bmtjiv0w.fsf_-_@lifelogs.com> <83o9xjn06c.fsf@gnu.org> <87shmeb5ln.fsf_-_@lifelogs.com> <83y3w5z1ez.fsf@gnu.org> <87lgr6yakj.fsf@lifelogs.com> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1492202984 9008 195.159.176.226 (14 Apr 2017 20:49:44 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 14 Apr 2017 20:49:44 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Apr 14 22:49:39 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cz89z-0002CM-GS for ged-emacs-devel@m.gmane.org; Fri, 14 Apr 2017 22:49:39 +0200 Original-Received: from localhost ([::1]:54587 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cz8A5-0004cI-Cy for ged-emacs-devel@m.gmane.org; Fri, 14 Apr 2017 16:49:45 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58996) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cz89L-0004c1-N7 for emacs-devel@gnu.org; Fri, 14 Apr 2017 16:49:02 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cz89I-00039d-I0 for emacs-devel@gnu.org; Fri, 14 Apr 2017 16:48:59 -0400 Original-Received: from [195.159.176.226] (port=42982 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cz89I-00036d-B7 for emacs-devel@gnu.org; Fri, 14 Apr 2017 16:48:56 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cz895-00010b-69 for emacs-devel@gnu.org; Fri, 14 Apr 2017 22:48:43 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 46 Original-X-Complaints-To: usenet@blaine.gmane.org X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never Cancel-Lock: sha1:GWdVAPmKQdZckDpiXmwfawhoVa4= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:213963 Archived-At: On Tue, 11 Apr 2017 16:05:16 -0400 Ted Zlatanov wrote: TZ> I updated the branch scratch/tzz/nettle with comprehensive TZ> tests. It now mirrors the low-level API in the GnuTLS crypto.h TZ> functions, so there's no libnettle/libhogweed dependency. The API was TZ> pretty different so I had to rewrite almost everything. I've put this work up on https://gitlab.com/emacs-ci/emacs/merge_requests/2 for those who want to use Gitlab to comment. Updates from my previous post: TZ> * the AEAD ciphers "CHACHA20-POLY1305" "AES-128-CCM-8" "AES-256-CCM-8" TZ> are not working yet. This is fixed, all ciphers (AEAD and non-AEAD) work now. TZ> * TODO from Eli: avoid allocating a scratch buffer and then copying its TZ> data (inside make_unibyte_string) into a newly-allocated string. TZ> Instead, use make_uninit_string. I've done this as much as possible. For AEAD output, I'm not sure how to set the length of an already-allocated string; I didn't want to modify `s.size' directly. I didn't see a function or macro to do it. This is needed for gnutls_symmetric_aead(). I also wanted to mention two possible avenues to explore: 1) how about a special C data structure that has to be called to get its payload data, but can't be inspected or printed otherwise, and after N reads is inaccessible? Would that be resistant to Lisp-level attempts to grab the data? 2) Could there be a built-in C way to let C core functions take strings, but callers can invoke them with '(buffer-string) to tell *the core function* to call that form. In other words, I want the eval to be done at the C level, so that looking at the call tree won't reveal the actual string that was passed to the function. I think that would simplify my code and other C code too. I can probably fake it with eval()? WDYT? If that's not possible, I'll pull the first part of fns.c:secure_hash() out into a common function for the gnutls.c crypto functions as well, so they can take buffer contents etc. easily. Ted