Closed Bug 286810 Opened 20 years ago Closed 20 years ago

(MASv1.8b2-xx) In BugZilla.m.o, clicking on Edit on any attachment shows encrypted+unencrypted content warning

Categories

(SeaMonkey :: Security, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
seamonkey1.0alpha

People

(Reporter: sgautherie, Assigned: jst)

References

Details

(Keywords: regression)

This regressed between
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b) Gecko/20050217] (release) (W98SE)
and
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b2) Gecko/20050312] (nightly) (W98SE)
and is still there in
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b2) Gecko/20050317] (nightly) (W98SE)
I believe /20050223 worked fine too !?
Flags: blocking1.8b2?
Target Milestone: --- → mozilla1.8beta2
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b2) Gecko/20050310

One day regression timeframe:

BuildId 2005030906 working, no warning
BuildId 2005031005 failing, warning

checkins:
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=SeaMonkeyAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-03-09+03%3A00&maxdate=2005-03-10+07%3A00&cvsroot=%2Fcvsroot
From bug 284993 perhaps?
Definitely caused by the patch for bug 284993, the problem goes away when I back
that out in my tree. Now must test 1.7.6 to make sure this isn't there, too.
Assignee: dveditz → jst
Blocks: lockicon
Depends on: 284993
Flags: blocking-seamonkey1.0a?
With Mozilla 1.7.6 I see this warning all the time if I access a b.m.o bug
report (not only for edit an attachment).
Target Milestone: mozilla1.8beta2 → ---
Target Milestone: --- → Seamonkey1.0alpha
For some reason I cannot duplicate this.  Can someone who is experiencing this
issue see if it still fails with the 20050330 nightly?  It is possible this was
fixed by the check-in for bug 285738.
(In reply to comment #6)
> For some reason I cannot duplicate this.  Can someone who is experiencing this
> issue see if it still fails with the 20050330 nightly?  It is possible thi
s was
> fixed by the check-in for bug 285738.


I´ve seen this bug in comment 2, I can't see it using BuildID 2005032905,
so the check-in for bug 285738 at 2005-03-29 20:22 didn´t change it.
Can´t test with BuildId 2005033007, as I deleted it because of Bug 288406.

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b2) Gecko/20050329
(In reply to comment #7)
> I´ve seen this bug in comment 2, I can't see it using BuildID 2005032905,

Sorry, fully wrong. I forgot that I´ve disabled some of the SSL-Warnings,
I`m still seeing that bug if all SSL-Warnings are enabled, using BuildId 2005032905.
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b2) Gecko/20050329
(In reply to comment #8)

> Sorry, fully wrong. I forgot that I´ve disabled some of the SSL-Warnings,
> I`m still seeing that bug if all SSL-Warnings are enabled, using BuildId
2005032905.
> Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b2) Gecko/20050329
> 

Well now I feel dumb too!  That is exaclty why I could not duplicate it.  After
re-enabling the warning I was able to duplicate the issue with a build from
before the checkin and verify that I was unable to duplicate it with the
20050331 nightly.  I am resoving this as fixed by the checkin for bug 285738.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b2) Gecko/20050401] (nightly) (W98SE)

Verified F. :-)
Status: RESOLVED → VERIFIED
Depends on: 285738
No longer depends on: 284993
Flags: blocking-seamonkey1.0a?
You need to log in before you can comment on or make changes to this bug.