Re: [whatwg] ... restrict reading value from JS?

2011-07-10 Thread Aryeh Gregor
On Sun, Jul 10, 2011 at 4:08 AM, Alex Vincent wrote: > This is just an idea. > > For the last 10+ years, password inputs have been accessible from scripts, > with nary a complaint.  If I have this code: > >   >     >       >      Show > password! >     >   > > I can extract the password by clickin

Re: [whatwg] ... restrict reading value from JS?

2011-07-10 Thread Dennis Joachimsthaler
Hello, Opera, for example, requires you to hit the "wand" or "login" button before it even does any autocompletion. I wish all browsers would implement it like this instead of just... Filling it out before the user can interact. Makes reading easy. Am 10.07.2011, 21:17 Uhr, schrieb Michal Zal

Re: [whatwg] ... restrict reading value from JS?

2011-07-10 Thread Michal Zalewski
> How about deleting the value if the input type is changed away from the > secure password input type AND that the secure password can only be > submitted to a similar URI. Right now, for interoperability, password managers allow a good amount of fuzziness when matching forms, and I do not believ

Re: [whatwg] ... restrict reading value from JS?

2011-07-10 Thread Dennis Joachimsthaler
How about deleting the value if the input type is changed away from the secure password input type AND that the secure password can only be submitted to a similar URI. Am 10.07.2011, 12:44 Uhr, schrieb Alex Vincent : On Sun, Jul 10, 2011 at 3:21 AM, Michal Zalewski wrote: > For the last 10+

Re: [whatwg] ... restrict reading value from JS?

2011-07-10 Thread Alex Vincent
On Sun, Jul 10, 2011 at 3:21 AM, Michal Zalewski wrote: > > For the last 10+ years, password inputs have been accessible from > scripts, > > with nary a complaint. If I have this code: > > Unfortunately, the problem is not that easy to fix: denying access to > the field does not prevent the attac

Re: [whatwg] ... restrict reading value from JS?

2011-07-10 Thread Michal Zalewski
> For the last 10+ years, password inputs have been accessible from scripts, > with nary a complaint.  If I have this code: Denying access to password fields from JavaScript is actually a somewhat interesting security enhancement when you consider the behavior of password managers. Right now, if y

Re: [whatwg] ... restrict reading value from JS?

2011-07-10 Thread Dennis Joachimsthaler
Hello Alex, may I ask: Why? This would only cover a few cases of cross-site-scripting attacks. It would not make a website more secure. As to the suggestion, I have one little concern: It should not be possible to WRITE those SecurePassword values. You only wrote "reading"... Also it would crip

[whatwg] ... restrict reading value from JS?

2011-07-10 Thread Alex Vincent
This is just an idea. For the last 10+ years, password inputs have been accessible from scripts, with nary a complaint. If I have this code: Show password! I can extract the password by clicking on the button. More to the point, with a XHR I can send that password