<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>El Tramo &#187; Openfire</title>
	<atom:link href="http://el-tramo.be/blog/tag/openfire/feed" rel="self" type="application/rss+xml" />
	<link>http://el-tramo.be</link>
	<description>Remko Tronçon&#039;s Homepage</description>
	<lastBuildDate>Fri, 11 Jun 2010 19:08:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Migrating from Openfire to Prosody</title>
		<link>http://el-tramo.be/blog/openfire-to-prosody-migration</link>
		<comments>http://el-tramo.be/blog/openfire-to-prosody-migration#comments</comments>
		<pubDate>Fri, 03 Jul 2009 07:07:19 +0000</pubDate>
		<dc:creator>Remko Tronçon</dc:creator>
				<category><![CDATA[Jabber]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Openfire]]></category>
		<category><![CDATA[Prosody]]></category>
		<category><![CDATA[XMPP]]></category>

		<guid isPermaLink="false">/?p=426</guid>
		<description><![CDATA[Because Openfire has been hogging too much of my limited el-tramo.be server resources lately, and because I don’t need a beast of an XMPP server for only 2 users, I decided to replace it by the lightweight Prosody. The migration went flawless, with the help of two tools: Sleek Migrate, and a Prosody XEP-0227 Importer.

First [...]]]></description>
			<content:encoded><![CDATA[<p>Because <a href="http://www.igniterealtime.org/projects/openfire/index.jsp">Openfire</a> has been hogging too much of my limited <a href="http://el-tramo.be">el-tramo.be</a> server resources lately, and because I don’t need a beast of an XMPP server for only 2 users, I decided to replace it by the lightweight <a href="http://prosody.im/">Prosody</a>. The migration went flawless, with the help of two tools: <a href="http://www.kismith.co.uk/wordpress/index.php/2008/11/30/sleek-migrate/">Sleek Migrate</a>, and a <a href="/git/xep227-to-prosody">Prosody XEP-0227 Importer</a>.</p>
<p><span id="more-426"></span></p>
<p>First of all, I used Sleek Migrate to retrieve the roster (and other) data from the server, and store it in the standard <a href="http://xmpp.org/extensions/xep-0227.html">XEP-0227</a> format. I extended the tool a bit such that it supports Openfire’s User Import/Export format, a format generated by an <a href="http://www.igniterealtime.org/projects/openfire/plugins/userimportexport/readme.html">Openfire plugin</a> that is distributed with the server software by default. Using this format as input for Sleek Migrate avoids the need to create a user file manually. The changes I made to Sleek Migrate are currently available from <a href="/git/sleekmigrate">my Git repository</a>, awaiting to be pushed to the main repository.</p>
<p>I then wrote a short script that populates the Prosody data dir with the server data from the XEP-0227 XML file. Currently, the script only generates roster and account data, but adding <a href="http://xmpp.org/extensions/xep-0054.html">vCard</a> and <a href="http://xmpp.org/extensions/xep-0049.html">Private XML Storage</a> (used amongst others to store <a href="http://xmpp.org/extensions/attic/xep-0048-1.0.html">MUC bookmarks</a>) should not be very hard. Until Prosody creates a native XEP-0227 importer, you can get the script from <a href="/git/xep227-to-prosody">my Git repository</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://el-tramo.be/blog/openfire-to-prosody-migration/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Customizable XEP-0076 implementation</title>
		<link>http://el-tramo.be/blog/malicious-stanzas</link>
		<comments>http://el-tramo.be/blog/malicious-stanzas#comments</comments>
		<pubDate>Sun, 01 Apr 2007 14:30:04 +0000</pubDate>
		<dc:creator>Remko Tronçon</dc:creator>
				<category><![CDATA[Jabber]]></category>
		<category><![CDATA[Openfire]]></category>
		<category><![CDATA[Psi]]></category>
		<category><![CDATA[XMPP]]></category>

		<guid isPermaLink="false">http://el-tramo.be/blog/malicious-stanzas</guid>
		<description><![CDATA[It is time for us to be honest: the reason Psi has not had a release in the past year and a half is because we have secretly been working on one of the most controversial and least implemented features in the Jabber world: XEP-0076 (Malicious Stanzas). We have allocated two full-time developers for achieving [...]]]></description>
			<content:encoded><![CDATA[<p>It is time for us to be honest: the reason Psi has not had a release in the past year and a half is because we have secretly been working on one of the most controversial and least implemented features in the Jabber world: <a href="http://www.xmpp.org/extensions/xep-0076.html">XEP-0076 (Malicious Stanzas)</a>. We have allocated two full-time developers for achieving this: <a href="http://machekku.uaznia.net/">Machekku</a> has done the groundbreaking work, implementing the main processing loop, statistic gathering, and user interfaces for this type of stanzas, whereas I have been concentrating mostly on backend issues. Although our work is still in a highly experimental stage, we decided to release the full source code in order to get useful feedback from the community. Besides a Psi implementation, we also provide an Openfire server-side implementation for malicious stanza tagging as an extension of the content filter, targeted at fixing non-XEP-0076-compliant behavior of entities.</p>
<p><span id="more-64"></span> You can find Machekku&#8217;s and my Psi work <a href="http://machekku.uaznia.net/xmpp/psi/patches/#xep_0076_scanner">here</a> and <a href="http://el-tramo.be/files/psi/xep-0076_send.diff">here</a> respectively. Apply these patches to a clean development version of Psi. In order to use this work, please modify the <tt>&lt;evil&gt;</tt> section of your <tt>options.xml</tt> accordingly. XEP-0076 statistics can be found in the options dialog, in a separate tab.</p>
<p>The patch against the latest development version of Openfire can be found <a href="http://el-tramo.be/files/openfire/xep-0076.diff">here</a>. This will add an extra checkbox to the content filter pane, allowing messages to be tagged as malicious.</p>
<p style="text-align: center"><img src="http://machekku.uaznia.net/xmpp/psi/screens/antievil.png" alt="" /></p>
]]></content:encoded>
			<wfw:commentRss>http://el-tramo.be/blog/malicious-stanzas/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>vCard-based Extended Presence Plugin</title>
		<link>http://el-tramo.be/blog/vcardextpres</link>
		<comments>http://el-tramo.be/blog/vcardextpres#comments</comments>
		<pubDate>Tue, 24 Oct 2006 12:47:13 +0000</pubDate>
		<dc:creator>Remko Tronçon</dc:creator>
				<category><![CDATA[Jabber]]></category>
		<category><![CDATA[Google Talk]]></category>
		<category><![CDATA[Openfire]]></category>
		<category><![CDATA[Psi]]></category>
		<category><![CDATA[XMPP]]></category>

		<guid isPermaLink="false">http://el-tramo.be/blog/vcardextpres</guid>
		<description><![CDATA[After gathering dust for a few months in some deep and dark corner of my hard disk, my vCard-based Extended Presence plugin for Openfire is now publicly available here.
What this plugin does is add avatar (XEP-0153) and nickname (XEP-0172) information from your vCard to all your outgoing presence packets. This allows clients that do not [...]]]></description>
			<content:encoded><![CDATA[<p>After gathering dust for a few months in some deep and dark corner of my hard disk, my vCard-based Extended Presence plugin for Openfire is now publicly available <a href="http://el-tramo.be/files/openfire/vcardextpres.jar">here</a>.</p>
<p><span id="more-52"></span>What this plugin does is add avatar (<a href="http://www.xmpp.org/extensions/xep-0153.html">XEP-0153</a>) and nickname (<a href="http://www.xmpp.org/extensions/xep-0172.html">XEP-0172</a>) information from your vCard to all your outgoing presence packets. This allows clients that do not support setting of vCard-based avatars (e.g. Psi) to still broadcast this information to contacts, such that clients supporting this avatar protocol (basically almost all clients, including the upcoming Psi 0.11) can still see your avatar. This server-side approach is basically what Google Talk does as well. For nickname support, this adds nickname information to presence subscription requests, such that clients supporting the protocol can present the request in a nicer way.</p>
<p>To use this plugin, simply put it in the <tt>plugins/</tt> dir of your Openfire installation. It should then be listed in the Plugins pane of the admin console. You can then change the settings of the plugin (enable/disable avatars/nicknames) from the first panel in the admin console.</p>
]]></content:encoded>
			<wfw:commentRss>http://el-tramo.be/blog/vcardextpres/feed</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
	</channel>
</rss>
