- Original Message -
From: "Mark Delany" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, July 25, 2006 1:37 AM
Subject: Re: [ietf-dkim] Eat all CR/LF - STRIP Canonicalization Method
> This is a replay issue:
>
> o I get a verified email from paypal that has MIME attachments.
> o I strip out the C
On Mon, 2006-07-24 at 22:27 -0700, Patrick Peterson wrote:
> > http://www.ietf.org/internet-drafts/draft-hallambaker-pcon-00.txt
>
> I think this is a great idea and am surprised it didn't generate more
> traffic on the list. It's not easy to cram needed new functionality into
> a backward-compat
- Original Message -
From: "Mark Delany" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, July 25, 2006 1:37 AM
Subject: Re: [ietf-dkim] Eat all CR/LF - STRIP Canonicalization Method
> Right. But a bad guy can modify the original content and it will still
> verify with STRIP.
I missed this subtl
Patrick Peterson wrote:
- Original Message -
From: "Hallam-Baker, Phillip" <[EMAIL PROTECTED]>
To: "IETF-DKIM"
Sent: Wednesday, July 12, 2006 2:05 PM
Subject: [ietf-dkim] The URL to my paper describing the DKIM
policy options
I submitted the draft in both pdf and txt. Only the txt i
Hi Hector,
Hector Santos wrote:
Look, I can't help but think if it was anyone else making this suggestion,
you wouldn't be able to kept up with this thread.What a shame, it is
more important to push out a faulty spec than to fix the problem to make
DKIM more robust and acceptable.
I don'
CC'd to namedroppers for wider discussion.
There are two wildcard problems
1) Wildcards do not match a node if there is any data at the node
*.example.com TXT "hello" will not match if there is any record at
a.example.com
2) It is not possible to define a midpoint wildcard
_pr
Thanks Stephen, I will take your suggestions stated under advisement.
--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com
- Original Message -
From: "Stephen Farrell" <[EMAIL PROTECTED]>
To: "Hector Santos" <[EMAIL PROTECTED]>
Cc:
Sent: Tuesday, July 25, 2006 12:04 PM
Phill's hack is indeed clever, but it seems to me egregiously
premature to propose a standard way to retrieve reputation data that
doesn't actually exist yet. We could equally well come up with a rule
to map the selector to a URL which would work just as well albeit not
as fast, again to retrieve
John,
You are mistake, the point is to retrieve policy data, not reputation data. In
point of fact I have already proposed the use of a URL pointer as a means to
publish reputation data. This is how secure letterhead works.
We already have policy data, and at the moment we have a heuristic hack
> From: Douglas Otis [mailto:[EMAIL PROTECTED]
> On Mon, 2006-07-24 at 22:27 -0700, Patrick Peterson wrote:
>
> > > http://www.ietf.org/internet-drafts/draft-hallambaker-pcon-00.txt
> >
> > I think this is a great idea and am surprised it didn't
> generate more
> > traffic on the list. It's n
On Jul 25, 2006, at 5:33 PM, Hallam-Baker, Phillip wrote:
The intent was to point to a general label where policy references
are found. Philip suggested this should point to an HTTP server.
HTTP is needed to support the size of an all encompassing policy
response.
No I did not make tha
> From: Douglas Otis [mailto:[EMAIL PROTECTED]
> Of course, a script or complaint DNS server generates the
> added wildcard records, but this may create issues related to
> revealing nodes within a domain.
There is no additional disclosure since even with NSEC3 there is always a means
of d
12 matches
Mail list logo
