From: David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Pavel Shilovsky <piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Grazvydas Ignotas
<notasas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: DNS resolver cache does not expire
Date: Mon, 27 Jun 2011 13:34:13 +0100 [thread overview]
Message-ID: <21187.1309178053@redhat.com> (raw)
In-Reply-To: <BANLkTikbk1yvwWCvhmqdH1DHZN1PPEz+hw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Pavel Shilovsky <piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> It seems that dns_resolver sets expiry timeout to zero here
> (http://lxr.free-electrons.com/source/security/keys/key.c#L310) and
> doesn't change it - so, it always returns cached value.
That's not the DNS resolver you've provided a pointer to - that's where the
key allocator initialises a new key.
> David, can you comment on this problem, please?
It's not much of a problem. Userspace needs to set the key timeout before
instantiating the key:
http://git.kernel.org/?p=linux/kernel/git/dhowells/keyutils.git;a=blob;f=key.dns_resolver.c;h=ab9b87875bcd94dae3083b2711207f87ceea7df1;hb=faabd7c8464502becd01972b1a76ab1dfa1906cc#l502
David
next prev parent reply other threads:[~2011-06-27 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 14:19 DNS resolver cache does not expire Grazvydas Ignotas
[not found] ` <BANLkTim+Phg+cY6_KAhxhfSeDj1td_GALw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-23 19:15 ` Pavel Shilovsky
[not found] ` <BANLkTikbk1yvwWCvhmqdH1DHZN1PPEz+hw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-23 19:48 ` Steve French
2011-06-23 20:14 ` Jeff Layton
2011-06-27 12:34 ` David Howells [this message]
[not found] ` <21187.1309178053-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-06-27 17:27 ` Pavel Shilovsky
[not found] ` <BANLkTikOq_dT1SF9aZ=0DNdoVOngvygfZw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-27 19:42 ` David Howells
[not found] ` <28505.1309203730-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-06-28 9:47 ` Grazvydas Ignotas
[not found] ` <BANLkTinN0pXZsPADfzvO8p+Jf0i3tWtKpw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-28 10:10 ` David Howells
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=21187.1309178053@redhat.com \
--to=dhowells-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=notasas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.