Extension talk:PageProtectionPlus/Installation Guide
Any user names refer to users of that site, who are not necessarily users of MediaWiki.org (even if they share the same username).
CipherSuite - ASN tag value[edit]
Q: I receive the following error message (on a german wiki), after installing PPP when trying to edit any page or trying to view a page with a protected part (via PageProtection)
Strona zabezpieczona
* Mechanizm szyfrujÄ
cy wykryĹ bĹÄ
d podczas odszyfrowywania chronionej sekcji:
CipherSuite: error while calling routine get_key_id for crypto-engine PEAR/Crypt_RSA: wrong ASN tag value: 0x04. Expected 0x02 (INTEGER)
ZurĂźck zu Hauptseite.
A: The ASN bad value for tag is mostly caused by the known bug. Workaround requires you to fix one file which belongs to PEAR/Crypt_RSA package. Solution is described in Installation Guide.
BCMath[edit]
Q: I only have bcmath available to me. Why is bcmath to be avoided? --136.152.168.147 18:06, 27 November 2006 (UTC)
A: When using it my machine spent more time to do some operations (that happened when I was using PageProtection previous versions), but if it works for you let us know â I'll remove avoid note from docs.
Execution too long[edit]
Q: I have installed PageProtectionPlus. Unfortunately, It doesn't work for me. It shows error below.
Fatal error: Maximum execution time of 30 seconds exceeded in /data/webssl/wiki/Crypt/RSA/Math/BCMath.php on line 230
Any hints?
I'm using
- MediaWiki 1.8.2
- Crypt_RSA 1.2.0b
- Crypt_Blowfish 1.1.0RC1
A: This probably occurs while generating RSA key. It is a switch called max_execution_time in your php.ini file, that should be increased (for example to 150). It usualy takes a few seconds up to one or two minutes (depending on CPU) to generate key pair. My sugestion is to increase the execution timeout in php.ini if you have access to it â you may then recover the default value after RSA keys will generate.
If you do not have access to php.ini try to put some PHP code around the line 230 of BCMath.php, which will cause the time limit for execution to be temporarily longer.
For more info see: http://www.zend.com/manual/ref.info.php and http://www.zend.com/manual/function.set-time-limit.php
A: It may also occur because of using BCMath. Use big_int PHP's package/extension instead by compiling and installing extension located at [[1]]
2nd edit breaks <protect>[edit]
In my installation, whenever I edit a page which has a <protect> block in it, it seems to lose the ability to decrypt the previously encrypted section. Instead, it'll simply spit out the key/encrypted text when you're permitted to access it, and the usual <ProtectedSite> when you can't. This happens every single time, but only to <protect> blocks that are not in the portion of the page I'm editing (assuming I'm just editing a section). This is very annoying, but I don't understand how PPP works enough to try and fix it. Has anyone else encountered this? Any solutions? --71.224.196.239 06:59, 14 February 2007 (UTC)
On my installation I have got the same problem. Please advice!!!
I discovered the same behavior since I updated our WIKI from PageProtection to PageProtectionPlus 2.3b. It would be a great help if someone could fix that problem soon. Thanks in advance. (Config: MW 1.9.2, Windows Server 2003, PHP 5.1.2, MySQL 5.0.20-nt) --Chrislee 00:34, 28 December 2007 (UTC)
Problem With FCKEditor[edit]
When i use the fckeditor in a page that use PPP i got the encrypted page, event the tag __NORICHEDITOR__ cannot bypass the problem, i have to comment the line that load FCKeditor in LocalSettings to edit ppp pages. I don't need FCKeditor to edit the page encrypted but some user need it to edit normal page. Does somebody already fixed this? thanks
Note that the above conversation may have been edited or added to since the transfer. If in doubt, check the edit history.
Installation on Virtual Hosting[edit]
I have a web host that gives me SSH access, but I am limited to a directory on (probably a virtual) server. Consequently, I do not have access to the standard dpkg, aptitude, apt-get, etc. Is it still possible to install this extension?