Closed Bug 284582 Opened 21 years ago Closed 17 years ago

warning "you are leaving an encrypted page" may be skipped

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Version:
1.7 Branch
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: mozillabug, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de-AT; rv:1.7.2) Gecko/20040906 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; de-AT; rv:1.7.2) Gecko/20040906 when following a link from a https site to a http site that immediately redirects to a https site the warning will be skipped. Two pages to demonstrate: Locate one reachable as https://localhost/index.html, the other as http://localhost/redirect.php (note https/http!) https://localhost/index.html: <html><body> This page is reached via https. Come back here via <a href="http://localhost/redirect.php">http</a> </body></html> http://localhost/redirect.php: <? header( "Status: 302" ); header( "Location: https://localhost/index.html" ); ?> The link usually stating that an encrypted page is left is not displayed. When searching for duplicates I have not found this reported, but some statements, that the warning is merely a user information, especially when no sensitive data is transmitted (a warning will be issued when https-form content is submitted to http). However, as links may contain session ids encoded in urls they may transfer sensitive information unencrypted. This mainly protects misconfigured web applications from their own stupidity, but when the user chooses to be warned the warning should be issued. This has been reproduced with Mozilla 1.7.2 on Linux (german suse supplied version) and vanilla 1.7.5 on Windows. Reproducible: Always Steps to Reproduce: 1. Make above files available on http and https server 2. navigate to https://localhost/index.html 3. click link to http://localhost/redirect.php 4. You'll be immediately redirected back to https://localhost/index.html without a warning that you are leaving an encrypted page Actual Results: warning not issued Expected Results: warning should have been issued
Version: unspecified → 1.7 Branch
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/
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: 20 years ago
Resolution: --- → EXPIRED
If this is still true, it's kinda bad. A redirect through http could go anywhere during a MITM attack, including an attacker-controlled https site. I think most users don't have this warning enabled, but users who chose to enable it should be protected by it.
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
No activity in more than a year. I don't have a local http/https server installed. Is anyone still seeing this bug? If not, please resolve WORKSFORME.
No reply to comment #4 after three weeks -- resolving INCOMPLETE. If you want to REOPEN, please paste the user-agent string (as found after "Build Identifier" at the bottom of the about: page) of a recent build with the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 17 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.