From gniibe at fsij.org Wed Mar 1 01:50:38 2017 From: gniibe at fsij.org (NIIBE Yutaka) Date: Wed, 01 Mar 2017 09:50:38 +0900 Subject: Computer Science bachelor degree thesis on Libgcrypt In-Reply-To: <1665aa81c11b866ad016dc88a6f8ab44@bdslabs.com.br> References: <5d8f5fe810e2cf72b5ae1f9f546e2e2f@bdslabs.com.br> <878tphysx5.fsf@fsij.org> <614414d8e848ed9f466ed921957ec9c4@bdslabs.com.br> <1665aa81c11b866ad016dc88a6f8ab44@bdslabs.com.br> Message-ID: <8760jtakgx.fsf@iwagami.gniibe.org> Hello, If you have a machine, you can build libgcrypt and do "make check" to run those tests. Attached is an example output of "make check". You can have a look and see what kinds of tests are there. "Marcio Barbado, Jr." wrote: > * well, given all of the recent buzz around SHA-1 collision, we're > considering tests among the substitution candidates (eg: BLAKE2, SHA-256 > and SHA-3). > > > So, concerning those tests, we have some questions like: are there any > architectures and/or contexts on which new benchmarks could be helpful > at this moment? For hash functions, we have libgcrypt/tests/hashtest.c and md_bench function in libgcrypt/tests/benchmark.c. Please have a look. We have those tests, basically to detect regression (for correctness and for performance), during our development [0]. Usually, we add tests based on existing test vectors for each algorithm [1]. We add tests based on bug reports, and write benchmark to measure performance. Well, what do you intend for your new benchmarks? Please note that this is the development mailing list, the major purpose is not for education. While we welcome questions about libgcrypt implementation and contribution to the development and you can learn by joining discussion, we can't answer question like what kind of study could be done by you. We don't know that. I think you should ask your teacher. [0] https://en.wikipedia.org/wiki/Regression_testing [1] https://en.wikipedia.org/wiki/Test_vector Hope this helps, -- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: example-output-make-check.txt URL: From cvs at cvs.gnupg.org Wed Mar 8 13:10:40 2017 From: cvs at cvs.gnupg.org (by Justus Winter) Date: Wed, 08 Mar 2017 13:10:40 +0100 Subject: [git] GCRYPT - branch, master, updated. libgcrypt-1.7.3-77-g6540240 Message-ID: This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "The GNU crypto library". The branch, master has been updated via 654024081cfa103c87bb163b117ea3568171d408 (commit) from 5bd530b8a4624f101b8d42e68f1b28bcc13f4f76 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 654024081cfa103c87bb163b117ea3568171d408 Author: Justus Winter Date: Wed Mar 8 13:09:11 2017 +0100 build: Use macOS' compatibility macros to enable all features. * configure.ac: On macOS, use the compatibility macros to expose every feature of the libc. This is the equivalent of _GNU_SOURCE on GNU libc. -- Not defining this leads to compilation errors or superfluous warnings on macOS. GnuPG-bug-id: 2910 Signed-off-by: Justus Winter diff --git a/configure.ac b/configure.ac index 78508ec..2609b41 100644 --- a/configure.ac +++ b/configure.ac @@ -270,6 +270,10 @@ case "${host}" in ;; m68k-atari-mint) ;; + *-apple-darwin*) + AC_DEFINE(_DARWIN_C_SOURCE, 900000L, + Expose all libc features (__DARWIN_C_FULL).) + ;; *) ;; esac ----------------------------------------------------------------------- Summary of changes: configure.ac | 4 ++++ 1 file changed, 4 insertions(+) hooks/post-receive -- The GNU crypto library http://git.gnupg.org _______________________________________________ Gnupg-commits mailing list Gnupg-commits at gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-commits From Antoine.Morvan at insa-rennes.fr Wed Mar 15 11:43:21 2017 From: Antoine.Morvan at insa-rennes.fr (Antoine Morvan) Date: Wed, 15 Mar 2017 11:43:21 +0100 (CET) Subject: GNU.org libgcrypt homepage Message-ID: <1356770828.9364424.1489574601534.JavaMail.zimbra@insa-rennes.fr> Hi, I was trying to access the development versions of libgcrypt from URL ftp://ftp.gnupg.org/gcrypt/alpha/libgcrypt/, as specified on the page https://www.gnu.org/software/libgcrypt/. However the server returns error 550: "directory does not exist". I was able to get the code on git, but just wanted to mention that broken link. Best regards. -- Antoine Morvan Research Engineer INSA - D?partement EII 20, Avenue des Buttes de Co?smes CS 70839, F - 35708 Rennes Cedex 7 mail: antoine.morvan at insa-rennes.fr phone: +33 2 23 23 88 15 From hanno at hboeck.de Wed Mar 15 21:55:30 2017 From: hanno at hboeck.de (Hanno =?UTF-8?B?QsO2Y2s=?=) Date: Wed, 15 Mar 2017 21:55:30 +0100 Subject: GNU.org libgcrypt homepage In-Reply-To: <1356770828.9364424.1489574601534.JavaMail.zimbra@insa-rennes.fr> References: <1356770828.9364424.1489574601534.JavaMail.zimbra@insa-rennes.fr> Message-ID: <20170315215530.76814bd0@pc1> On Wed, 15 Mar 2017 11:43:21 +0100 (CET) Antoine Morvan wrote: > I was trying to access the development versions of libgcrypt from URL > ftp://ftp.gnupg.org/gcrypt/alpha/libgcrypt/, as specified on the page > https://www.gnu.org/software/libgcrypt/. However the server returns > error 550: "directory does not exist". I was able to get the code on > git, but just wanted to mention that broken link. This may be because someone decided it's the sane thing to switch off ftp. It's an inherently insecure protocol (there is ftp+tls, but no browser supports it, so it's not an option for downloads). Here's the right URL: https://gnupg.org/ftp/gcrypt/libgcrypt/ Someone should just update the webpage. -- Hanno B?ck https://hboeck.de/ mail/jabber: hanno at hboeck.de GPG: FE73757FA60E4E21B937579FA5880072BBB51E42 From wk at gnupg.org Thu Mar 16 08:09:42 2017 From: wk at gnupg.org (Werner Koch) Date: Thu, 16 Mar 2017 08:09:42 +0100 Subject: GNU.org libgcrypt homepage In-Reply-To: <20170315215530.76814bd0@pc1> ("Hanno =?utf-8?Q?B=C3=B6ck=22'?= =?utf-8?Q?s?= message of "Wed, 15 Mar 2017 21:55:30 +0100") References: <1356770828.9364424.1489574601534.JavaMail.zimbra@insa-rennes.fr> <20170315215530.76814bd0@pc1> Message-ID: <87d1dhy9xl.fsf@wheatstone.g10code.de> On Wed, 15 Mar 2017 21:55, hanno at hboeck.de said: > This may be because someone decided it's the sane thing to switch off > ftp. It's an inherently insecure protocol (there is ftp+tls, but no Nope. It is merely that there is no alpha/libgcrypt directory anymore. We provide signatures for all files on the ftp server. Checking the signatures is a far better practice than to rely on a public exposed server and the questionable security of X.509 secured TLS connections. > Here's the right URL: > https://gnupg.org/ftp/gcrypt/libgcrypt/ The landing page is https://gnupg.org/related_software/libgcrypt/ which tells you the current version. I'll change the gnu.org page to redirect to the above thing. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: