Hi :)
Niels Möller writes:
> http://www.lysator.liu.se/~nisse/archive/nettle-3.10rc2.tar.gz
> http://www.lysator.liu.se/~nisse/archive/nettle-3.10rc2.tar.gz.sig
FWIW, I tested these on AMD64 and Arm64 using our Rust bindings for
Nettle, and the sequoia-openpgp test suite. I discovered no p
Niels Möller writes:
>>> * Focus on getting post-quantum algorithms into Nettle.
>>
>> From GnuTLS perspective, it would be helpful if there is support for at
>> least one post-quantum KEM algorithm so it could make TLS handshake
>> provide quantum safety and forward secrecy (with PSK). Signatur
Hi Niels :)
Niels Möller writes:
> While looking at extended tests of the aead update function (for the
> associated data), I stumbled on a restriction of gcm_update that is
> different from most (all?) other update functions in Nettle. According
> to the docs,
>
> -- Function: void gcm_update
Hi,
https://lists.lysator.liu.se/mailman/hyperkitty/list/nettle-bugs@lists.lysator.liu.se/
shows zero mails this year. Not sure where to raise that, so I'm
raising this here.
Best,
Justus
signature.asc
Description: PGP signature
___
nettle-bugs mail
Hello :)
I'd like to share some algorithms that we'll need for the next revision
of OpenPGP and the upcoming PQC algorithms for OpenPGP, just to give you
an early heads up because I know that implementing these things
correctly takes a lot of time and effort, and we don't have the
expertise to con
Niels Möller writes:
>> We have quite a few
>> tests: we instantiate it with every compatible cipher and do a roundtrip
>> test, we have the test vectors from RFC7253, we have an additional set
>> of test vectors with 15 byte nonces published by dkg,
>
> Do you have any testvectors with a dozen
Hi Niels :)
Niels Möller writes:
> * Support for OCB authenticated encryption mode.
Most appreciated! I read the documentation and found only two minor
issues (patches sent). The interface looks good.
I have added support for OCB in our Rust bindings on 2022-02-03 in a
feature branch.
Hi Niels :)
"Niels Möller" writes:
> I've now merged OCB support to the master branch. Some changes from the
> development branch:
Sweet! I can confirm that it performs as expected on our test vectors.
> * I moved the corresponding nettle_aead struct to an internal header for
> now. Used fo
Hi Niels :)
ni...@lysator.liu.se (Niels Möller) writes:
> Hi, when working on OCB, and trying to have some consistency between
> similar functions, I'm looking at the various "all-in-one"
> *_message_encrypt and *_message_decrypt functions. They are motivated in
> part by convenience, for applica
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 u
ni...@lysator.liu.se (Niels Möller) writes:
> Justus Winter writes:
>
>>> I've given it a try, see branch ocb-mode. Based on RFC 7253. Passes
>>> tests, but not particularly optimized.
>>
>> I have wrapped it in our Rust bindings, glued Sequoia to it, an
Hello Niels :)
sorry for not following up earlier. Thanks for working on it!
ni...@lysator.liu.se (Niels Möller) writes:
> ni...@lysator.liu.se (Niels Möller) writes:
>
>> If someone wants to work on it, please post to the list. I might look
>> into it myself, but as you have noticed, I have ra
Hello,
we (Sequoia PGP) would love to see OCB being implemented in Nettle. The
OpenPGP working group is working on a revision of RFC4880, which will
mostly be a cryptographic refresh, and will bring AEAD to OpenPGP.
The previous -now abandoned- draft called for EAX being mandatory, and
OCB being
"Neal H. Walfield" writes:
> I'm not that familiar with Nettle's API, so I don't know if the
> following is sufficiently idiomatic.
>
> That said, we could do the following: we could add a flag to the sha1
> context to indicate to the update function that it should try to
> detect collision attem
ni...@lysator.liu.se (Niels Möller) writes:
> Justus Winter writes:
>
>> Do we need to do anything else to be listed on
>> https://www.lysator.liu.se/~nisse/nettle/ ?
>
> If you want to make it really easy for me, please send a patch, the file
> on the web should be
Justus Winter writes:
>> Regarding the Rust bindings, what's the best place to point other Rust
>> users? https://crates.io/crates/nettle, or
>> https://sequoia-pgp.gitlab.io/nettle-rs/nettle/, or somewhere else?
>
> https://crates.io/crates/nettle is the preferre
ni...@lysator.liu.se (Niels Möller) writes:
> Justus Winter writes:
>
>> I read the reference, and I don't see how it applies here.
>
> Right, it's a bit different.
>
>> For the
>> record, this is the build failure that I'm referring to:
>>
&
ni...@lysator.liu.se (Niels Möller) writes:
> Have you looked at nettle's pgp.h?
No.
> This code is not really in a useful state. It aims to be able to write
> out a public RSA key in openpgp format, and doesn't quite succeed at
> that.
Well, a key packet on its own is not useful, you also need
ni...@lysator.liu.se (Niels Möller) writes:
> Justus Winter writes:
>
>> just a small bug report, there are some .stamp files that got included
>> in the release by accident. I noticed because it caused build problems,
>> likely only due to the fact that my build proce
Hi :)
just a small bug report, there are some .stamp files that got included
in the release by accident. I noticed because it caused build problems,
likely only due to the fact that my build process copied the files once,
changing the mtimes in the process.
% tar tf nettle-3.5.1.tar.gz | gre
Hello :)
I just wanted to say hi, and announce the availability of bindings for
the Rust programming language.
As it is idiomatic for bindings to foreign code, there are two packages.
First, there is the almost completely autogenerated crate (crate is
Rust-lingo for library) 'nettle-sys', which
21 matches
Mail list logo
