From: Ben Boeckel <mathstuf@gmail.com>
To: keyrings@vger.kernel.org
Subject: Re: [PATCH 5/5] dns_key: add a function to verify the key description
Date: Thu, 27 Sep 2018 18:39:51 +0000 [thread overview]
Message-ID: <20180927183951.GC6356@rotor.kitware.com> (raw)
In-Reply-To: <20180927131450.23458-6-mathstuf@gmail.com>
On Thu, Sep 27, 2018 at 18:15:19 +0100, David Howells wrote:
> You can actually vet the description in ->preparse(). ->vet_description() is
> redundant if all key types implement ->preparse().
Would it be better to do so in ->preparse() then? Currently the only
place it is verified (that I can find) is in the userspace
key.dns_resovler.
--Ben
prev parent reply other threads:[~2018-09-27 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 13:14 [PATCH 5/5] dns_key: add a function to verify the key description Ben Boeckel
2018-09-27 17:15 ` David Howells
2018-09-27 18:39 ` Ben Boeckel [this message]
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=20180927183951.GC6356@rotor.kitware.com \
--to=mathstuf@gmail.com \
--cc=keyrings@vger.kernel.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.