nettle-bugs July 2021

nettle-bugs@lists.lysator.liu.se

4 participants
14 discussions

Add RSA-OAEP encryption/decryption to Nettle
by Nicolas Mora 09 Mar '24

09 Mar '24

Hello, I've made a new Merge Request in the nettle gitlab repo to provide RSA-OAEP encryption and decryption: https://git.lysator.liu.se/nettle/nettle/-/merge_requests/20 It adds 2 new functions: int pkcs1_oaep_encrypt (size_t key_size, void *random_ctx, nettle_random_func *random, size_t hlen, size_t label_length, const uint8_t *label, size_t message_length, const uint8_t *message, mpz_t m); int pkcs1_oaep_decrypt (size_t key_size, const mpz_t m, size_t hlen, size_t label_length, const uint8_t *label, size_t *length, uint8_t *message); The parameter hlen is the output length of the SHA function used for masking data: - SHA1_DIGEST_SIZE - SHA256_DIGEST_SIZE - SHA384_DIGEST_SIZE - SHA512_DIGEST_SIZE Is it possible to get feedback for this MR and eventually push it to the master branch? Thanks in advance /Nicolas

4 21

Curve point decompression
by Wim Lewis 10 Nov '21

10 Nov '21

I'm looking at implementing elliptic curve point compression a la SEC1 (admittedly, mostly to reduce the number of "feature not supported" code paths in a library, but it seems like a somewhat useful ability). Nettle/Hogweed already implements it internally for curve25519, but I want to implement it for the "secp" curves as well. Point compression is easy enough, but point decompression requires some curve math, potentially dependent on the specific curve, and some of it is redundant with what's already done in ecc_point_set(). So I was thinking about moving this functionality into Hogweed as a function along the lines of ecc_point_set_compressed(), which would take, instead of a y-coordinate, an int containing the sign/parity of the y-coordinate. So my question for the list and for the maintainers is, is this a reasonable API to add to Hogweed? Is there interest in including it in Hogweed if I were to take the time to turn it into a tidy patch?

3 10

[S390x] Optimize SHA1 with fat build support
by Maamoun TK 20 Sep '21

20 Sep '21

I made a merge request in the main repository that optimizes SHA1 for s390x architecture with fat build support !33 <https://git.lysator.liu.se/nettle/nettle/-/merge_requests/33>. regards, Mamone

2 10

[S390x] Optimize AES modes
by Maamoun TK 19 Sep '21

19 Sep '21

I made a merge request for optimizing AES modes on s390x architecture, the patch implements the optimized cores using cipher instructions that have been added to s390x arch in message security assist extensions. The patch uses the following functions: KM-AES-128 (ECB-AES128) KM-AES-192 (ECB-AES192) KM-AES-256 (ECB-AES256) KMC-AES-128 (CBC-AES128) KMC-AES-192 (CBC-AES192) KMC-AES-256 (CBC-AES256) KMAC-AES-128 (CCM-AES128, CMAC-AES128) KMAC-AES-192 (CCM-AES192) KMAC-AES-256 (CCM-AES256, CMAC-AES256) KMF-AES-128 (CFB-AES128, CFB8-AES128) KMF-AES-192 (CFB-AES192, CFB8-AES192) KMF-AES-256 (CFB-AES256, CFB8-AES256) KM-XTS-AES-128 (XTS-AES128) KM-XTS-AES-256 (XTS-AES256) KIMD-GHASH (GHASH) KMCTR-AES-128, KMA-GCM-AES-128 (CTR-AES128) KMCTR-AES-192, KMA-GCM-AES-192 (CTR-AES192) KMCTR-AES-256, KMA-GCM-AES-256 (CTR-AES256) KMA-GCM-AES-128 (GCM-AES128) KMA-GCM-AES-192 (GCM-AES192) KMA-GCM-AES-256 (GCM-AES256) The merge request has also a benchmark that measures the speed of optimized cores on s390x arch. I can't set up gitlab CI for automatic testing on s390x arch because qemu hasn't implemented cipher functions for this arch. However, there is an easy way to test the patch manually by requesting a free account on the LinuxONE Community Cloud, both short-term and long-term access are available. https://linuxone.cloud.marist.edu/#/register?flag=VM regards, Mamone

4 39

[AArch64] Optimize AES with fat build support
by Maamoun TK 30 Jul '21

30 Jul '21

I made a merge request in the main repository that optimizes AES for arm64 architecture with fat build support !34 <https://git.lysator.liu.se/nettle/nettle/-/merge_requests/34>. regards, Mamone

1 0

[S390x] Fat build support for AES and GHASH
by Maamoun TK 24 Jul '21

24 Jul '21

I created a MR !31 <https://git.lysator.liu.se/nettle/nettle/-/merge_requests/31> that adds fat build support of AES and GHASH for S390x architecture. The MR's description has a brief overview of the modifications done to add the fat build support. regards, Mamone

2 6

[S390x] Optimize memxor
by Maamoun TK 22 Jul '21

22 Jul '21

I made a merge request !30 <https://git.lysator.liu.se/nettle/nettle/-/merge_requests/30> that optimizes memxor function for S390x architecture. I've attached a benchmark on a Z15 processor in the MR description. regards, Mamone

1 1

Fwd: [S390x] Optimize GHASH
by Maamoun TK 17 Jul '21

17 Jul '21

---------- Forwarded message --------- From: Maamoun TK <maamoun.tk(a)googlemail.com> Date: Sat, Jul 17, 2021 at 2:00 PM Subject: Re: [S390x] Optimize GHASH To: Niels Möller <nisse(a)lysator.liu.se> On Sat, Jul 17, 2021 at 1:37 PM Niels Möller <nisse(a)lysator.liu.se> wrote: > Maamoun TK <maamoun.tk(a)googlemail.com> writes: > > In another topic, I've optimized the SHA-512 algorithm for arm64 > > architecture but it turned out all CFarm variants don't support SHA-512 > > crypto extension so I can't do any performance or correctness testing for > > now. Do you know any CFarm alternative that supports SHA-512 and SHA3 > > extensions for arm64 architectures? > > Can you do correctness tests on qemu? (I've been using a crosscompiler > and qemu-user to test other ARM code, and that's also what the ci tests > do). > Sure, but I'm also concerned about the performance testing. I was always trying to get the best performance out of hardware-accelerated cores. > I have access to the systems listed on > https://gmplib.org/devel/testsystems, is any of those applicable? The > arm64 machines available includes one Cortex-A73 and one Apple M1. > Cortex-A73 doesn't support SHA-512 and SHA3 List of ARM microarchitectures - Wikipedia <https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures> Cortex-A75 is the minimum architecture that has a full implementation of ARMv8.2-A which is the arch that introduced SHA-512 and SHA3 AArch64 Options (Using the GNU Compiler Collection (GCC)) <https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html> Cortex-A55 should support those extensions according to the list.

1 0

Re: [Aarch64] Optimize AES
by Maamoun TK 17 Jul '21

17 Jul '21

On Sat, Jul 17, 2021 at 1:46 PM Niels Möller <nisse(a)lysator.liu.se> wrote: > Maamoun TK <maamoun.tk(a)googlemail.com> writes: > > > It fits better to have one implementation per key size, I'll modify this > > patch to apply this approach. However, we need to merge the s390x branch > at > > first since it has a separate implementation for each key size. > > Right. With fat support in, is there anything else that is essential > before merging? > No, AES and GHASH have the full functionalities for S390x architecture in this way.

1 0

[S390x] Optimize GHASH
by Maamoun TK 17 Jul '21

17 Jul '21

I made a merge request !26 <https://git.lysator.liu.se/nettle/nettle/-/merge_requests/26> that optimizes the GHASH algorithm for S390x architecture. I've attached a benchmark in the description of merge request that describes the improvement of using GHASH accelerator over C implementation. I've also made two patches for fat build support of AES and GHASH for S390x architecture in addition to optimize memxor function using 'xc (xor storage-to-storage) instruction' Files · s390x-fat · Maamoun TK / nettle · GitLab (liu.se) <https://git.lysator.liu.se/mamonet/nettle/-/tree/s390x-fat> Files · s390x-memxor · Maamoun TK / nettle · GitLab (liu.se) <https://git.lysator.liu.se/mamonet/nettle/-/tree/s390x-memxor> I'll make merge requests for both patches after the current one being merged since they need to rebase on top of that patch. regards, Mamone

3 14

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

nettle-bugs July 2021