exception error raised in sslstart
|
Jan. 07, 2009, 12:18 PM
Post: #46
|
|||
|
|||
RE: exception error raised in sslstart
(Jan. 07, 2009 11:31 AM)ProxRocks Wrote:(Jan. 07, 2009 03:57 AM)Oddysey Wrote: Given the above, Proxo can indeed be said to be accessing, and filtering on, another port besides 80/443. A bit strange that Scott never mentioned this... It seems we have a misunderstanding regarding local and remote ports here. http://www.geocities.com/sidki3003/prox/...tc/FAQ.txt : Quote:Q3: What local ports are involved in the request/response chain? IOW: Proxomitron listens on one single local port for incoming (by default local) user-agent HTTP(S) requests, filters their headers, then forwards them. It doesn't matter at all, to which remote port the forwarded request is going. However, usually it's port 80. Sometimes 443, sometimes 8080, sometimes a random port. |
|||
Jan. 07, 2009, 03:00 PM
Post: #47
|
|||
|
|||
RE: exception error raised in sslstart
(Jan. 07, 2009 03:20 AM)whenever Wrote: Maybe it is the time for us to upgrade to the latest openssl build? Yep. Unfortunately i don't have the knowledge to do that. If you know someone who can do it, great. If you want to contact the author of the original 2003 patch, let me know, maybe his old email address is still valid. |
|||
Jan. 07, 2009, 07:02 PM
Post: #48
|
|||
|
|||
RE: exception error raised in sslstart
(Jan. 07, 2009 12:45 AM)ProxRocks Wrote: keep in mind, the ONLY time i've seen this error is when NO web browser is even open... That seems strange. Surely there must have been some background request to the proxy for Windows Update, WGA Revalidation, Antivirus Definitions, etc. Proxo would not be doing anything on its own without a request to process. |
|||
Jan. 07, 2009, 07:49 PM
Post: #49
|
|||
|
|||
RE: exception error raised in sslstart
sidki, I think ProxRocks has it correct, or at least mostly correct. I don't know about the random part, but indeed, the browser first requests a resolution of the alphanumeric name entered on the address bar. That process starts with the OS, and if needful, is then handed off, at local port 53, to the nearest DNS (usually one's ISP), or to an assigned one (again, usually one's ISP). The Domain Name Resolution process does not use ports 80, 8080, or any other port beyond 53. (Unless the machine's SysAdmin has monkeyed with the OS's port assignments.)
But, ProxRocks, I contend that Proxo is indeed filtering the outgoing name resolution request. If it didn't then how would you describe the operation of these filters (taken from Scott's default config)? Code: In = FALSE Looking at them (and with a little help from JJoe, early on in my Proxo life), I got the idea to do this, while I was active at Yahoo: Code: In = TRUE I also wrote this (by myself, thank you ): Code: In = TRUE I'd be hard-pressed to find some other description for these actions besides "filtering the outgoing address", which as we've established, happens on Port 53 (when going outside of one's machine). Oddysey I'm no longer in the rat race - the rats won't have me! |
|||
Jan. 13, 2009, 02:01 PM
Post: #50
|
|||
|
|||
RE: exception error raised in sslstart
I found a link where proxomitron causes a error in SSL. To see it, clear your cache and go to https://addons.mozilla.org/seamonkey/addon/445
My dlls are dated from 2004, and i can't debug the code of a secure page... |
|||
Jan. 13, 2009, 03:04 PM
Post: #51
|
|||
|
|||
RE: exception error raised in sslstart | |||
Jan. 13, 2009, 04:15 PM
(This post was last modified: Jan. 13, 2009 04:59 PM by lnminente.)
Post: #52
|
|||
|
|||
RE: exception error raised in sslstart
Ups, sorry! The problem was in the connection settings of my browser, i didn't use to filter ssl content :/
Now the connection settings are well, proxomitron configured to filter SSL pages, and it seems i need to update the dll files... Now the cert! Saint Geek give me patience!! dlls from sidki: http://sidki.proxfilter.net/prox/ssl-stu...d-rev1.zip cert from yahoo groups: http://groups.yahoo.com/group/prox-list/...080923.zip Testing in Firefox 3.0.5 and 3.1b2(lot faster) i had to accept a lot of ssl problems and exceptions... doesn't seem very promising... Is it usual to have 16 "active" connections for a while after loading the secure page? |
|||
Jan. 13, 2009, 05:29 PM
Post: #53
|
|||
|
|||
RE: exception error raised in sslstart
Nope.
BTW, you don't need to configure an HTTPS proxy for your browser while using URL commands like above. |
|||
« Next Oldest | Next Newest »
|