56366 - PSM doesn't work

Status: VERIFIED WORKSFORME

(Core Graveyard :: Security: UI, defect, P3)

Description

[R.K.Aa.]

2000101212 SEA linux
PSM downloaded and installed today.

going to http://www.nor.no there is a couple of buttons with rounded burgundy
corners: the top button reads "nettbanken" and should take me to a secure page.

This has worked before, but it is a while since i tested it, since PSM in
general is pretty unusable on linux.

The situation has worsened however:
What now happens is that it initially takes one *minute* to spawn the dialog box
that tells it's a secure page.

After that - nothing. Something seemingly loads and loads, but nothing happens.
No excessive CPU load either.

CLicking stop-button to stop whatever from loading, now hangs mozilla and
mailnews and whatever bits are open.

(In comparision, NC4.75 spawn the dialog box in a second, and thereafter load
the secure in a matter of seconds as well.)

Comment 1

[R.K.Aa.]

In case it is of interest, this was while using a P3/500 /256 RAM.

Comment 2

[John Unruh]

Worksforme. The security warning appeared in about one second, and then the page 
loaded in less than 15 seconds, including the time it took for psm to load.
There are other secure sites to try this on:
https://www.thawte.com
https://www.verisign.com
https://www.rsasecurity.com/

Comment 3

[R.K.Aa.]

This STILL doesn't work.
SEA 2000102021

The alert takes one to two minutes to appear.
Thereafter nothing happens, and moz ewventually freezes.
This outputs to console, perhaps interesting:
Error loading URL https://web.nor.no/main.asp?bank=nor&seg=P: 804b0002

I'm reopening this one. I can't use mozilla for daily tasks as it is now.

System info:
500MHZ P3, RH6.2 + all upgrades, helixcode gnome, sawmill.

Comment 4

[R.K.Aa.]

correction: Moz will "spin forever" till i hit stop, and THEN it will freeze.

Comment 5

[R.K.Aa.]

Thanks for the file. I guess you know that not a single filemode was correct (a
zip heh.. all were non-executable, me fixed it.)

Clicking the main button and once again it took a minute before alert appeared.
I wonder if there is some awful "blur" regression going on regarding js.

Scanning traffic after dismissing the alert, and all i saw was UDP traffic at
intervals, of which all were seemingly standard query DNS lookups. It never got
further.

a netstat shows 7 tcp sockets opened, all like this:

tcp      0   0 mp-217-178-252.dax:2064 153.110.204.15:www    ESTABLISHED

Yet again clicking a Stop now hanged mozilla.

I have two ISP's i dial up to. Dialed up the other one now, to test that too.
Again it took a minute for alert to appear.
Now running gdb i see 12 new threads spawn before alert appears.
First very slowly - then the last 6 a sec before alert pops up.

Dismissing alert spawns yet 3 new threads.
And then - noooothing. Mozilla spins and spins.

a ps -ef |grep mozilla shows this:

dark     12317  7950  0 22:30 pts/0    00:00:00 sh /usr/local/mozilla/mozilla -g
dark     12320 12317  0 22:30 pts/0    00:00:00 sh /usr/local/mozilla/run-mozill
dark     12329 12320  0 22:30 pts/0    00:00:02 /usr/bin/gdb /usr/local/mozilla/
dark     12330 12329 37 22:30 pts/0    00:01:28 /usr/local/mozilla/mozilla-bin
dark     12332 12329  0 22:30 pts/0    00:00:00 /usr/local/mozilla/mozilla-bin
dark     12333 12329  0 22:30 pts/0    00:00:00 /usr/local/mozilla/mozilla-bin
dark     12334 12329  0 22:30 pts/0    00:00:00 /usr/local/mozilla/mozilla-bin
dark     12335 12332  0 22:31 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12336 12332  0 22:31 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12337 12332  0 22:31 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12338 12332  0 22:32 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12339 12332  0 22:32 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12340 12332  0 22:32 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12341 12332  0 22:32 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12342 12332  0 22:32 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12343 12332  0 22:32 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12344 12332  0 22:32 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12345 12332  0 22:32 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12346 12332  0 22:32 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12347 12332  0 22:32 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12348 12332  0 22:32 pts/0    00:00:00 [mozilla-bin <defunct>]
dark     12349 12332  0 22:32 pts/0    00:00:00 [mozilla-bin <defunct>]

And finally a NEW alert box: "The connection was refused when attempting to
contact web.nor.no.
This time mozilla didn't freeze: it stopped spinning after that last (new) alert
box.

Clicking the big button once again this time spawned only 1 new thread,
and the alert appeared almost immediately.
Same result however - connection refused

I tried loading http://www.nor.no/ again, but now couldn't even load it.
got "Error loading URL http://www.nor.no/: 80004005" over and over.
Deleted cache and memory via prefs, quit moz - restarted:
Same error. Trying the sit now with Netscape 4.7 instead gave a more explanatory
error mesage: "TCP error: Nor route to host". My luck.

The site going down before my very eyes explains the "new" alert. But there are
bugs enough to chomp on here. Not sure it's really PSM anymore, but it sure
horks it for me. Contours of both js and networking here however.

Comment 6

[R.K.Aa.]

Downloaded trunk build ID 2000102321 to try again.
The alert still takes insanely long to appear.
Then moz froze after dismissing it.
This was while testing as regular user.

Then i tried running as root:
Now it all worked, even if alert took long time.
I could log in.

Looked at files in /usr/local/mozilla and noticed that file component.reg both
there and in /usr/local/mozilla/psm had just been written to - the timestamp was
a minute old.

Then quit mozilla and tried as regular user again: same result as before -
things took time, then mozilla froze.

Trying yet again - this time sniffing packets to see what was on.

THe first sniff didn't reveal much - traffic stopped, but one outgoing packet
went to deploy.akamaitechnologies.com for some reason.

Killed moz and tried again, sniffing more.
This time no akamaitech.
Two TCP packets only, then full freeze.
The packets were one standard query and one standard query response. only DNS
lookups really. No akamaitech this time. (Pity i trashed that first sniff - it
was weird, since no other traffic was going on.)

However: with this build i never get as far (as regular user) as to the the
"defunct" mozilla-bin's i observed with previous build.

Is PSM only supposed to work for user root?
I checked all accesses on the files in the zip you pointed me to.
I set all runnables and libraries to executable by all, and writeable only by
root. This should be correct, AFAIK.

Not sure how to conclude about this. "Something is wrong".

Comment 7

[R.K.Aa.]

correction:
running under gdb i see the same massive amount of threads spawn before alert
dialog appears,
and the same gang of defunct mozilla-bin's. Each thread it's own, 15 all in all.

And the packets sent are UDP (not TCP)

I now waited a long time, till i finally got a "connection refused" dialog
No freeze after dismissing that.

Clicked big button on webpage again. Now alert appeared right away, spawning
only one thread.
Connection was refused yet again.
Quit mozilla which exited normally.
15 TCP sockets to the URL are now hanging open "TIME_WAIT" or "FIN_WAIT2"
----
Tried as root again: Again one minute before alert appears.
And again it after this responds and feeds me the correct URL.
So it's not down. But mozilla doesn't let me access it via PSM as a regular user.

Sorry i'm wordy, but "this bad bug".

Comment 8

[R.K.Aa.]

build installed some hours ago with installer:
Alert now appears right away.

-No https pages at my bank are able to load completely.
-The "Bank" page that should spawn in a new window, appears in the main window
instead.
-No lock icon appears.
-PSM *does* work (1.4), and the threads are spawned by the dozen and doesn't
terminate till i quit mozilla. (That would be bug 34834, now marked fixed, which
it obviously isn't.)

No crash nor hang: Resolving as WFM.

Comment 9

[John Unruh]

Dark, please try the latest PSM 1.4 for linux, updated 10/4.
http://www.concentric.net/~unruh/linux-psm1.4.zip

Comment 10

[R.K.Aa.]

I wonder if there are some significant differences between the builds installer
installs and the SEA tar.gz builds. Testing this all again with the new psm and
a sea build from 1106, the bug again behaves as bad as originally reported.
Extremely long delay before alert appears, and in the end taking me nowhere - a
click finally causing a freeze. Reopening on that note.

Will try with the installer build as well, but tomorrow.

(An (unrelated) sample of a bug that is in the sea-builds but not in installed
ones is  bug 59160)

Comment 11

[R.K.Aa.]

Tried again with installed build 2000110821

As user root:
First time i clicked the bank button nothing happened at all, apart from console
indicating that an alert SHOULD have appeared ("we don't handle
eBorderStyle_close yet... please fix me")

I hit the stop button - to no avail.
After 4 minutes i clicked the reload-button instead. NOW the alert appeared.
The page also started reloading so i hadn't gotten any further.

I then clicked the bank button again.
This time the alert appeared right away and i was sent to the login page at the
bank.

Turns out there's another bug also active on that page:
THe one where horisontal ruler blinks and blinks, forever reloading.

After having watched that for a minute or so, the page still hadn't stopped
loading. Nor had the lock icon changed to the locked look.

I then hit stop-button again.
Now the lock-button immediately displayed locked status.

I then did a ps -ef |grep psm |wc -l

There were already 60 psm threads spawned.

I then quit mozilla, to test it as my regular user.

As regular user i can't seem to be able to reload the page, but the
reload-button is also now what spawns the alert-dialog. (I also did "hard"
reload, shift+reload and ctrl+reload, just in case.)
Console just states Error loading URL http://www.nor.no/index.html: 804b0002
I kept trying to reload it but it the error just kept appearing.
Testing with NC4.75 the page loaded fine during all this. so whatever error, it
was mozilla's.
I couldn't send this bug either, nor get mail, turned out all networking had
stopped working in moz.

I then quit mozilla and restarted. Now the bank index page loaded right away again.
But when clicking bank-button: Same behaviour as before with the alert box:
doesn't appear till i hit reload.
And when reload is hit, i get
Error loading URL https://web.nor.no/main.asp?bank=nor&seg=P: 804b0002
Then networking dies again and i have to quit moz and restart to get it working
again.

Tried again. Now, instead of clicking reload i clicked a link to bug-list on
personal toolbar.
Then the alert-box suddenly appeared - and the buglist loaded. I clicked stop
there and filled in URL to this
bug manually. Now the networking bits were hanging again and i had to quit moz
once more.

Sniffing with ethereal shows that no packets are sent at all.

All in all there seems to be a whole ratpack of unfortunate bugs making their
worst of this case, but the effect is that PSM doesn't work - way too many
threads are spawned, if i at all get that far.

I suggest you try the site for yourself.
You don't need an account to see the initial mishaps.
I look forward to testing PSM again when this bug is fixed.

Comment 12

[R.K.Aa.]

One bug affecting the behaviour observed here is bug 52798
"gif img in table with width=100% blinks rapidly (flashes, flickers)"

Also note: The URL in question has modified code since this bug was originally
submitted: It now loads the secure bank-page in the original window, and no
longer spawns a second window for that.

Comment 13

[Andreas Franke (gone)]

This should be the same as bug 49507. 

Comment 14

[nitinp]

changing QA contact to [e-mail]

Comment 15

[John Unruh]

Worksforme with the 11/27 commercial trunk build.

Comment 16

[R.K.Aa.]

well it sure doesn't work for me.
2000121414 d/l'ed PSM via debug/install PSM (which is 1.3 i believe)
Hangs and hangs - the dialogue doesn't appear when run as normal user.
Funny how all .so files aren't executable also, after install.
But they are doublets anyways, so no harm done perhaps?

So:
As normal user: No go - loads forever - freezes when i click stop.
As root: spawning countless new PSM threads, one for each time the HR image
flickers, which happens very frequently. Once a second perhaps.

Comment 17

[John Unruh]

Try today's build. 
http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-i686-pc-linux-gnu.tar.
gz

Comment 18

[John Unruh]

Verifying.

Comment 19

[John Unruh]

Mass changing Security:Crypto to PSM

Comment 20

[John Unruh]

Mass changing Security:Crypto to PSM