linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stéphane Aulery" <saulery-GANU6spQydw@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: 773443-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Bug#773443: host.conf.5: spoof deprecated ?
Date: Tue, 10 Mar 2015 00:26:28 +0100	[thread overview]
Message-ID: <20150309232628.GA17006@free.fr> (raw)
In-Reply-To: <54FD61CD.2060900-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Hello Michael,

Le lundi 09 mars 2015 à 10:03:09, Michael Kerrisk (man-pages) a écrit :
> On 03/09/2015 08:59 AM, Stéphane Aulery wrote:
> > Le lundi 09 mars 2015 à 08:22:01, Michael Kerrisk (man-pages) a écrit :
> >>
> >> On 03/08/2015 02:05 PM, Stéphane Aulery wrote:
> >>>
> >>> A Debian user reported that [1]:
> >>>
> >>>> spoof* keywords (nospoof, spoofalert, spoof) are here from 1996,
> >>>> they are still valid keywords but do not have any effect apparently,
> >>>> no libraries or tools use them
> >>>>
> >>>> it is misleading to see references to resolv+ and rlogin, the keywords
> >>>> are just ignored these days; the only meaning they have is that they
> >>>> are
> >>>> allowed by host.conf syntax
> >>>
> >>> The glibc source code seems to confirm that the keywords nospoof,
> >>> spoofalert and spoof are accepted but without effects. I could find
> >>> nothing in the changelog. Could you please confirm that they are
> >>> obsolete? I could correct the man page accordingly.
> >>
> >> I had a quick grep in the glibc source code.
> >>
> >> It appears that you (and the reporter) are correct. (Even back in 
> >> glibc 2.1, things look the same).
> >>
> >> A patch would be appreciated!

I dug a little further comparing versions 2.0.6 [1], 2.0.7 [2]
and trunk [3] of glibc and I come to a different conclusion.

The keywords nospoof, spoofalert, spoof and RESOLV_SPOOF_CHECK were
added to glibc 2.0.7 but never implemented and documented in the
changelog.

[1] http://ftp.gnu.org/gnu/glibc/glibc-2.0.6.tar.gz
[2] http://archive.debian.org/debian/dists/hamm/main/source/libs/glibc_2.0.7t.orig.tar.gz
[3] https://sourceware.org/git/?p=glibc.git&a=search&h=HEAD&st=grep&s=spoof&sr=1

Regards,

-- 
Stéphane Aulery
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-03-09 23:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08 13:05 host.conf.5: spoof deprecated ? Stéphane Aulery
     [not found] ` <20150308130510.GA3004-GANU6spQydw@public.gmane.org>
2015-03-09  7:22   ` Bug#773443: " Michael Kerrisk (man-pages)
     [not found]     ` <54FD4A19.2030203-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-09  7:59       ` Stéphane Aulery
     [not found]         ` <20150309075913.GA1341-GANU6spQydw@public.gmane.org>
2015-03-09  9:03           ` Michael Kerrisk (man-pages)
     [not found]             ` <54FD61CD.2060900-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-09 23:26               ` Stéphane Aulery [this message]
     [not found]                 ` <20150309232628.GA17006-GANU6spQydw@public.gmane.org>
2015-03-09 23:27                   ` [PATCH] host.conf.5: keywords and env. var. nospoof, spoofalert, spoof and RESOLV_SPOOF_CHECK were added to glibc 2.0.7 but never implemented Stéphane Aulery
     [not found]                     ` <1425943648-17928-1-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-10  6:20                       ` Bug#773443: " Michael Kerrisk (man-pages)
     [not found]                         ` <54FE8D43.4070306-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-10  7:28                           ` Stéphane Aulery
2015-03-10  6:00                   ` Bug#773443: host.conf.5: spoof deprecated ? Michael Kerrisk (man-pages)

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=20150309232628.GA17006@free.fr \
    --to=saulery-ganu6spqydw@public.gmane.org \
    --cc=773443-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).