Re: Basic Authentication issue in 2.46

[Gerry Hickman via support-seamonkey]

Paul in Houston, TX wrote:


Is it possible to disable the 'Upgrade-Insecure-Requests' header in
SeaMonkey?


Any references to Insecure in about:config?


I found these four, tried toggling the first, but no luck...

network.websocket.allowInsecureFromHTTPS
security.tls.insecure_fallback_hosts
security.warn_submit_insecure
services.sync.prefs.sync.security.warn_submit_insecure

--
Gerry Hickman (London UK)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Basic Authentication issue in 2.46

[David C. Mores via support-seamonkey]

Gerry Hickman wrote:

I have a SiteCom router with an embedded web server. For many years I
was able to log in from SeaMonkey by typing http://10.0.0.1/ and then
the user name and password. This still works in older versions of SM and
FF, but not in SM 2.46

I believe the issue is related to a new HTTP header being sent by SM 2.46

Upgrade-Insecure-Requests: 1

I set up a raw HTTP test on a linux VM (without using a browser) and
tested both with and without this header.

Request with header : Authentication FAILS
Request without header : Authentication WORKS

It's quite strange, as I don't see how the router can even know about
this header as it's too old. I also noticed something even more odd, if
I change the header to something like

BlahBlahBalh: 1

the authentication also fails, but if I use

BlahBlahBalh: one

everything starts working

Is it possible to disable the 'Upgrade-Insecure-Requests' header in
SeaMonkey?



I found this same behavior with my Linksys/Cisco WRT120N home router 
that I bought in 2010.  Since SeaMonkey is based pretty much on Firefox 
code, I checked it there with the same result.  So I decided to file a 
bug report on Firefox because any fix there would/should migrate to the 
SeaMonkey code.


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

The Comment story started 4 months ago and has recently concluded that 
my router is the bad boy.  It has been at end-of-life status according 
to Linksys/Cisco for about 6 years.  The only workaround I have is, as 
you have found, to use the older version of SM, or another browser such 
as Google Chrome, MS Edge or Pale Moon - that apparently do not (yet) 
send the Upgrade-Insecure-Header in the request.


This header mechanism is legitimate W3C:
https://w3c.github.io/webappsec-upgrade-insecure-requests/
I looks like we got to learn to live with it.

How old is your SiteCom router?  Have you looked into available firmware 
upgrades for it?

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Basic Authentication issue in 2.46

[Paul in Houston, TX]

Gerry Hickman wrote:

I have a SiteCom router with an embedded web server. For many years I was able 
to log in
from SeaMonkey by typing http://10.0.0.1/ and then the user name and password. 
This still
works in older versions of SM and FF, but not in SM 2.46

I believe the issue is related to a new HTTP header being sent by SM 2.46

Upgrade-Insecure-Requests: 1

I set up a raw HTTP test on a linux VM (without using a browser) and tested 
both with and
without this header.

Request with header : Authentication FAILS
Request without header : Authentication WORKS

It's quite strange, as I don't see how the router can even know about this 
header as it's
too old. I also noticed something even more odd, if I change the header to 
something like

BlahBlahBalh: 1

the authentication also fails, but if I use

BlahBlahBalh: one

everything starts working

Is it possible to disable the 'Upgrade-Insecure-Requests' header in SeaMonkey?


Any references to Insecure in about:config?


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Strange 403 Forbidden error

[Eric]

Dirk Munk wrote:

I was trying to reach the following website:

http://www.scanmaker.com

and I got a 403 Forbidden error.

Chrome shows no problem and I can view the website, very strange.



This is my setup:

Windows 10 64 bit, completely updated to the latest patches.

Seamonkey 2.50, 64 bit

Build identifier: 20170424091539

User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101
Firefox/52.0 Lightning/5.4

IPv6 connection to website, using Hurricane Electric tunnel.



What can cause this problem?



I was getting this problem a lot recently, come to find out it was my 
Anti-virus, which had a built in page blocker for suspect pages.


I had to go in to the Anti-virus and white-list the website.  Very 
complicated process and different for each anti-virus program.


From viewing other posts, it looks like this page no longer is available.

Hope this helps for future issues like this.

Eric
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Basic Authentication issue in 2.46

[Gerry Hickman via support-seamonkey]

I have a SiteCom router with an embedded web server. For many years I 
was able to log in from SeaMonkey by typing http://10.0.0.1/ and then 
the user name and password. This still works in older versions of SM and 
FF, but not in SM 2.46


I believe the issue is related to a new HTTP header being sent by SM 2.46

Upgrade-Insecure-Requests: 1

I set up a raw HTTP test on a linux VM (without using a browser) and 
tested both with and without this header.


Request with header : Authentication FAILS
Request without header : Authentication WORKS

It's quite strange, as I don't see how the router can even know about 
this header as it's too old. I also noticed something even more odd, if 
I change the header to something like


BlahBlahBalh: 1

the authentication also fails, but if I use

BlahBlahBalh: one

everything starts working

Is it possible to disable the 'Upgrade-Insecure-Requests' header in 
SeaMonkey?


--
Gerry Hickman (London UK)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: support-seamonkey Digest, Vol 137, Issue 11

[Paul B. Gallagher]

shirs...@rogers.com wrote:


Get off my phone and computer now!!!


ROTFLMAO!!

Nobody held a gun to your head and made you subscribe, and nobody can 
stop you from unsubscribing.






--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: support-seamonkey Digest, Vol 137, Issue 11

[shirstep]

  Get off my phone and computer now!!!Sent from my BlackBerry 10 smartphone on the Rogers network.From: support-seamonkey-requ...@lists.mozilla.orgSent: Friday, May 5, 2017 9:31 PMTo: support-seamonkey@lists.mozilla.orgReply To: support-seamonkey@lists.mozilla.orgSubject: support-seamonkey Digest, Vol 137, Issue 11





This message is eligible for Automatic Cleanup! (support-seamonkey-requ...@lists.mozilla.org) 
Add cleanup rule
 | More info





___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: LXLE, Seamonkey, PaleMoon, Thunderbird & Funding

[Mr. Ed]

On 05/06/17 6:31 AM, Alex Beauroy wrote:
> On 06/05/2017 04:13, Ronnie wrote:
>> Seamonkey, PaleMoon and Thunderbird should merge. Might be the best way
>> to proceed.
>>
>> Furthermore. I've been asking for more than a year how LXLE can donate
>> to the project through BountySource, as donations made to LXLE there are
>> designated for projects like Seamonkey.
>>
>> LXLE utilizes Seamonkey to a great extent. Helping to fund development
>> is a no brainer.
>>
>> Someone get something set up over there so we can contribute easily and
>> often.
>>
>> ~Ronnie
>>
> Hey there!!! What is "PaleMoon"
> @lex

https://www.palemoon.org/

-- 
"This is America!  You can't make a horse
 testify against himself!"  Mister Ed

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: LXLE, Seamonkey, PaleMoon, Thunderbird & Funding

[Alex Beauroy]

On 06/05/2017 04:13, Ronnie wrote:

Seamonkey, PaleMoon and Thunderbird should merge. Might be the best way
to proceed.

Furthermore. I've been asking for more than a year how LXLE can donate
to the project through BountySource, as donations made to LXLE there are
designated for projects like Seamonkey.

LXLE utilizes Seamonkey to a great extent. Helping to fund development
is a no brainer.

Someone get something set up over there so we can contribute easily and
often.

~Ronnie


Hey there!!! What is "PaleMoon"
@lex
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: The State of the SeaMonkey Union!

[Alex Beauroy]

On 06/05/2017 03:16, Ed Mullen wrote:

On 5/5/17 at 2:49 PM, Pat Connors's prodigious digits fired off with
great aplomb:



Setting up our own infrastructure, potentially in conjunction with
Thunderbird, will cost. If you feel you can contribute towards future
releases in this way, please consider donating:
https://www.seamonkey-project.org/donate/

I am trying to donate and I get the British Paypal which does not give
option for dollars.  When I go to the US version, it does not
recognize SeaMonkey.  Anyone have a good link for the US version of
Seamonkey Paypal?

PS  All these years of using SeaMonkey, I never knew about them get
money when we use DuckDuckGo for our search engine.  Thanks for
letting us know, I am now using it and find it as good as Google.



Yeah, ditto.  I changed from Google.  Hey, a few sheckles here ...


Me too , I change from Google & Yahoo Search ( the old "Alta Vista")
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: There's a new stable akalla 2.50 x64 build

[Richmond]

S Slicer wrote:
> Francesco wrote:
>> Thanks.
>> I'll keep 2.50 since i can live with this bug After all it's the only 
>> one i've found so far. Except for that, 64 bit 2.50 works really fine.
>>
>> Francesco
>>
>>
>> Il giorno martedì 2 maggio 2017 18:56:16 UTC+2, Frank-Rainer Grahl ha 
>> scritto:
>>> Looks like the x64 problem is a bit older :)
>>>
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=393302
>>> I wouldn't expect a solution soon.
>>>
>>> FRG
>>>
>>> Francesco wrote:
 I can't find a 32 bit 2.50 release on akalla site, but maybe i'm missing 
 something.

 Thanks
 Francesco

 Il giorno martedì 2 maggio 2017 14:30:20 UTC+2, Frank-Rainer Grahl ha 
 scritto:
> Interesting. Seems to be a problem with the x64 version only. First 
> problem I
> ever encountered with the x64. Please uninstall and try the x86 version. I
> will need to look at the installer and see if something is wrong there.
> FRG
>
> Francesco wrote:
>> Il giorno sabato 29 aprile 2017 11:57:27 UTC+2, Daniel ha scritto:
>>> On 29/04/2017 4:55 PM, Francesco wrote:
 Il giorno venerdì 28 aprile 2017 16:40:40 UTC+2, Daniel ha scritto:
> On 28/04/2017 11:20 PM, Francesco wrote:
>> Il giorno lunedì 24 aprile 2017 15:05:33 UTC+2, TCW ha scritto:
>>> Just saw it here
>>> https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
>>
>> Hello,
>> i installed this release and noticed that the right click "send to 
>> mail recipient" command doesn't work anymore.
>> Seamonkey is defined as default mail client, but the right click 
>> "send to mail recipient" command does nothing.
>> Any suggestion on how to fix it?
>> About memory usage, in my case sometimes it raeches 1,5 GB, but 
>> after a few seconds it goes to 500 MB with 3 tabs open.
>>
>> Thanks and best regards
>> Francesco
>>
> Francesco, as shown in my sig file I'm using the SM 2.46 Official
> Release Version, not the unofficial 2.50 release (although you User
> Agent suggests you posted via Google) that you suggest you are using.
>
> What are you doing when you try to 'right click "send to mail
> recipient"'?? Are you in a Browser window, or the Mail & Newsgroup 
> screen??
>
> My Right Click list fails to offer me "send to mail recipient" in 
> either
> screen! ;-(
>
 ahahah... sorry, i just noticed that my post was not completely 
 clear...
 When i try to send a file through Windows explorer by using mouse 
 right click and then selecting "send to mail recipient", nothing 
 happens.
>>>
>>> Ah!! O.K., well then your system seems to not know what is your default
>>> e-mail program. As you're using Windows, I would have expected
>>> Outlook/Express or Live Mail to have been your default system e-mail
>>> client if nothing else was selected.
>>>
 Or better, Seamonkey opens, if previously closed, but no mail compose 
 window appear.
 I also tried by creating a new sendto shortcut to Seamonkey with 
 /compose command but in this case the compose window opens, but with 
 no attachment.
 With 2.46 and 2.48b1 i had no problem.

 Thanks!

>>> Could it be that, whilst you had SM 2.46 or 2.48b1 installed, your
>>> system knew they were your default, so tried to start them, but now that
>>> you have removed them, your system just doesn't know what to start up
>>> properly??
>>>
>>> --
>>> Daniel
>>>
>>> User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101
>>> SeaMonkey/2.46 Build identifier: 20161213183751
>>
>> Daniel,
>> Seamonkey is still registered as default email client in my sistem. It 
>> starts on sendto command but with no mail-compose window (and no file 
>> attached).
>>
>> Francesco
>>

>>
> The last 64- bit version that worked for me was 2.45!
> 
> I even uninstalled all add-ons, and v2.50, like the others after v2.45, 
> crashed every time I tried to compose an e-mail or reply to an e-mail. I 
> have no idea why.
> 
Is it this one?

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

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: The State of the SeaMonkey Union!

[Frank-Rainer Grahl]

The DuckDuckGo deal was only recently finalized around the time 2.46 came out.

Thanks for your support
FRG

Ed Mullen wrote:
On 5/5/17 at 2:49 PM, Pat Connors's prodigious digits fired off with great 
aplomb:


Setting up our own infrastructure, potentially in conjunction with 
Thunderbird, will cost. If you feel you can contribute towards future 
releases in this way, please consider donating:

https://www.seamonkey-project.org/donate/
I am trying to donate and I get the British Paypal which does not give 
option for dollars.  When I go to the US version, it does not recognize 
SeaMonkey.  Anyone have a good link for the US version of Seamonkey Paypal?


PS  All these years of using SeaMonkey, I never knew about them get money 
when we use DuckDuckGo for our search engine.  Thanks for letting us know, I 
am now using it and find it as good as Google.




Yeah, ditto.  I changed from Google.  Hey, a few sheckles here ...



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey