Thread Closed 
Beta Config (Sep 19 2010)
Sep. 29, 2010, 05:43 PM
Post: #31
RE: Beta Config (Sep 19 2010)
(Sep. 28, 2010 10:27 PM)dave Wrote:  Found a little problem here: Yahoo News
The Print and Email links do not show up.

Confirmed.
Everyone is hereby invited to take it. Wink (It's apparently an Ad Functions I/II issue.)
Sep. 29, 2010, 11:07 PM
Post: #32
RE: Beta Config (Sep 19 2010)
After installing and loading this new beta config, Proxomitron is coughing up a long stream of SSLeay errors. At Proxomitron's Preference/HTTP settings, I do not not have the option checked for "Use SSLeay/OpenSSL to filter secure pages." I did not get these errors before installing this config set. Does anyone know how to correct this?
Sep. 29, 2010, 11:12 PM
Post: #33
RE: Beta Config (Sep 19 2010)
(Sep. 29, 2010 05:43 PM)sidki3003 Wrote:  Confirmed.
Everyone is hereby invited to take it. Wink (It's apparently an Ad Functions I/II issue.)

The links load for me only when both Ad Functions I and II are turned off which also allows the facebook and retweet links to load. However, there is a timer button that comes up on top of the facebook link. Also, if scripting is blocked and Ad Functions I and II are also turned off, none of the links show up [includes facebook, retweet, email and print].

A far as fixing this, I have no idea. Sad
Sep. 30, 2010, 02:08 AM
Post: #34
RE: Beta Config (Sep 19 2010)
(Sep. 29, 2010 05:43 PM)sidki3003 Wrote:  
(Sep. 28, 2010 10:27 PM)dave Wrote:  Found a little problem here: Yahoo News
The Print and Email links do not show up.

Confirmed.
Everyone is hereby invited to take it. Wink (It's apparently an Ad Functions I/II issue.)

More clues.

Error console shows

Code:
Error: YAHOO.ads.renderer has no properties
Source file: http://l.yimg.com/d/combo?yui/2.7.0/build/yahoo/yahoo-min.js&yui/2.7.0/build/event/event-min.js&yui/2.7.0/build/dom/dom-min.js&yui/2.7.0/build/get/get-min.js&yui/2.7.0/build/animation/animation-min.js&yui/2.7.0/build/json/json-min.js&yui/2.7.0/build/connection/connection-min.js&yui/2.7.0/build/datasource/datasource-min.js&yui/2.7.0/build/selector/selector-min.js&yui/2.7.0/build/cookie/cookie-min.js&yui/2.7.0/build/container/container-min.js&media/m/infinite_browse/mw_infinite_browse_carousel-min-3870.js&yui/2.7.0/build/element/element-min.js&yui/2.7.0/build/carousel/carousel-min.js&news/p/story/generic/infinite-browse-carousel-ult-min-44698.js&uh/15/js/uh_rsa-1.0.9.js&news/p/common/generic/common_base_rollup-min-44697.js&news/p/common/generic/common_page_rollup-min-26267.js&media/m/location_widget/location_widget-min-22834.js&news/p/common/generic/filter-reload-local-viewer-filter_init-reload_init-min-38036.js&s5/miniassist_200912081429.js&news/p/story/generic/mediabuzz-story-min-39391.js&news/p/common/generic/foundation/im-min-6761.js&news/p/common/generic/foundation/popup-min-12622.js&news/p/common/generic/im_init-min-12623.js&news/p/common/generic/popup_init-min-12623.js&news/p/story/generic/aska-min-44740.js&news/p/common/generic/yui3-min-36486.js&yui/2.7.0/build/imageloader/imageloader-min.js&yui/2.7.0/build/container/container_core-min.js&media/phugc/mwphcom_min_r1413.js
Line: 130

I added ~ads.renderer $TST(uHost=l.yimg.com) to the bottom of AdKeys-J.

Adding

Code:
l.yimg.com/b/social_buttons/   $SET(0=i_timer:0.)
pro.tweetmeme.com/button.js    $SET(0=i_level:2.0.a_cont_typ.)

to Exceptions-U seems to 'handle' or 'break' Wink the rest.
Sep. 30, 2010, 02:15 AM
Post: #35
RE: Beta Config (Sep 19 2010)
(Sep. 29, 2010 11:07 PM)wammie Wrote:  After installing and loading this new beta config, Proxomitron is coughing up a long stream of SSLeay errors. At Proxomitron's Preference/HTTP settings, I do not not have the option checked for "Use SSLeay/OpenSSL to filter secure pages." I did not get these errors before installing this config set. Does anyone know how to correct this?

What do the errors say?
Are the SSL DLLs in the Proxomitron's folder?
Do you have the header filter ! |||||||||||| 2.2 Use Half-SSL enabled?
Are you using any Half-SSL style (http://https..) links?
Sep. 30, 2010, 03:39 AM
Post: #36
RE: Beta Config (Sep 19 2010)
(Sep. 30, 2010 02:15 AM)JJoe Wrote:  
(Sep. 29, 2010 11:07 PM)wammie Wrote:  After installing and loading this new beta config, Proxomitron is coughing up a long stream of SSLeay errors. At Proxomitron's Preference/HTTP settings, I do not not have the option checked for "Use SSLeay/OpenSSL to filter secure pages." I did not get these errors before installing this config set. Does anyone know how to correct this?

What do the errors say?
Are the SSL DLLs in the Proxomitron's folder?
Do you have the header filter ! |||||||||||| 2.2 Use Half-SSL enabled?
Are you using any Half-SSL style (http://https..) links?
The error boxes I get are:

"ProxomiTron Application Error" > "Sorry, This version of SSLeay doesn't contain all the needed functions. It may be too different a version or compiled without all the necessary algorithms"
and
"ProxomiTron Application Error" > "OpenSSL_add_all_algorithms"

[Odd that "Proxomitron" has a capital T in there, huh?]

I do not have the header filter 2.2 Use Half-SSL enabled. I am not intentionally using any Half-SSL style links. I'm not doing anything unique or different now browsing-wise than what I did with the previous Feb/June 2009 config set. The libeay32.dll file in my Proxomitron directory is version 0.9.8.11 from the OpenSSL project and it's been in that directory for months.

I have no special filters or mods going on here. All I did was install the new Sept 19 2010 beta filter set, switch to the light mode using the header filter config, and started general browsing as a tester.
Sep. 30, 2010, 04:03 AM
Post: #37
RE: Beta Config (Sep 19 2010)
(Sep. 30, 2010 03:39 AM)wammie Wrote:  All I did was install the new Sept 19 2010 beta filter set, switch to the light mode using the header filter config, and started general browsing as a tester.

Are you sure "Use SSLeay/OpenSSL to filter secure pages" is not active? I think the beta has it enabled by default.

I haven't tried it but I don't think version 0.9.8.11 from the OpenSSL project will work with The ProxomiTron Wink . Compatible files are at http://www.proxomitron.info/files/index.html .

HTH
Sep. 30, 2010, 04:20 AM
Post: #38
RE: Beta Config (Sep 19 2010)
JJoe,

I made the changes to AdKeys-J and Exceptions-U as detailed in Post #34 and the buttons all showed up. Smile! However, they disappear if I block scripts. Can this be fixed? Thanks.
Sep. 30, 2010, 01:52 PM
Post: #39
RE: Beta Config (Sep 19 2010)
(Sep. 30, 2010 04:20 AM)dave Wrote:  JJoe,

I made the changes to AdKeys-J and Exceptions-U as detailed in Post #34 and the buttons all showed up. Smile! However, they disappear if I block scripts. Can this be fixed? Thanks.

If "block scripts" means enabling ! |||||||||||| 7.1 Block all Scripts 07.03.20 [sd] (o.3) (Out), try adding
news.yahoo.com $SET(0=i_script:0.)
to Exceptions-U.

HTH
Sep. 30, 2010, 09:25 PM
Post: #40
RE: Beta Config (Sep 19 2010)
(Sep. 30, 2010 01:52 PM)JJoe Wrote:  If "block scripts" means enabling ! |||||||||||| 7.1 Block all Scripts 07.03.20 [sd] (o.3) (Out), try adding
news.yahoo.com $SET(0=i_script:0.)
to Exceptions-U.

HTH
I am now using $SET(0=i_script:1.) for news.yahoo.com in Exceptions-U and was hoping to keep that and see the buttons. Sounds like this may not be possible.
Sep. 30, 2010, 10:55 PM
Post: #41
RE: Beta Config (Sep 19 2010)
(Sep. 30, 2010 04:03 AM)JJoe Wrote:  
(Sep. 30, 2010 03:39 AM)wammie Wrote:  All I did was install the new Sept 19 2010 beta filter set, switch to the light mode using the header filter config, and started general browsing as a tester.

Are you sure "Use SSLeay/OpenSSL to filter secure pages" is not active? I think the beta has it enabled by default.

I haven't tried it but I don't think version 0.9.8.11 from the OpenSSL project will work with The ProxomiTron Wink . Compatible files are at http://www.proxomitron.info/files/index.html .

HTH
Yes, in the Proxomitron client, I do not see the SSLeay option enabled in the checkbox. However, in the default config file, I see this:
[Global]...UseSSLeay = TRUE

Also, the configuration file contains the following:
In = TRUE
Out = FALSE
Key = "Location: 4 Half-SSL 06.11.02 (cch!) [jjoe] (d.2) (In)"
URL = "$TST(keyword=(^*.a_cont_loc.)*.i_ssl_h:[12].*)"
Match = "https://\1"
Replace = "http://https-px-.\1"

Would both of these filters need to be disabled?
Oct. 01, 2010, 12:50 AM (This post was last modified: Oct. 01, 2010 01:56 AM by JJoe.)
Post: #42
RE: Beta Config (Sep 19 2010)
(Sep. 30, 2010 09:25 PM)dave Wrote:  I am now using $SET(0=i_script:1.) for news.yahoo.com in Exceptions-U and was hoping to keep that and see the buttons. Sounds like this may not be possible.

Well you are being difficult Wink

but this web page filter,

Code:
[Patterns]
Name = "protect news.yahoo buttons from script block"
Active = TRUE
URL = "$TYPE(htm)(news.yahoo.com/|l.yimg.com/*social_buttons)"
Limit = 512
Match = "(<script\s*"
        "(BuzzWidget|"
        "Social_+Buttons|"
        "l.yimg.com/d/combo\?yui|"
        "static.ak.fbcdn.net/))\1"
Replace = "\1"

, appears to protect the necessary code for the social buttons and probably unnecessary (it's a quick hack) code.
Oct. 01, 2010, 01:55 AM (This post was last modified: Oct. 01, 2010 02:00 AM by JJoe.)
Post: #43
RE: Beta Config (Sep 19 2010)
(Sep. 30, 2010 10:55 PM)wammie Wrote:  Yes, in the Proxomitron client, I do not see the SSLeay option enabled in the checkbox. However, in the default config file, I see this:
[Global]...UseSSLeay = TRUE

Also, the configuration file contains the following:

Odd. So are you saying, the active cfg (aka default aka the beta) file has UseSSLeay enabled but the dialog sceen shows it disabled?

I think, I only see these errors after I hide the DLLs or use the wrong ones and try to load https with "UseSSLeay = TRUE" or Half-SSLed addresses (http://https..).

What does the dialog screen show after you use a text editor to change "UseSSLeay = TRUE" to "UseSSLeay = FALSE" in the beta's cfg, save, and then load or reload the beta? And do the errors go away.

(Sep. 30, 2010 10:55 PM)wammie Wrote:  In = TRUE
Out = FALSE
Key = "Location: 4 Half-SSL 06.11.02 (cch!) [jjoe] (d.2) (In)"
URL = "$TST(keyword=(^*.a_cont_loc.)*.i_ssl_h:[12].*)"
Match = "https://\1"
Replace = "http://https-px-.\1"

This filter is only active when the variable 'keyword' contains ".i_ssl_h:1." or ".i_ssl_h:2.". It is usually enabled by the trigger filter ! |||||||||||| 2.2 Use Half-SSL.
Oct. 01, 2010, 02:35 AM
Post: #44
RE: Beta Config (Sep 19 2010)
(Oct. 01, 2010 12:50 AM)JJoe Wrote:  Well you are being difficult Wink

but this web page filter,

Code:
[Patterns]
Name = "protect news.yahoo buttons from script block"
Active = TRUE
URL = "$TYPE(htm)(news.yahoo.com/|l.yimg.com/*social_buttons)"
Limit = 512
Match = "(<script\s*"
        "(BuzzWidget|"
        "Social_+Buttons|"
        "l.yimg.com/d/combo\?yui|"
        "static.ak.fbcdn.net/))\1"
Replace = "\1"

, appears to protect the necessary code for the social buttons and probably unnecessary (it's a quick hack) code.

Thanks JJoe. It works as advertised. Smile!
Oct. 01, 2010, 03:03 AM
Post: #45
RE: Beta Config (Sep 19 2010)
(Oct. 01, 2010 01:55 AM)JJoe Wrote:  Odd. So are you saying, the active cfg (aka default aka the beta) file has UseSSLeay enabled but the dialog sceen shows it disabled?
Yes.
(Oct. 01, 2010 01:55 AM)JJoe Wrote:  I think, I only see these errors after I hide the DLLs or use the wrong ones and try to load https with "UseSSLeay = TRUE" or Half-SSLed addresses (http://https..). What does the dialog screen show after you use a text editor to change "UseSSLeay = TRUE" to "UseSSLeay = FALSE" in the beta's cfg, save, and then load or reload the beta? And do the errors go away.
When I change the value to FALSE in the config file, save and reload, the checkbox in Proxomitron's gui remains blank. However... I've discovered that if I try to mark the checkbox, that's when I get the SSLeay wrong version messages, and the checkmark that appears there momentarily then disappears after I click OK on the dialogs.

So... ideally, sometime I'd like to try getting the SSL page filtering feature to work, but after reading some posts on bulletin boards about this, it seems that it can be quite tricky to get this working reliably across bank websites and such, and most folks using Proxomitron don't bother.
Thread Closed 


Forum Jump: