ni...@lysator.liu.se (Niels Möller) writes:
> PS. Speaking of work, I'm considering looking for new
> employment/contracting, any advice or suggestions welcome off-list. My
> wish list:
>
> * Primarily foss work.
> * Problems in the intersection of computer science and math.
> * Part time, e.g.,
ni...@lysator.liu.se (Niels Möller) writes:
> I've also noticed that the copyright/authorship section of the manual
> is very out-of-date, so I'm trying to put together a more
> comprehensive AUTHORS file to replace that.
See below. Based on the author info in the manual, ChangeLog, and git
Hi Niels :)
ni...@lysator.liu.se (Niels Möller) writes:
> At some point, we need to stop to make a new release, despite a lot of
> great ongoing work. Opinions on release priorities and any "must haves"
> before a new release are welcome.
OCB is the only mandatory-to-implement AEAD mode in the
Sorry for not being that active last weeks, I've been a bit busy at
work, and I've also been spending probably too many hours following the
war news.
Next things I want to do are: Review pending work, including SM4,
poly1305, HPKE. I've also noticed that the copyright/authorship section
of the
Hi, just a heads up that I'll likely not be very responsive next few
weeks. I may or may not get some hacking time during Christmas holidays.
What I'd like to do when I get time: Review recent patches for powerpc
ecc and sm4. Complete support for ANSI x9.62 (I'm not really up-to-date
on the
Maamoun TK writes:
> I considered to use m4 macros but it "mangles" parameter names, it becomes
> hard for reader to keep track on the macro body. However, I'm still up to
> change it to m4 macros if you like.
The below patch seems to work. It's a drawback that m4 doesn't have
named parameters,
On Thu, Mar 4, 2021 at 10:48 AM Niels Möller wrote:
> And I'd like to change to m4 macros.
>
I considered to use m4 macros but it "mangles" parameter names, it becomes
hard for reader to keep track on the macro body. However, I'm still up to
change it to m4 macros if you like.
> Do you plan
Maamoun TK writes:
>> 1. New Arm64 code (don't recall current status off the top of my head).
>
> I almost forget about fat build, do you want fat support before merging the
> code to the master branch or it's ok to be made afterward?
I've merged the arm64 branch now, thanks! Fat build would be
On Thu, Feb 25, 2021 at 10:14 AM Niels Möller wrote:
> 1. New Arm64 code (don't recall current status off the top of my head).
I almost forget about fat build, do you want fat support before merging the
code to the master branch or it's ok to be made afterward?
2. s390x testing. I'd prefer to
Hi Niels,
On Thu, Feb 25, 2021 at 10:14 AM Niels Möller wrote:
> 1. New Arm64 code (don't recall current status off the top of my head).
>
It has no issue I'm aware of, as long the arm64 code is reviewed, passes
the testsuite, and hits the expected performance it's ok to move forward
and merge
ni...@lysator.liu.se (Niels Möller) writes:
> 4. RSA-OAEP merge request. I intend to attend to (3) first, and will not
>pay much attention to this one at the moment. If anyone else would
>like to help out with review, maybe have alook at this one?
>
I've haven't had much hacking time since the 3.7.1 bug fix rel1ease. I'm
aware of the following recent issues that need review/work:
1. New Arm64 code (don't recall current status off the top of my head).
2. s390x testing. I'd prefer to not run a git checkout on the s390x test
machine, but
Here's a copy of the second status update, which I just submitted to
Internetfonden.
Regards,
/Niels
Nettle project funded by Internetfonden
Status update for February 2013
* Summary
New ECC code integrated in the Nettle repository. The code has been
optimized with respect to both storage
13 matches
Mail list logo
