public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: overseers@sources.redhat.com
Subject: Exposing hidden projects to ht://Dig indexing
Date: Sat, 30 Dec 2000 06:08:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.10.10007252051380.16275-100000@dair.pair.com> (raw)

Hopefully you've all figured this out, but I thought better send
a specific heads-up.

Until now, everything that could be reached from links rooted at
http://sources.redhat.com/ was indexed and nothing else.  Soon,
a find+grep-like operation will add all pages with '<meta
name="robots" content="noindex,follow">' tags, as previously
reported.

Meaning, somebody's Secret Project will risk getting exposed
now, if it has its mailing lists in the ordinary place on
sources.redhat.com, i.e. /www/sourceware/ml/ or if it has its
pages at /www/sourceware/htdocs/.  Since even this semi-private
"overseers" list was indexed (perhaps by accident), I will not
take special precautions to "hide" any projects.

The right way to "hide" them from being indexed by ht://Dig (if
so wanted), is to add a matching unique substring to the
exclude_urls attribute in sourceware.conf.  BTW, that file is
managed via CVS, please don't edit in-place.  Send patches for
/sourceware/infra/htdig-conf/sourceware.conf or requests or ask
someone else in the "sourceware" group to fix it.  For example,
an appropriate setting for excluding the overseers mailing list
would be:

exclude_urls:		${site__exclude_urls} /ecos/docs-1.0/ /ecos/docs-1.1/ \
            /ml/overseers/

Just trying to be Extra Cautious so nobody will panic and do
wrong.  But you're all sensible people.

brgds, H-P

WARNING: multiple messages have this Message-ID
From: Hans-Peter Nilsson <hp@bitrange.com>
To: overseers@sources.redhat.com
Subject: Exposing hidden projects to ht://Dig indexing
Date: Tue, 25 Jul 2000 17:58:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.10.10007252051380.16275-100000@dair.pair.com> (raw)
Message-ID: <20000725175800.htZyVe_N9Jw64p_YhiESoYUXtdxUZ_I3_Lv2uYx5yuI@z> (raw)

Hopefully you've all figured this out, but I thought better send
a specific heads-up.

Until now, everything that could be reached from links rooted at
http://sources.redhat.com/ was indexed and nothing else.  Soon,
a find+grep-like operation will add all pages with '<meta
name="robots" content="noindex,follow">' tags, as previously
reported.

Meaning, somebody's Secret Project will risk getting exposed
now, if it has its mailing lists in the ordinary place on
sources.redhat.com, i.e. /www/sourceware/ml/ or if it has its
pages at /www/sourceware/htdocs/.  Since even this semi-private
"overseers" list was indexed (perhaps by accident), I will not
take special precautions to "hide" any projects.

The right way to "hide" them from being indexed by ht://Dig (if
so wanted), is to add a matching unique substring to the
exclude_urls attribute in sourceware.conf.  BTW, that file is
managed via CVS, please don't edit in-place.  Send patches for
/sourceware/infra/htdig-conf/sourceware.conf or requests or ask
someone else in the "sourceware" group to fix it.  For example,
an appropriate setting for excluding the overseers mailing list
would be:

exclude_urls:		${site__exclude_urls} /ecos/docs-1.0/ /ecos/docs-1.1/ \
            /ml/overseers/

Just trying to be Extra Cautious so nobody will panic and do
wrong.  But you're all sensible people.

brgds, H-P

             reply	other threads:[~2000-12-30  6:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Hans-Peter Nilsson [this message]
2000-07-25 17:58 ` Hans-Peter Nilsson
2000-12-30  6:08 ` Chris Faylor
2000-07-25 18:24   ` Chris Faylor
2000-12-30  6:08   ` Jason Molenda
2000-07-25 18:46     ` Jason Molenda
2000-12-30  6:08     ` Chris Faylor
2000-07-25 18:55       ` Chris Faylor
2000-12-30  6:08   ` Hans-Peter Nilsson
2000-07-25 18:43     ` Hans-Peter Nilsson

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=Pine.BSF.4.10.10007252051380.16275-100000@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=overseers@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).