(hmm not really a DNS thing but where else to put it ;)
Hi,
I've noted that on a variety of machines /etc/hosts finally do get
pre-configured with "::1 ip6-localhost", but should this not be "::1
localhost", so that any daemon doing getaddrinfo("localhost",...) and
binding to all the sockets that
[Why not go DNSSEC first instead of solving a problem which is not a
real problem? See below... ]
Gervase Markham wrote:
[..]
> The technology in question, including a version of the list, is about
> to ship in Firefox 3, but we'd like to verify and improve the quality
> of the underlying data.
[three possible solutions below, thus keep on reading ;) ]
Stephane Bortzmeyer wrote:
On Mon, Jun 09, 2008 at 04:53:01PM -0500,
Ted Lemon <[EMAIL PROTECTED]> wrote
a message of 16 lines which said:
Why not just set up a list of TLDs in a mozilla.org subdomain, sign
the subdomain with DNSSE
Gervase Markham wrote:
[..]
Cookies are set for a particular domain or domain suffix, and are sent
to all sites with that domain suffix. So (under the current code)
www.mybank.co.uk can set cookies for either www.mybank.co.uk (shared
with foo.www.mybank.co.uk but not login.mybank.co.uk), mybank.c
Gervase Markham wrote:
Jeroen Massar wrote:
If adserver.co.uk (as they are 'evil') sets a cookie for co.uk then
indeed that cookie gets sent to mybank.co.uk too. What harm does/can
this do? (Except that they might set a cookie identical of type to the
bank one and maybe auto-login to
Livingood, Jason wrote:
>> TLDs, including your own zones. This is indeed not just Site Finder
>> all over again - it's far worse, and breaks far more applications than
>> Site Finder did.
>
> Please do send me that list of applications. I would very much like to
> describe these use cases in th
David Conrad wrote:
> On Jul 16, 2009, at 5:43 AM, Jeroen Massar wrote:
>> Livingood, Jason wrote:
>>> Please do send me that list of applications. I would very much like to
>>> describe these use cases in the next version of the draft.
>>
>> Please list
