On Thu, May 6, 2010 at 8:44 AM, wrote:
Good observations Frank & Ash & Aryeh & others,
I see a few shortcomings in this approach:
a) each document is encrypted asymmetrically, affecting performance.
1) yes, that's partially true. What is asymmetrically encrypted is
the keys to symmetrical
On Fri, 2010-05-07 at 16:40 -0400, Aryeh Gregor wrote:
> On Fri, May 7, 2010 at 4:21 PM, Tab Atkins Jr. wrote:
> > On Fri, May 7, 2010 at 10:06 AM, Juuso Hukkanen
> > wrote:
> >> 1) Man-in-the-middle problem; which doesn't exists because
> >>a) those are just academic mind games
> >
> >
On Fri, May 7, 2010 at 4:21 PM, Tab Atkins Jr. wrote:
> On Fri, May 7, 2010 at 10:06 AM, Juuso Hukkanen
> wrote:
>> 1) Man-in-the-middle problem; which doesn't exists because
>> a) those are just academic mind games
>
> You don't get to talk about security anymore.
I don't think "academi
On Fri, 2010-05-07 at 13:21 -0700, Tab Atkins Jr. wrote:
> On Fri, May 7, 2010 at 10:06 AM, Juuso Hukkanen
> wrote:
> > 1) Man-in-the-middle problem; which doesn't exists because
> >a) those are just academic mind games
>
> You don't get to talk about security anymore.
>
> ~TJ
+1
Yo
On May 6, 2010, at 11:14 AM, Edward O'Connor wrote:
>
> Consider how the above would work in legacy browsers, and then consider
> how this would work in them:
>
> As Ashley Crandall Amos says in href="http://example.com/books/crandall/linguisticmeans";>Linguistic Means of
> Determining the Date
On Fri, May 7, 2010 at 10:06 AM, Juuso Hukkanen wrote:
> 1) Man-in-the-middle problem; which doesn't exists because
> a) those are just academic mind games
You don't get to talk about security anymore.
~TJ
On Fri, May 7, 2010 at 1:06 PM, Juuso Hukkanen wrote:
> You asked many questions, and unfortunately all you missed the
> auth="verisign" argument, which _is_ enough to prevent all practical (,even
> if they are all theoretical!,) man-in-the-middle attacks.
You haven't explained what it does. Did
On Fri, May 7, 2010 at 11:26 AM, Schalk Neethling
wrote:
> Hey TJ, I understand what type=date is supposed to offer the user and agree
> that using Modernizr to detect whether the element is supported and provide a
> fallback but my more direct question is, would HTML 5 offer the ability to
> a
On Thu, May 6, 2010 at 2:19 PM, Schalk Neethling
wrote:
> Greetings,
>
> Are there any talks at the moment whether the type=date input will allow a
> user to enter a date manually or use the date picker or, should developers
> fall back to using a standard input field and add the date picker vi
On Fri, 2010-05-07 at 17:06 +, Juuso Hukkanen wrote:
> answer 1:
> Most servers are already configured to read the requested pages
> before
> submitting those over the internet.
What do you base this on? I can't say I've ever seen a server set up to
parse HTML content
> For example my abov
I was expecting criticism; as is unavoidable with all crypto issues.
You asked many questions, and unfortunately all you missed the
auth="verisign" argument, which _is_ enough to prevent all practical
(,even if they are all theoretical!,) man-in-the-middle attacks.
passsalt="colordev.co
On Thu, May 6, 2010 at 8:44 AM, wrote:
> passsalt="no|domainname" auth="verisign">
>
I see a few shortcomings in this approach:
a) each document is encrypted asymmetrically, affecting performance.
b) there is no management of keys (expiration, revocation, trust, etc).
c) the values for the pubt
establish a WebSocket connection
[[
41. ...
If the entry's name is "set-cookie" or "set-cookie2" or another
cookie-related field name
If the relevant specification is supported by the user agent, handle the
cookie as defined by the appropriate specification, with the resource
being the one
Am 07.05.2010 00:30 schrieb Schalk Neethling:
Just to rectify any misunderstanding, I love the date picker that Opera
provides and others will hopefully do in turn but, my question is that
currently using type=date only provides the option of selecting a date using
the date picker. In a recent
I think using the role attribute is the best solution here:
This way we're using the type attribute to indicate what sort of data
is being entered, and the role attribute to indicate how it will be
used. I think the separation of these is sensible, although it's not
entirely consistent across t
establish a WebSocket connection
[[
28. Read bytes from the server until either the connection closes, or a
0x0A byte is read. Let field be these bytes, including the 0x0A byte.
If field is not at least seven bytes long, or if the last two bytes aren't
0x0D and 0x0A respectively, or if it d
On Fri, May 7, 2010 at 5:58 AM, Garrett Smith wrote:
> | # a date-fullyear is defined as four or more digits
> | representing a number greater than 0
>
> I read that as "" to "". Is there a different interpretation of that?
Surely is not greater than 0?
On Thu, 06 May 2010 23:36:00 +0100, Tab Atkins Jr.
wrote:
My suggestion was to fall back to using a standard text input field and
use JavaScript to add the date picker which will allow the user to
enter the date manually if so desired. Are there any current plans to
add this ability to t
18 matches
Mail list logo
