Re: Chase bank access bug fixed in SM 2.32
Ken Rudolph wrote: Using the PrefBar Customize, I get the User Agent Extlist box. But I'm not sure how to go from there. I tried putting in the Firefox user agent above in the Value box opposite Real UA and applying that. But it didn't affect the browser message at Chase.com. I know I'm doing something wrong...but I just don't have the competence to know what I'm doing at that level or precisely what I have to do. I'm also afraid of doing something that is irrevocable and would cause other problems. Oh, well. Looks like I missed the beginning of that procedural chain. Lemme try again. In the PrefBar tool bar, right-click on the toolbar, and select Customize PrefBar. You can also get to that via Edit - Preferences - PrefBar. From there, instructions as before: make sure you've dragged the User Agent item into the Enabled Items column, and then double-click User Agent to see the specific settings available. Smith ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
NFN Smith wrote: Ken Rudolph wrote: Could you specify exactly how you added the FireFox user-agent string to the PrefBar. For somebody who is tech stupid, that is. There used to be a way in the Tools menu to manage the user-agent. That hasn't been around for a while. I missed responding to this particular question in a separate reply. In the PrefBar settings, make sure you drag the User Agent setting into Enabled Items section. Then double-click on the User Agent, and you'll get a dialog box that allows you to choose whatever spoofs you want. One minor annoyance is that the defaults offered are several years old, and you'll need to update to settings that are relatively current. The useragentstring.com reference is definitely helpful. If you want a setting for the current version of Firefox, running under Windows 7/64, then you would want: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0 Using the PrefBar Customize, I get the User Agent Extlist box. But I'm not sure how to go from there. I tried putting in the Firefox user agent above in the Value box opposite Real UA and applying that. But it didn't affect the browser message at Chase.com. I know I'm doing something wrong...but I just don't have the competence to know what I'm doing at that level or precisely what I have to do. I'm also afraid of doing something that is irrevocable and would cause other problems. Oh, well. -- Ken Rudolph ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
On 16/01/15 12:27, NFN Smith wrote: Snip See above. Yes, you can change your user agent in prefs.js, but that hard-codes things, and you have to update every time that Mozilla does another update cycle. One minor glitch that I've discovered with spoofing in Seamonkey is that it affects your email, as well. When you send mail, User-Agent: is also a header line. I use the dispMUA extension that shows a message's User-Agent: header (useful for providing tech support, to know which client a user is using), as an icon in the message header display. A few days ago, I was sorting out my Sent Mail folder, and noticed that several messages that I had sent were showing a Firefox logo. On further investigation, I discovered that those messages had been sent, when I had Seamonkey spoofing that I was running Firefox on a Mac. Smithy, why use an extension (dispMUA) to display a message's User-Agent: header when all you need do is set the pref mailnews.headers.showUserAgent to false and the User-Agent line will be displayed in the Subject area of the message pane. Could you specify exactly how you added the FireFox user-agent string to the PrefBar. For somebody who is tech stupid, that is. There used to be a way in the Tools menu to manage the user-agent. That hasn't been around for a while. This might be the general.useragent.compatMode.firefox pref in about:config of SeaMonkey, *not* PrefBar. Try clicking on the Pref to set it to false, maybe. -- Daniel User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 SeaMonkey/2.32 Build identifier: 20141218225909 or User agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 SeaMonkey/2.32 Build identifier: 20150101220549 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
Daniel wrote: Smithy, why use an extension (dispMUA) to display a message's User-Agent: header when all you need do is set the pref mailnews.headers.showUserAgent to false and the User-Agent line will be displayed in the Subject area of the message pane. Partially personal preference and partially that I didn't know that setting exists. With the extension, the mail client is displayed as an icon, and for me, that makes it faster to see what I'm looking for, rather than having to read the text. Also, I less often need to see the detail of the User Agent string (version and platform) than simply to see which client is being used. Smith ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
Ken Rudolph wrote: Could you specify exactly how you added the FireFox user-agent string to the PrefBar. For somebody who is tech stupid, that is. There used to be a way in the Tools menu to manage the user-agent. That hasn't been around for a while. I missed responding to this particular question in a separate reply. In the PrefBar settings, make sure you drag the User Agent setting into Enabled Items section. Then double-click on the User Agent, and you'll get a dialog box that allows you to choose whatever spoofs you want. One minor annoyance is that the defaults offered are several years old, and you'll need to update to settings that are relatively current. The useragentstring.com reference is definitely helpful. If you want a setting for the current version of Firefox, running under Windows 7/64, then you would want: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0 Smith ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
On 17/01/15 05:20, NFN Smith wrote: Daniel wrote: Smithy, why use an extension (dispMUA) to display a message's User-Agent: header when all you need do is set the pref mailnews.headers.showUserAgent to false and the User-Agent line will be displayed in the Subject area of the message pane. Partially personal preference and partially that I didn't know that setting exists. With the extension, the mail client is displayed as an icon, and for me, that makes it faster to see what I'm looking for, rather than having to read the text. Also, I less often need to see the detail of the User Agent string (version and platform) than simply to see which client is being used. Smith RGR, to each their own! -- Daniel User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 SeaMonkey/2.32 Build identifier: 20141218225909 or User agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 SeaMonkey/2.32 Build identifier: 20150101220549 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
David H. Durgee wrote: Ken Rudolph wrote: David H. Durgee wrote: Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have the annoying and false disclaimer on their log-on page: Your browser may not give you the best experience when you're on Chase.com. We recommend that you use any of the following browsers: Internet Explorer 8 or higher, Firefox 25 or higher, Safari 6.0 or higher, and Chrome 31 or higher. I wish there were some easy way to alter the user-agent line to preference the Firefox version, since asking the banks to accept SeaMonkey as a valid browser over and over gets nowhere. That is why I copied the FireFox user agent string and added it to PrefBar as an additional user agent. I now tend to leave this set as my user agent string to avoid this very idiotic message there and elsewhere. Could you specify exactly how you added the FireFox user-agent string to the PrefBar. For somebody who is tech stupid, that is. There used to be a way in the Tools menu to manage the user-agent. That hasn't been around for a while. It has been a while since I did so, but I believe it was relatively simple. Hit the Customize button on your PrefBar toolbar. That should open a new window of available and enabled items. Right-click on the User Agent entry under enabled items and select Edit from the pop-up menu. Open FireFox and access the troubleshooting information either via menus or about:support so you will have access to the User Agent string. Hit the + button on the user agent edit window from PrefBar to obtain a new entry in the table. Copy/Paste the FireFox string into the blank Value field and label it as you like. Optionally you can re-order the user agent strings and the hit the OK button to save the changes. Dave To add to this, go to http://www.useragentstring.com/ You can cut and paste any of the user agent strings to spoof other browsers. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
Following up several responses in a single post... Zeb Carter wrote: David H. Durgee wrote: Ken Rudolph wrote: David H. Durgee wrot e: Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have For this, I think the problem is not with Seamonkey, but brain-dead developers who know only about Firefox, not that Firefox is merely the most prominent browser built on Gecko (http://geckoisgecko.org). Since the time that Seamonkey developers went with spoofing Firefox in ID string (and including the Seamonkey name), I've found that the number of conflicts has been minimal. There's a couple of extensions that allow for spoofing -- Browser Agent Switcher, and PrefsBar. It's been a long time since I've needed to spoof Firefox, although I occasionally will spoof my platform to allow for downloads of Mac versions of stuff for my software collection. Some sites look for Browser Agent strings for contextual delivery of downloads (by platform). And even if I don't often need to spoof my browser identity, I've found that there's several other settings in PrefsBar that I find really useful. In any case, it's been long enough since I've had the misfortune of having to connect to Chase, that I forgot that their developers are of the brain-dead variety, in how they identify browsers, and their assumptions of users' work flows. I know that they're trying to do security, but I find their aggressive offering of remember password show that they don't really get it, in assuming that user presence at a keyboard is sufficient to authenticate the user. I wish there were some easy way to alter the user-agent line to preference the Firefox version, since asking the banks to accept SeaMonkey as a valid browser over and over gets nowhere. That is why I copied the FireFox user agent string and added it to PrefBar as an additional user agent. I now tend to leave this set as my user agent string to avoid this very idiotic message there and elsewhere. See above. Yes, you can change your user agent in prefs.js, but that hard-codes things, and you have to update every time that Mozilla does another update cycle. One minor glitch that I've discovered with spoofing in Seamonkey is that it affects your email, as well. When you send mail, User-Agent: is also a header line. I use the dispMUA extension that shows a message's User-Agent: header (useful for providing tech support, to know which client a user is using), as an icon in the message header display. A few days ago, I was sorting out my Sent Mail folder, and noticed that several messages that I had sent were showing a Firefox logo. On further investigation, I discovered that those messages had been sent, when I had Seamonkey spoofing that I was running Firefox on a Mac. Could you specify exactly how you added the FireFox user-agent string to the PrefBar. For somebody who is tech stupid, that is. There used to be a way in the Tools menu to manage the user-agent. That hasn't been around for a while. For this one, I happen to have Firefox installed on my machine, because I provide tech support for Firefox users. Going to Help - About shows what Firefox is showing. To add to this, go to http://www.useragentstring.com/ You can cut and paste any of the user agent strings to spoof other browsers. This is good stuff, although a quick look indicates that they're a couple of release cycles behind, at least for Seamonkey. Firefox looks current. However, if you look at several of the most current settings, it's easy enough to interpolate up to most current versions. In my case, since I spoof both platform and browser, it's definitely useful for getting the detail of what I want. Smith ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
On 15/01/2015 11:20, PhillipJones wrote: With latest SeaMonkey Version; now Discover also does this. The Wheels at top of SeaMonkey(or Mozilla) are not not educating these financial institutions. In the early days of Mozilla/Firefox they had a tech evang volunteer team who would bombard website contact addresses to complain about this sort of problem. There's still a tech evang component in Bugzilla but there's no team any more, at least since Firefox reached mainstream status. Phil -- Philip Chee phi...@aleytys.pc.my, philip.c...@gmail.com http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
Ken Rudolph wrote: David H. Durgee wrote: Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have the annoying and false disclaimer on their log-on page: Your browser may not give you the best experience when you're on Chase.com. We recommend that you use any of the following browsers: Internet Explorer 8 or higher, Firefox 25 or higher, Safari 6.0 or higher, and Chrome 31 or higher. I wish there were some easy way to alter the user-agent line to preference the Firefox version, since asking the banks to accept SeaMonkey as a valid browser over and over gets nowhere. That is why I copied the FireFox user agent string and added it to PrefBar as an additional user agent. I now tend to leave this set as my user agent string to avoid this very idiotic message there and elsewhere. Could you specify exactly how you added the FireFox user-agent string to the PrefBar. For somebody who is tech stupid, that is. There used to be a way in the Tools menu to manage the user-agent. That hasn't been around for a while. It has been a while since I did so, but I believe it was relatively simple. Hit the Customize button on your PrefBar toolbar. That should open a new window of available and enabled items. Right-click on the User Agent entry under enabled items and select Edit from the pop-up menu. Open FireFox and access the troubleshooting information either via menus or about:support so you will have access to the User Agent string. Hit the + button on the user agent edit window from PrefBar to obtain a new entry in the table. Copy/Paste the FireFox string into the blank Value field and label it as you like. Optionally you can re-order the user agent strings and the hit the OK button to save the changes. Dave ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have the annoying and false disclaimer on their log-on page: Your browser may not give you the best experience when you're on Chase.com. We recommend that you use any of the following browsers: Internet Explorer 8 or higher, Firefox 25 or higher, Safari 6.0 or higher, and Chrome 31 or higher. I wish there were some easy way to alter the user-agent line to preference the Firefox version, since asking the banks to accept SeaMonkey as a valid browser over and over gets nowhere. That is why I copied the FireFox user agent string and added it to PrefBar as an additional user agent. I now tend to leave this set as my user agent string to avoid this very idiotic message there and elsewhere. Dave ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
On 01/14/2015 07:44 PM, Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have the annoying and false disclaimer on their log-on page: Your browser may not give you the best experience when you're on Chase.com. We recommend that you use any of the following browsers: Internet Explorer 8 or higher, Firefox 25 or higher, Safari 6.0 or higher, and Chrome 31 or higher. I wish there were some easy way to alter the user-agent line to preference the Firefox version, since asking the banks to accept SeaMonkey as a valid browser over and over gets nowhere. You are already advertising Firefox compatibility with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 For whatever reason Chase didn't like it, so [1094714 – Unable to login at chase.com due to NS_ERROR_FAILURE (SeaMonkey only)](https://bugzilla.mozilla.org/show_bug.cgi?id=1094714) had to be fixed. -- Strip District Music Fest 2015-01-17 http://www.stripdistrictmusicfest.com/ Je Suis Charlie ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
Paul B. Gallagher wrote: PhillipJones wrote: With latest SeaMonkey Version now Discover also does This. The Wheel at To of SeaMonkey are not (or Mozilla) is not educating these financial institutions. I've seen you write coherent, grammatical English lots of times, so I know you're capable of it, but the last sentence has me completely baffled. I must assume that autocorrupt is interfering. What did you mean to say? Wrote too fast. (brain going faster than fingers). Should be: With latest SeaMonkey Version; now Discover also does this. The Wheels at top of SeaMonkey(or Mozilla) are not not educating these financial institutions. -- Phillip M. Jones, C.E.T. If it's Fixed, Don't Break it http://www.phillipmjones.netmailto:pjones...@comcast.net http://phillipjones-cet.net/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
PhillipJones wrote: Paul B. Gallagher wrote: PhillipJones wrote: With latest SeaMonkey Version now Discover also does This. The Wheel at To of SeaMonkey are not (or Mozilla) is not educating these financial institutions. I've seen you write coherent, grammatical English lots of times, so I know you're capable of it, but the last sentence has me completely baffled. I must assume that autocorrupt is interfering. What did you mean to say? Wrote too fast. (brain going faster than fingers). Should be: With latest SeaMonkey Version; now Discover also does this. The Wheels at top of SeaMonkey(or Mozilla) are not educating these financial institutions. See I did it again I added one to many not's. I am removing rather than rewriting again. -- Phillip M. Jones, C.E.T. If it's Fixed, Don't Break it http://www.phillipmjones.netmailto:pjones...@comcast.net http://phillipjones-cet.net/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have the annoying and false disclaimer on their log-on page: Your browser may not give you the best experience when you're on Chase.com. We recommend that you use any of the following browsers: Internet Explorer 8 or higher, Firefox 25 or higher, Safari 6.0 or higher, and Chrome 31 or higher. I wish there were some easy way to alter the user-agent line to preference the Firefox version, since asking the banks to accept SeaMonkey as a valid browser over and over gets nowhere. With latest SeaMonkey Version now Discover also does This. The Wheel at To of SeaMonkey are not (or Mozilla) is not educating these financial institutions. -- Phillip M. Jones, C.E.T. If it's Fixed, Don't Break it http://www.phillipmjones.netmailto:pjones...@comcast.net http://phillipjones-cet.net/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
PhillipJones wrote: Paul B. Gallagher wrote: PhillipJones wrote: With latest SeaMonkey Version now Discover also does This. The Wheel at To of SeaMonkey are not (or Mozilla) is not educating these financial institutions. I've seen you write coherent, grammatical English lots of times, so I know you're capable of it, but the last sentence has me completely baffled. I must assume that autocorrupt is interfering. What did you mean to say? Wrote too fast. (brain going faster than fingers). Should be: With latest SeaMonkey Version; now Discover also does this. The Wheels at top of SeaMonkey(or Mozilla) are not not educating these financial institutions. OK, now I see. Thanks. -- 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: Chase bank access bug fixed in SM 2.32
David H. Durgee wrote: Ken Rudolph wrote: Thank you SeaMonkey team! One seriously annoying bug fixed. Still, after several months, the Chase (and also the BofA) sites still have the annoying and false disclaimer on their log-on page: Your browser may not give you the best experience when you're on Chase.com. We recommend that you use any of the following browsers: Internet Explorer 8 or higher, Firefox 25 or higher, Safari 6.0 or higher, and Chrome 31 or higher. I wish there were some easy way to alter the user-agent line to preference the Firefox version, since asking the banks to accept SeaMonkey as a valid browser over and over gets nowhere. That is why I copied the FireFox user agent string and added it to PrefBar as an additional user agent. I now tend to leave this set as my user agent string to avoid this very idiotic message there and elsewhere. Could you specify exactly how you added the FireFox user-agent string to the PrefBar. For somebody who is tech stupid, that is. There used to be a way in the Tools menu to manage the user-agent. That hasn't been around for a while. -- Ken Rudolph ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Chase bank access bug fixed in SM 2.32
PhillipJones wrote: With latest SeaMonkey Version now Discover also does This. The Wheel at To of SeaMonkey are not (or Mozilla) is not educating these financial institutions. I've seen you write coherent, grammatical English lots of times, so I know you're capable of it, but the last sentence has me completely baffled. I must assume that autocorrupt is interfering. What did you mean to say? -- 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
