my freedom\nhaven<\/a>.\nYou can also drop me an instant message on \"hysseo\" at zemarmot.net.<\/p>\n\nHave a nice life!<\/p>\n\n\n
The easy way<\/strong> is via your installed Wordpress's administration pages:<\/p>\n\n\n- Click
Plugins<\/code> > Add New<\/code>;<\/li>\n- Search for
xmpp-auth<\/code>;<\/li>\n- Find it in the displayed list;<\/li>\n
- Click
Install Now<\/code>.<\/li>\n<\/ol>\n\nAlternatively<\/strong>, here is the old \"manual\" version:<\/p>\n\n\n- Upload the plugin archive to wp-content\/plugins\/<\/em> directory on your Wordpress installation;<\/li>\n
- Uncompress it by keeping it in its own sub-directory called xmpp-auth\/<\/em>;<\/li>\n
- Activate the plugin through the 'Plugins' menu in Wordpress;<\/li>\n
- Configure the plugin through the appearing sub-menu
XMPP Authentication<\/code>\nunder the Plugins<\/code> menu;<\/li>\n- When aknowledging the configuration by pressing the
Update<\/code> button, login\nwill be tested (a connection will be attempted). If anything is wrong with\nyour configuration, you will be immediately informed.<\/li>\n<\/ol>\n\nOnce installed<\/strong>, I would suggest to modify the configuration in Settings<\/em> >\nDiscussion<\/em> > uncheck Comment author must fill out name and e-mail<\/em> as they\nwill be verified by XMPP (but the fields will stay if the user wants to add\nthem in).<\/p>\n\nAlso the new comment field (for JID) is automatically displayed if you use a\nrecent theme (because it uses a function newly added since 3.0). If you don't\nsee the new field after activating, don't panick. 4 solutions:<\/p>\n\n
\n- the simpler: use a more recent theme. The default twentyten<\/em> and\ntwentyeleven<\/em> will work perfectly without doing anything;<\/li>\n
- if you don't want to change your theme, try to contact the theme writers\nand ask them if they could not support the generic (and now \"adviced\")\ncomment_form() feature (they will understand);<\/li>\n
- you know PHP\/HTML and want to do it fast: simply check the file\ncomments.php of your theme. and either replace the whole form by this\nsimpler function:
<?php comment_form(); ?><\/code> yourself;<\/li>\n- or if you want to do it manually, add the following code (can be modified,\nbut what matters obviously is the id of the input field):<\/li>\n<\/ol>\n\n
*\n \n <\/p>\n\n
My advice is obviously<\/strong> to go for the first and the second solutions. The\nthird one is really when you want to do this fast (but still you should report\nthis to the theme writers for them to update upstream) and the fourth is a\nlast resort if you have some very atypical comment form.<\/p>\n\ndependencies<\/h4>\n\n\nPHP > 5.1.0 (for function stream_socket_enable_crypto<\/em>).<\/p><\/li>\nexpat<\/strong> library to parse XML (enabled with the --with-xml<\/code>\noption of the php compilation).<\/p><\/li>\n<\/ul>\n\nNote for gentoo users<\/em>: you must set the 'xml' USE flag.<\/p>\n\n\nOpenSSL<\/strong> (> 0.9.6) must be installed on the server and PHP must be built\nwith --with-openssl<\/code>.<\/p><\/li>\nOPTIONAL<\/em>: if the plugin is installed on a BSD (Mac included),\nin order to use the SRV records on the admin JID, which is the correct way of\nresolving the server and port addresses for a domain, the PEAR<\/em> extension\nNET_DNS<\/strong> must be installed: pear install NET_DNS<\/code> (Note that it will ask\nto have php compiled with mhash<\/code> option).\nIf it is installed on Windows, it is not anymore useful if you have PHP\n5.3.0 or later installed (under this version of PHP, you should also install\nthe NET_DNS extension to benefit SRV records).\nLinux servers do not need this extension to have SRV.<\/p><\/li>\n<\/ul>\n\nNote for gentoo users<\/em>: you must set the 'mhash' USE flag.<\/p>\n\nWorking Platforms<\/h4>\n\n
This script has been tested only currently on Wordpress 3.2.1 up to Wordpress\n3.2.1 with PHP 5.3.5 up to PHP 5.3.8, running on a GNU\/Linux 64 bits (Gentoo\nLinux).\nHopefully it should work with other software versions (not for PHP4, because\nof the TLS feature which is PHP5 specific. Yet if you are really interested\ninto PHP4 compatibility and if TLS is not required for your connection, just\nask me, I will try to make a compatibility layer), but I cannot guarantee.\nTell me please if you tried this successfully with another configuration so\nthat I update the known working platforms list.<\/p>\n\n
At the opposite, if you find a bug or encounter an issue on some\nconfiguration, don't hesitate to tell me, and I will try and fix it.<\/p>\n\n\n
\n- Will it work with any web browser and any IM client?<\/dt>\n
On the web side, the XEP-0070 uses RFC-2617, which is a common way to\nauthenticate to websites. On the XMPP-side, RFC-6120 and XEP-0070 have a nice\nway for clients which do not understand a given feature for falling back into\na message to answer, as though it was a discussion.<\/p>\n\n
So hopefully it \"should\" work in most case with not-too broken web browser or\nIM client.\nFor IM clients, it should work (tested or reported by someone) with Psi,\nGajim, OneTeam\u2026 In particular, it is known not to work with Pidgin, Adium,\nSwift, and the GoogleMail web interface.<\/p><\/dd>\n
- I get \"Warning: require_once(Auth\/SASL\/DigestMD5.php)\" or another similar warning<\/dt>\n
You should check the Installation\/dependencies section. Some PHP modules are\nnecessary. If you are administrator or have flexible administrators, this will\nbe very easily fixable (follow my instructions in the \"dependencies\" section).\nIf you use a public service, which did not install these dependencies by\ndefault, and where you cannot have anything installed, then I am sorry but my\nplugin unfortunately won't work for you (actually for PEAR modules, you may\nadd them by hand, as they are pure PHP. But you would need to be developers\nfor the manipulation).<\/p><\/dd>\n
- When configuring, I get: \"Authentication failure: TLS negotiation failed.\"<\/dt>\n
This means that your server uses TLS (and that's good!) but simply I did not\npackage the certificate of their CA into my plugin. Please just tell me (see\n\"Contacts\" section) your server, I will check the CA and if it is an\nacceptable one, I will add its certificate.<\/p>\n\n
It may also mean that the server certificate is self-signed, which is really not\nsecure. If many servers are this way, I may consider adding an option to\nforce such connection, but I would prefer not. If this happens to you, I\nwould rather suggest you to change the server of your bot for one where\nsecurity matters.<\/p><\/dd>\n
- The new \"JID\" field does not appear in the comment form!<\/dt>\n
You most probably use an outdated theme which does not use recent Wordpress\nfeatures about commenting (since 3.0). This is not a blocker. See the bottom\nof the \"Installation\" tab. I provide the solutions to this issue.<\/p><\/dd>\n\n<\/dl>\n\n\n
0.6<\/h4>\n\n\n- Fix comment validation.<\/li>\n
- Comment validation through XMPP is now marked as \"experimental\".\nThough still functional, I find the user experience crappy. I will want to\nreview this deeply before considering it in release state.<\/li>\n
- Comment validation times out at 50 sec (was 30).<\/li>\n
- Transaction IDs are 6 characters. This makes them easier to copy, even on\nsmaller virtual keyboard (for instance to validate on your personal smartphone\na login made on a third-party untrusted machine).<\/li>\n<\/ul>\n\n
0.5<\/h4>\n\n\n- Update SASL lib to Auth_SASL2 0.1.0.<\/li>\n
- Fix Cacert root certificate.<\/li>\n
- Add Let's Encrypt root certificate.<\/li>\n
- Improving\/experimenting the protocole from XEP-0070. It should be more\nuser-friendly, while still staying secure.<\/li>\n<\/ul>\n\n
0.4<\/h4>\n\n\n- When login is disabled, login page look is not modified.<\/li>\n
- When comments is disabled, I still display the JID field, but simply don't\nprocess anything and without the '*' of mandatory fields.<\/li>\n
- Localization prepared and French localization available.<\/li>\n
- DNS results are now cached. I use the ttl of records (maximum 1 week, as\nproposed in RFC-1035) and reorder cached data using failure and success\nknowledge.<\/li>\n
- PEAR Auth_SASL coded is included in the plugin, hence the dependency is no more.<\/li>\n
A patch has been sent upstream for SCRAM support.<\/p><\/li>\n
After many years of inactivity, I fixed all the code and tested it against\nWordpress 4.4.1.<\/p><\/li>\n
- Root certificates were also updated.<\/li>\n<\/ul>\n\n
0.3<\/h4>\n\n\n- Profile page configuration: per-user choice to disable password, IM\nauthentication, or use both.<\/li>\n
- IPv6 support and better DNS integration.<\/li>\n
- The core XMPP library has been rewritten in a much more robust, hence secure\nAPI. The current version had been started in 2008. My first XMPP experiment\nthat I used for the plugin Jabber Feed (that I will probably soon merge with\nthe current plugin) and the API was not very nice and could break more\neasily on some unexpected outputs.<\/li>\n<\/ul>\n\n
0.2<\/h4>\n\n\n- Admins have now possibility to deactivate the plugin on a per-feature basis.<\/li>\n
- Experimental component support.<\/li>\n
- \"Jabber \/ Google Talk\" in profile renamed to \"Standard IM\".<\/li>\n<\/ul>\n\n
0.1.5<\/h4>\n\n\n- TLS certificates were not properly configured.<\/li>\n
- Various fixes.<\/li>\n<\/ul>\n\n
0.1<\/h4>\n\n
Initial Release.\nThe plugin can be used to login as a user, or post comments as an unsubscribed\nvisitor.<\/p>","raw_excerpt":"Allows users to authenticate without password via XMPP and for visitors to be filtered by XMPP verification.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/szl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/14288","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/szl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/szl.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/szl.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=14288"}],"author":[{"embeddable":true,"href":"https:\/\/szl.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/jehan"}],"wp:attachment":[{"href":"https:\/\/szl.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=14288"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/szl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=14288"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/szl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=14288"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/szl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=14288"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/szl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=14288"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/szl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=14288"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}