1
OESF Wiki / Http Error 400
« on: December 16, 2007, 10:26:42 pm »
Thanks a lot, I can now access the wiki properly from office.
Select language:
News:
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
2
The reason why people are blocked from logging into the wiki:
Quote
Bad Behavior 2.0.11
December 6th, 2007 by Michael Hampton
All users should update to Bad Behavior 2.0.11 immediately to prevent being blocked from your own site.
Within the past two days users have found themselves blocked from their own sites while using recent versions of Bad Behavior. A third party blacklist which Bad Behavior queries recently began sending false positives for any IP address queried, causing everyone using Bad Behavior to be blocked. This issue is fixed in Bad Behavior 2.0.11.
Download Bad Behavior now!
P.S. Yes, Bad Behavior is still in development. More news coming soon.
Update: Some people have asked for more details on what exactly happened. In brief, yesterday I moved all of my sites to a new dedicated server. In the process, I decommissioned an old blacklist I was running which I thought wasn’t being used, not realizing that Bad Behavior was still set to use it. Shortly afterward, I found myself locked out of my own blog, just as you all did. So therefore, this release.
3
OESF Wiki / Http Error 400
« on: December 11, 2007, 05:12:48 am »
Okay, I got around setting up a test server running MediaWiki and Bad Behavior:
Commenting the below lines in common_tests.inc.php unblocks myself from the site:
if (array_key_exists('Proxy-Connection', $package['headers_mixed'])) {
return "b7830251";
}
According to google, Proxy-Connection: Close is a legitimate http header. See here for another user blocked by Proxy-Connection
Commenting the below lines in common_tests.inc.php unblocks myself from the site:
if (array_key_exists('Proxy-Connection', $package['headers_mixed'])) {
return "b7830251";
}
According to google, Proxy-Connection: Close is a legitimate http header. See here for another user blocked by Proxy-Connection
4
OESF Wiki / Http Error 400
« on: December 10, 2007, 10:55:25 pm »
Update: I still have the same 400 error when I try to access any page in the wiki from office, just now.
5
I have some suggestions on Bad Behavior in here.
Regarding upload: the reason why Special:upload says uploads are disabled is probably because Meyer set $wgEnableUploads back to false at the time you access the page. However I cannot debug the situation further unless an administrator post the current LocalSettings.php (in MediaWiki) up here.
Regarding upload: the reason why Special:upload says uploads are disabled is probably because Meyer set $wgEnableUploads back to false at the time you access the page. However I cannot debug the situation further unless an administrator post the current LocalSettings.php (in MediaWiki) up here.
6
OESF Wiki / Http Error 400
« on: December 10, 2007, 11:07:39 am »
Well, thanks to tux for bringing me back to this thread (and the image upload thread next door). As I am recently busy with some other stuffs I do not check oesf that often anymore... anyway lets first answer your questions:
1. What was the URI that gave you the above error?
Any page on the oesf wiki, for example: https://www.oesf.org/index.php?title=Main_Page
I am effectively blocked from viewing all oesf wiki pages from my office network.
2. What was the date and time the error occurred? (If you can't remember, try accessing the URI again and report the results.)
Well, basically I can reproduce the error any time I was in office when I try to access any wiki pages. The last time I had such problem.. was probably the time when I posted the message, so it was approximately Nov 4 2007, 09:41 PM server time.
3. Can you access any other MediaWiki (like Wikipedia) from behind your company's proxy server?
Yes, of course. I own several MediaWiki websites myself: here, here, here, and here, just to name a few. And I can access them from office without any problem.
4. Are you saying that you are being blocked from viewing/browsing the Wiki or is it that editing is being blocked? Are you able to access other wikimedia sites that have BadBehaviour and the other spam defenses, some of which you suggested, installed. cool.gif
I will check tomorrow when I am back in office to see if viewing the wiki is still being blocked - if it is so then I believe there's too much anti-spam defenses on the website and that's affecting legitimate users. No I am not aware of any other mediawiki sites with the BadBehaviour extension.
5. Do you have a problem when accessing the Wiki using non-proxy access?
Well I am now on my home network at a fixed IP (through a router) at 125.59.xx.xx and had no problem viewing the site - but Bad Behaviour is preventing me from creating a new user account on the wiki. I do not experience the same problem I had in office when I use my own private Squid server at 202.177.xx.xx to access the wiki, account creation is still blocked though.
6. I must say that something strange appears to be going on if attempting to access the Wiki apparently asks for / access. blink.gif From your experience with the wikimedia software have you any pointers to a solution? Did your IT staff have anything to say?
Since it is apparent from the Bad Behaviour page itself that the bad behavior extension is generating way too many false positives, I think it may be more beneficial if the extension is removed and replaced with other anti-spam measures, for example the ReCaptcha extension developed by UC Berkeley together with some access control customization settings. On the other hand you could try settings Bad Behavior blocking mode to normal, instead of strict I presume you are running. The Bad Behavior extension does not offer any fine tuning of the anti-spam settings, and the documentation is awfully vague and limited: quote
p.s.
Wikipedia does not use Bad Behavior, instead they use AntiSpoof, a modified ConfirmEdit for links in incoming edits and account creation, SpamBlacklist and Username Blacklist.
1. What was the URI that gave you the above error?
Any page on the oesf wiki, for example: https://www.oesf.org/index.php?title=Main_Page
I am effectively blocked from viewing all oesf wiki pages from my office network.
2. What was the date and time the error occurred? (If you can't remember, try accessing the URI again and report the results.)
Well, basically I can reproduce the error any time I was in office when I try to access any wiki pages. The last time I had such problem.. was probably the time when I posted the message, so it was approximately Nov 4 2007, 09:41 PM server time.
3. Can you access any other MediaWiki (like Wikipedia) from behind your company's proxy server?
Yes, of course. I own several MediaWiki websites myself: here, here, here, and here, just to name a few. And I can access them from office without any problem.
4. Are you saying that you are being blocked from viewing/browsing the Wiki or is it that editing is being blocked? Are you able to access other wikimedia sites that have BadBehaviour and the other spam defenses, some of which you suggested, installed. cool.gif
I will check tomorrow when I am back in office to see if viewing the wiki is still being blocked - if it is so then I believe there's too much anti-spam defenses on the website and that's affecting legitimate users. No I am not aware of any other mediawiki sites with the BadBehaviour extension.
5. Do you have a problem when accessing the Wiki using non-proxy access?
Well I am now on my home network at a fixed IP (through a router) at 125.59.xx.xx and had no problem viewing the site - but Bad Behaviour is preventing me from creating a new user account on the wiki. I do not experience the same problem I had in office when I use my own private Squid server at 202.177.xx.xx to access the wiki, account creation is still blocked though.
6. I must say that something strange appears to be going on if attempting to access the Wiki apparently asks for / access. blink.gif From your experience with the wikimedia software have you any pointers to a solution? Did your IT staff have anything to say?
Since it is apparent from the Bad Behaviour page itself that the bad behavior extension is generating way too many false positives, I think it may be more beneficial if the extension is removed and replaced with other anti-spam measures, for example the ReCaptcha extension developed by UC Berkeley together with some access control customization settings. On the other hand you could try settings Bad Behavior blocking mode to normal, instead of strict I presume you are running. The Bad Behavior extension does not offer any fine tuning of the anti-spam settings, and the documentation is awfully vague and limited: quote
Quote
Strict: Bad Behavior operates in two blocking modes: normal and strict. In normal mode, some checks which could stop spam, but also block certain types of corporate and government users, are disabled. When strict mode is enabled, spam from these sources is blocked, but those users may be blocked as well. It is up to you whether you want to have the government reading your blog, or keep away the spammers.
(Other options are present, but not currently used in the MediaWiki port.)
p.s.
Wikipedia does not use Bad Behavior, instead they use AntiSpoof, a modified ConfirmEdit for links in incoming edits and account creation, SpamBlacklist and Username Blacklist.
7
OESF Wiki / Http Error 400
« on: November 05, 2007, 12:41:57 am »
Since I am on a corporate network I have to use a proxy to access the OESF wiki, however I get the following error message:
Error 400
We're sorry, but we could not fulfill your request for / on this server.
Your proxy server sent an invalid request. Please contact the proxy server administrator to have this problem fixed.
Your technical support key is: cbc6-b2f1-b783-0251
You can use this key to fix this problem yourself.
If you are unable to fix the problem yourself, please contact michael.hubbard at gmail.com and be sure to provide the technical support key shown above.
Clicking the link "fix this problem yourself" leads to the following page
Technical Support
Your request was intercepted by security software which protects the Web site you visited from malicious activity, such as hackers, spam and viruses. We apologize for the inconvenience, but your request matched a profile of suspicious activity. This problem is usually quite easy to fix.
Your computer appears to have sent a request through a proxy server which corrupted the request. Uninstall the proxy server and try again. It is not normally enough to simply disable the proxy server. If you are required to use the proxy server, contact the proxy server administrator for assistance.
This problem may be caused by misconfigured or malfunctioning browser privacy software or personal firewall software. If you use this type of software, turn it off or reconfigure it and try again.
(Example: For Norton Internet Security, you need to disable the Stealth Mode Browsing feature.)
This problem may be caused by viruses or spyware on your computer, or by malicious software that pretends to be anti-virus or anti-spyware software. Ensure that you have REAL anti-virus and anti-spyware software on your computer, that they are kept up-to-date, and that you have run a full system scan using each tool. Once your system is cleaned of viruses and spyware, please try your request again.
The free Google Pack provides trustworthy anti-virus and anti-spyware software.
If the above suggestions fail to resolve the problem, click Back and contact the e-mail address you were given for further assistance.
----
I can access the OESF forum (which is what I am currently doing) without any problems.
Error 400
We're sorry, but we could not fulfill your request for / on this server.
Your proxy server sent an invalid request. Please contact the proxy server administrator to have this problem fixed.
Your technical support key is: cbc6-b2f1-b783-0251
You can use this key to fix this problem yourself.
If you are unable to fix the problem yourself, please contact michael.hubbard at gmail.com and be sure to provide the technical support key shown above.
Clicking the link "fix this problem yourself" leads to the following page
Technical Support
Your request was intercepted by security software which protects the Web site you visited from malicious activity, such as hackers, spam and viruses. We apologize for the inconvenience, but your request matched a profile of suspicious activity. This problem is usually quite easy to fix.
Your computer appears to have sent a request through a proxy server which corrupted the request. Uninstall the proxy server and try again. It is not normally enough to simply disable the proxy server. If you are required to use the proxy server, contact the proxy server administrator for assistance.
This problem may be caused by misconfigured or malfunctioning browser privacy software or personal firewall software. If you use this type of software, turn it off or reconfigure it and try again.
(Example: For Norton Internet Security, you need to disable the Stealth Mode Browsing feature.)
This problem may be caused by viruses or spyware on your computer, or by malicious software that pretends to be anti-virus or anti-spyware software. Ensure that you have REAL anti-virus and anti-spyware software on your computer, that they are kept up-to-date, and that you have run a full system scan using each tool. Once your system is cleaned of viruses and spyware, please try your request again.
The free Google Pack provides trustworthy anti-virus and anti-spyware software.
If the above suggestions fail to resolve the problem, click Back and contact the e-mail address you were given for further assistance.
----
I can access the OESF forum (which is what I am currently doing) without any problems.
8
OESF Announcements / Whats Needs To Be Fixed?
« on: September 27, 2007, 03:45:14 am »
Since you are now running MediaWiki 1.11.0, I strongly recommend (again) the recaptcha extension. (http://recaptcha.net)
It's really easy to install and with the default setting you can sit back and watch the spammers try hopelessly.
It's really easy to install and with the default setting you can sit back and watch the spammers try hopelessly.
9
Zaurus - pdaXrom / Want Compiled Thread?
« on: July 20, 2007, 11:42:36 am »Quote
Well, 2.2.0 - doesn't compile as it requires QPE headers, which obviously pdaX doesn't have
Should I try 2.1.0 or it will be the same?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=165197\"][{POST_SNAPBACK}][/a][/div]
It will be the same. However I am pretty sure I have not changed anything in the code that will require additional QPE header files. Would you mind generating a new Makefile with the Textreader.pro inside the source tar, and add the __FOR_QT__ directive in it?
10
Zaurus - pdaXrom / Want Compiled Thread?
« on: July 19, 2007, 10:53:32 am »
I have added some new features* (and at the same time merged wellswang's fixes) to justreader and compiled it for the Cacko / Sharp rom, however I do not have the cross compilation tools to compile for the pdaxrom. Can someone compile it for me?
The sources are at:
http://168weedon.com/zaurus/justreader_2.2.0.tar.gz
http://168weedon.com/zaurus/justreader_2.1.0.tar.gz
* e.g. automatic bookmarking, which records your reading progress for each file, and jumps to that position every time you open the same file even if you have closed justreader or opened other files (for details check the CHANGES file in the source)
The sources are at:
http://168weedon.com/zaurus/justreader_2.2.0.tar.gz
http://168weedon.com/zaurus/justreader_2.1.0.tar.gz
* e.g. automatic bookmarking, which records your reading progress for each file, and jumps to that position every time you open the same file even if you have closed justreader or opened other files (for details check the CHANGES file in the source)
11
C1000/3x00 General discussions / What's With The Sound Quality?
« on: July 18, 2007, 01:31:49 am »
The new compiled kernel runs perfectly on my Cacko C3200. I used the FastFPE-cachedfb version and noticed some performance improvement. I am going to compare it with another machine with the same config with the stock kernel to see if there's any significant difference.
12
Software / Qpegps 0.9.3 Released
« on: July 16, 2007, 10:57:04 am »
Thank you ztep for all your good work. I am using 0.9.3.1 with a map that constitute of 180 1000x1000 gifs on my C3200 with Cacko 1.23 without any problems.
However when I install and try to run it on a friend's machine with the exact same hardware and rom and more or less the same config, it fails to start up, without any error message even when started in console.
When started in console it looked like this:
$ qpegps
Display size = 480x640
$
and then nothing happens
While in my (working) machine it looked like:
$ qpegps
Display size = 480x640
and then the qt application starts up.
I've tried starting as root and as the user zaurus,
result from ldd /home/QtPalmtop/bin/qpegps is exactly the same as my machine
also sudo find / | grep gps shows the same thing as well.
I even tried copying the qpegps*.conf from my Settings directory to my friend's directory and still it wouldn't work. Does anyone have any idea?
However when I install and try to run it on a friend's machine with the exact same hardware and rom and more or less the same config, it fails to start up, without any error message even when started in console.
When started in console it looked like this:
$ qpegps
Display size = 480x640
$
and then nothing happens
While in my (working) machine it looked like:
$ qpegps
Display size = 480x640
and then the qt application starts up.
I've tried starting as root and as the user zaurus,
result from ldd /home/QtPalmtop/bin/qpegps is exactly the same as my machine
also sudo find / | grep gps shows the same thing as well.
I even tried copying the qpegps*.conf from my Settings directory to my friend's directory and still it wouldn't work. Does anyone have any idea?
13
C1000/3x00 General discussions / What's With The Sound Quality?
« on: July 16, 2007, 05:08:16 am »Quote
I can provide compiled kernels for Cacko and Sharp ROM only.
...
My current kernel merges the latest Tetsu with the latest Cacko patches and adds some additional features. So perhaps this would be useable with pdaXii13 too? I'll let you know once I have it set up.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164943\"][{POST_SNAPBACK}][/a][/div]
As a C3200 Cacko user, I would appreciate greatly if you can release your current compiled kernel.
14
Sharp ROMs / Wpa-gui Backported To Sharprom
« on: July 13, 2007, 12:04:39 pm »
I have prepared an ipkg.
http://168weedon.com/zaurus/wpa_gui_0.5.6_arm.ipk
By installing this ipkg, your existing /etc/wpa_supplicant.conf will be backed up at /etc/wpa_supplicant.conf.bak, and a "default" wpa_supplicant.conf will be created.
The gui itself is not capable of doing much... it can connect to wpa_supplicant and monitor some of its status. I cannot get the modify bit to work too, modifying directly wpa_supplicant.conf is probably the faster way to make wpa work on zaurus.
I can't compile it on my zaurus, otherwise I would have delve deeper into the code.
Installed together with the ipk is also a script wpa_sup.sh that starts wpa_supplicant, use at your own risk.
http://168weedon.com/zaurus/wpa_gui_0.5.6_arm.ipk
By installing this ipkg, your existing /etc/wpa_supplicant.conf will be backed up at /etc/wpa_supplicant.conf.bak, and a "default" wpa_supplicant.conf will be created.
The gui itself is not capable of doing much... it can connect to wpa_supplicant and monitor some of its status. I cannot get the modify bit to work too, modifying directly wpa_supplicant.conf is probably the faster way to make wpa work on zaurus.
I can't compile it on my zaurus, otherwise I would have delve deeper into the code.
Installed together with the ipk is also a script wpa_sup.sh that starts wpa_supplicant, use at your own risk.
15
Sharp ROMs / Wpa-gui Backported To Sharprom
« on: July 12, 2007, 03:45:33 am »
There is no ipk but a compiled binary file for wpa-gui is in the source package. All you need to do is copy it to your bin path.
I am still trying to get it to connect with wpa-supplicant under Cacko 1.23 tho.
I am still trying to get it to connect with wpa-supplicant under Cacko 1.23 tho.
Pages: [1] 2