Nicolas Mora writes:
> I've added a merge request to implement AES key wrap and unwrap in
> Nettle [1].
Thanks. Can you give a bit more details on the usecase? I've understood
that it's part of web-related specs, but do you know any examples of
protocols or applicatinos using it, and how?
I've
ni...@lysator.liu.se (Niels Möller) writes:
> So to be concrete on the interface comments, I'd suggest something like
>
> void
> nist_keywrap16(const void *ctx, nettle_cipher_func *encrypt,
>const uint8_t *iv, size_t ciphertext_length,
>uint8_t *ciphertext, cosnt
Maamoun TK writes:
> Debian.remote.s390x:
> image: $CI_REGISTRY/$BUILD_IMAGES_PROJECT:$DEBIAN_BUILD
> before_script:
> - apt-get update -qq
> - apt-get install -qq git
> - 'which ssh-agent || ( apt-get install -qq openssh-client )'
> - eval $(ssh-agent -s)
> - ssh-add <(echo "$SSH_P
David Edelsohn writes:
> Thanks for setting this up. The default accounts have a limited time
> (90 days?). For long-term CI access, I can help request a long-term
> account for Nettle.
That would be helpful.
I've had look at the terms and conditions,
http://security.marist.edu/LinuxOne/TC.P
On Wed, Feb 3, 2021 at 11:13 AM Niels Möller wrote:
> ...
> I've had look at the terms and conditions,
> http://security.marist.edu/LinuxOne/TC.PDF. Most of it looks very
> reasonable, but there are a few items that I find a bit unclear:
>
> 9. [...] You agree to obey all relevant New York State
On Wed, Feb 3, 2021 at 11:13 AM Niels Möller wrote:
>
> David Edelsohn writes:
>
> > Thanks for setting this up. The default accounts have a limited time
> > (90 days?). For long-term CI access, I can help request a long-term
> > account for Nettle.
>
> That would be helpful.
>
> I've had look
Hello Niels,
Thanks for your feedback!
Le 2021-02-03 à 03 h 47, Niels Möller a écrit :
Thanks. Can you give a bit more details on the usecase? I've understood
that it's part of web-related specs, but do you know any examples of
protocols or applicatinos using it, and how?
The AES Key Wrap is
Nicolas Mora writes:
> It was designed to wrap key data, but not necessarily AES only. The
> kek must be an AES key though. The key data to wrap can be any data,
> as long as it's a set of 64 bits blocks.
If it doesn't add a lot of complexity, I think it would be nice to be
able to substitute at
