Closed
Bug 287153
Opened 19 years ago
Closed 19 years ago
Detect insecure fill-in/submission of SSNs
Categories
(Core :: DOM: Core & HTML, enhancement)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: bugzilla, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 Build Identifier: Warn the user when they type a number into an insecure form which looks like a social security number if not submitting to a TLS/SSL protected site. Rationale: this is another bit of anti-phishing bar-raising, and user protection. If we check submitted values, it's possible that a page author may use JavaScript to scramble the values before submission. So we may want to run the checking code onblur, and warn the user at that point. Very similar to https://bugzilla.mozilla.org/show_bug.cgi?id=287092 Reproducible: Always Steps to Reproduce:
Comment 1•19 years ago
|
||
Is this something you want as part of _Gecko_, or as part of the app? The app can already register as a form submit observer if it wishes.... And certainly Gecko is not going to be running random onblur handlers on everything in sight.
Comment 2•19 years ago
|
||
Even typing your numbers into a dodgy site could be enough to have them captured. You don't need a form submission. The site could send each character to the server as it's typed using XMLHttpRequest. IMO, a better approach is for the browser to have a heuristic-based phishing detector, and if it's suspicious of a site, disable all form controls until the user has followed the procedure to dismiss the yellow bar and enable them. Gerv
Comment 3•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 4•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Updated•5 years ago
|
Component: HTML: Form Submission → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•