https://blog.seamonkey-project.org/2024/03/28/seamonkey-2-53-18-2-is-out/
--
"Where, then, is boasting? It is excluded. On what principle? On that of observing the law? No, but on that of faith. For we maintain that a man is justified by faith apart from observing the law." --Romans 3:27-28. Right leg hurts again after sleeping overnight. :(
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:
> https://blog.seamonkey-project.org/2024/03/28/seamonkey-2-53-18-2-is-out/
>

I remember when it was possible to look at the Bugzilla entries without
having an account with them, and even more annoying is that it does not
appear to be possible to create a bugzilla.mozilla.org account using
Seamonkey. Just one more annoyance arising from Mozilla.org.

On 28/03/2024 10:20, R Daneel Olivaw wrote:
> Ant wrote:
>> https://blog.seamonkey-project.org/2024/03/28/seamonkey-2-53-18-2-is-out/
>
> I remember when it was possible to look at the Bugzilla entries without
> having an account with them, and even more annoying is that it does not
> appear to be possible to create a bugzilla.mozilla.org account using
> Seamonkey.  Just one more annoyance arising from Mozilla.org.

Maybe disable JS for Bugzilla, at least for browsing ?

/df

--
London
UK

On 28/03/2024 11:33, Dirk Fieldhouse wrote:
> ...>
> Maybe disable JS for Bugzilla, at least for browsing ?

No, it's that exploitable bugs are protected. I hope that the protection
is removed once the bug can't be exploited and this from
<https://blog.mozilla.org/security/2015/09/04/improving-security-for-bugzilla/>
seems to confirm that, at least 9 years ago:
> ... we publish security bugs once they’re no longer dangerous ,,,

/df
--
London
UK

No account needed for viewing bugs:

https://bugzilla.mozilla.org/show_bug.cgi?id=1885418

https://bugzilla.mozilla.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&chfieldfrom=2018-01-01&chfieldto=Now&f1=component&list_id=15949575&o1=notequals&product=SeaMonkey&query_format=advanced&resolution=---&v1=Web%20Compatibility&order=changeddate%20DESC%2Cpriority%2Cbug_severity&query_based_on=

R Daneel Olivaw wrote:
> Ant wrote:
>> https://blog.seamonkey-project.org/2024/03/28/seamonkey-2-53-18-2-is-out/
>>
>
> I remember when it was possible to look at the Bugzilla entries without having
> an account with them, and even more annoying is that it does not appear to be
> possible to create a bugzilla.mozilla.org account using Seamonkey.  Just one
> more annoyance arising from Mozilla.org.

On 3/27/2024 10:33 PM, Ant wrote:
> https://blog.seamonkey-project.org/2024/03/28/seamonkey-2-53-18-2-is-out/
>

Not yet listed at <https://archive.seamonkey-project.org/releases/>.

--
David E. Ross
<http://www.rossde.com/>

Demonstrators worldwide are demanding that Israel stop
fighting in Gaza. Why does it seem that no one is demanding
that Hamas stop fighting? And where are the demonstrations
against Russia fighting in the Ukraine.

frg wrote:
> No account needed for viewing bugs:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1885418
>
> https://bugzilla.mozilla.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&chfieldfrom=2018-01-01&chfieldto=Now&f1=component&list_id=15949575&o1=notequals&product=SeaMonkey&query_format=advanced&resolution=---&v1=Web%20Compatibility&order=changeddate%20DESC%2Cpriority%2Cbug_severity&query_based_on=
>
>
> R Daneel Olivaw wrote:
>> Ant wrote:
>>> https://blog.seamonkey-project.org/2024/03/28/seamonkey-2-53-18-2-is-out/
>>>
>>>
>>
>> I remember when it was possible to look at the Bugzilla entries
>> without having an account with them, and even more annoying is that it
>> does not appear to be possible to create a bugzilla.mozilla.org
>> account using Seamonkey.  Just one more annoyance arising from
>> Mozilla.org.
>

ok, looking at
https://www.seamonkey-project.org/releases/seamonkey2.53.18.2/ and
"What's New in SeaMonkey 2.53.18.2", access to the first four bugs is
blocked but access to the other three is permitted.

Dirk Fieldhouse wrote:
> On 28/03/2024 11:33, Dirk Fieldhouse wrote:
>> ...>
>> Maybe disable JS for Bugzilla, at least for browsing ?
>
> No, it's that exploitable bugs are protected. I hope that the protection
> is removed once the bug can't be exploited and this from
> <https://blog.mozilla.org/security/2015/09/04/improving-security-for-bugzilla/>
> seems to confirm that, at least 9 years ago:
>> ... we publish security bugs once they’re no longer dangerous ,,,
>
>
> /df
>

Yes, disabling JS made no difference.
As I wrote to Frank below, access to the first four bugs in
https://www.seamonkey-project.org/releases/seamonkey2.53.18.2/ - "What's
New in SeaMonkey 2.53.18.2" is blocked, access to the other three is
permitted.

R Daneel Olivaw wrote:
> Dirk Fieldhouse wrote:
>> On 28/03/2024 11:33, Dirk Fieldhouse wrote:
>>> ...>
>>> Maybe disable JS for Bugzilla, at least for browsing ?
>>
>> No, it's that exploitable bugs are protected. I hope that the protection
>> is removed once the bug can't be exploited and this from
>> <https://blog.mozilla.org/security/2015/09/04/improving-security-for-bugzilla/>
>>
>> seems to confirm that, at least 9 years ago:
>>> ... we publish security bugs once they’re no longer dangerous ,,,
>>
>>
>> /df
>>
>
> Yes, disabling JS made no difference.
> As I wrote to Frank below, access to the first four bugs in
> https://www.seamonkey-project.org/releases/seamonkey2.53.18.2/ - "What's
> New in SeaMonkey 2.53.18.2" is blocked, access to the other three is
> permitted.

Logging in doesn't help for regular users, message changes to something
like, "You are not authorized to access bug 1881093." Which is normal
for security bugs
Dave