All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Cryptography
Date: Mon, 16 Nov 2009 19:26:47 +0100	[thread overview]
Message-ID: <20091116182647.GA30919@thorin> (raw)
In-Reply-To: <4B01681A.9070302@gmail.com>

On Mon, Nov 16, 2009 at 03:56:26PM +0100, Vladimir 'phcoder' Serbinenko wrote:
> 2) Adaptation to the lack of gnulib abstraction layer on top of gcrypt

It seems that the usual way of importing gc-pbkdf2-sha1.c is by linking it
with gc-gnulib.c or gc-libgcrypt.c.  Is this option problematic?

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-11-16 18:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 13:48 [PATCH] Cryptography Vladimir 'phcoder' Serbinenko
2009-11-16 14:35 ` Robert Millan
2009-11-16 14:56   ` Vladimir 'phcoder' Serbinenko
2009-11-16 18:26     ` Robert Millan [this message]
2009-11-16 19:38       ` Vladimir 'phcoder' Serbinenko
2009-11-16 19:59         ` Robert Millan
2009-11-16 20:20           ` Vladimir 'phcoder' Serbinenko
2009-11-16 21:16             ` Import of libgcrypt 1.4.4 ciphers (was: Re: [PATCH] Cryptography) Robert Millan
2009-11-16 14:42 ` [PATCH] Cryptography Felix Zielcke
2009-11-16 14:58   ` Vladimir 'phcoder' Serbinenko
2009-11-17 12:21 ` Robert Millan
2009-11-17 12:56   ` Robert Millan
2009-12-05 15:44     ` Vladimir 'φ-coder/phcoder' Serbinenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091116182647.GA30919@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.