<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    
    <title>Dr. Christopher Kunz</title>
    <link>http://www.christopher-kunz.de/</link>
    <description>Just my € 0.02</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.6.2 - http://www.s9y.org/</generator>
    
    

<item>
    <title>Roundcube, SQLite and PHP 5.4 </title>
    <link>http://www.christopher-kunz.de/archives/285-Roundcube,-SQLite-and-PHP-5.4.html</link>
            <category>PHP</category>
    
    <comments>http://www.christopher-kunz.de/archives/285-Roundcube,-SQLite-and-PHP-5.4.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=285</wfw:comment>

    <slash:comments>7</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=285</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt;After updating PHP to version 5.4 (with mixed success), I am still cleaning up the fallout peu à peu. (See all entries of this mini-series &lt;a href=&quot;http://www.christopher-kunz.de/plugin/tag/php+5%FF4%FF0&quot;&gt;here&lt;/a&gt;) During my holidays, the fact that my Roundcube installation is also broken bit me (I needed quick access to my flight information and the e-mail was not cached on my iPhone). Today, I tried to fix it.&amp;#160;&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;I was using Roundcube 0.8-beta with the SQLite backend, and it seemed the database was no longer accessible. SQLite is a bit picky with its permissions, so I checked that first, but the server log said:&amp;#160;&lt;/p&gt; &lt;br /&gt;
&lt;p&gt; [Wed Aug 08 19:06:33 2012] [error] MDB2 Error: not found (-4): [Error message: extension sqlite is not compiled into PHP]\n&lt;br /&gt;&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;Whoopsydaisies, is there an extension missing? I duly checked my PHP for SQLite support and sure enough, the sqlite3 extension was loaded. But alas, Roundcube uses the outdated sqlite2 API, so it fails. I tried updating to Roundcube 0.8.0, but to no avail. After a while of googling, I found a bug in the Debian tracker that essentially said &amp;#8220;Roundcube&amp;#8217;s fault for using outdated code&amp;#8221; and led to a bug in the Roundcube bug tracker (&lt;a href=&quot;http://trac.roundcube.net/ticket/1488332&quot;&gt;#1488332&lt;/a&gt;). This one was marked as fixed 6 days ago (August 08th), so I downloaded the latest nightly, marked 20120812. This nightly &lt;strong&gt;did not fix the issue&lt;/strong&gt;, either. &lt;/p&gt; &lt;br /&gt;
&lt;p&gt;So either there&amp;#8217;s currently &lt;strong&gt;no way to use Roundcube with SQLite and PHP 5.4&lt;/strong&gt; or I have missed something. Does anyone have a hint for me?&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;(PS: The current nightly has an awesome new UI, so the update wasn&amp;#8217;t for naught. And I have switched to MySQL for the time being.)&lt;br /&gt;&lt;/p&gt; 
    </content:encoded>

    <pubDate>Tue, 14 Aug 2012 09:34:08 +0200</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/285-guid.html</guid>
    <category>PHP 5.4.0</category>
<category>Roundcube</category>
<category>SQLite</category>
<category>update</category>

</item>
<item>
    <title>Owncloud iOS app and SSL connections</title>
    <link>http://www.christopher-kunz.de/archives/283-Owncloud-iOS-app-and-SSL-connections.html</link>
    
    <comments>http://www.christopher-kunz.de/archives/283-Owncloud-iOS-app-and-SSL-connections.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=283</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=283</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt;Starting today, the iOS app for Owncloud is available in the Apple appstore. It is not a universal app and currently, only an iPhone version is available. That is a pity, but not a showstopper. What proved to be a hindrance, though: &lt;strong&gt;The iOS App for Owncloud does not support non-CA-signed SSL certificates&lt;/strong&gt;. If you use a certificate that is not signed by a CA known to the iOS certificate bundle, the connection fails with the rather unspecific error &amp;#8220;Server Not Found - A server with the specified hostname could not be found.&amp;#8221;&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;It seems that there is currently no workaround for this. I have tried installing the self-signed certificate on my iPad (by mailing the PEM to myself and then opening the attachment on the iPad) but to no avail. Maybe this will be fixed in future versions or maybe it&amp;#8217;s even a &amp;#8220;feature&amp;#8221;. &lt;/p&gt;&lt;br /&gt;
&lt;p&gt;Update: An updated version has subsequently been released in the App Store to fix this issue. It also fixes screen resolution issues on the iPad (i.e. makes the Owncloud app a universal app).&lt;br /&gt;&lt;/p&gt; 
    </content:encoded>

    <pubDate>Wed, 01 Aug 2012 09:39:09 +0200</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/283-guid.html</guid>
    
</item>
<item>
    <title>Debian Wheezy: Courier auth fails </title>
    <link>http://www.christopher-kunz.de/archives/282-Debian-Wheezy-Courier-auth-fails.html</link>
    
    <comments>http://www.christopher-kunz.de/archives/282-Debian-Wheezy-Courier-auth-fails.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=282</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=282</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt;I had an issue with Courier stopping to work on Debian Wheezy. This seems to be because Courier cannot access one of Postfix&amp;#8217;s named pipes for SASL. Just restarting Postfix didn&amp;#8217;t work. I had to issue&amp;#160;&lt;/p&gt;&lt;br /&gt;
&lt;p&gt;&lt;font face=&quot;courier new,courier,monospace&quot;&gt;killall -9 gam_server&lt;/font&gt;&lt;/p&gt;&lt;br /&gt;
&lt;p&gt; to effectively stop Postfix&amp;#8217;s file alteration monitor, the gamin server. After a restart everything worked again. &lt;/p&gt;&lt;br /&gt;
&lt;p&gt;HTH anyone and I also hope I won&amp;#8217;t forget about this blog entry when I next have the problem.&lt;br /&gt;&lt;/p&gt; 
    </content:encoded>

    <pubDate>Thu, 10 May 2012 08:38:24 +0200</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/282-guid.html</guid>
    
</item>
<item>
    <title>PHP 5.4.3 and 5.3.13 fix several security issues</title>
    <link>http://www.christopher-kunz.de/archives/281-PHP-5.4.3-and-5.3.13-fix-several-security-issues.html</link>
            <category>PHP</category>
    
    <comments>http://www.christopher-kunz.de/archives/281-PHP-5.4.3-and-5.3.13-fix-several-security-issues.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=281</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=281</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt;The PHP team has announced PHP 5.4.3 and 5.3.13, fixing two separate security issues.&lt;/p&gt; &lt;br /&gt;
&lt;ul&gt; &lt;br /&gt;
&lt;li&gt;CVE-2012-2311 and CVE-2012-1823 are both fixed now. These are the CVE numbers for the PHP-CGI bug that has been announced by &lt;a href=&quot;http://eindbazen.net/2012/05/php-cgi-advisory-cve-2012-1823/&quot;&gt;Eindbazen&lt;/a&gt; last week, and extensively covered by myself in various posts. &lt;br /&gt;&lt;/li&gt; &lt;br /&gt;
&lt;li&gt;In addition, CVE-2012-2329 has been fixed, another issue in PHP-CGI. This was a heap overflow triggered by specially crafted HTTP headers and a script executing apache_request_headers(). &lt;br /&gt;&lt;/li&gt; &lt;br /&gt;
&lt;/ul&gt;I have tested my own exploit against the new version (5.4 only, I have no 5.3 setup) and there does not seem to be a possibility to exploit the vectors opened in CVE-2012-2311 and CVE-2012-1823. These issues seem to be fixed now. &lt;del&gt;I have no exploit code for CVE-2012-2329, so I cannot make a statement if it is fixed yet.&lt;/del&gt; &lt;strong&gt;Update: &lt;/strong&gt;I have tested Georg Wicherski&amp;#8217;s PoC exploit against 5.4.3 and it seems that CVE-2012-2329 is now also fixed. &lt;br /&gt; &lt;br /&gt;
&lt;p&gt;Read the announcement here: &lt;a href=&quot;http://www.php.net/archive/2012.php#id2012-05-08-1&quot;&gt;PHP 5.4.3/5.3.13 release announcement&lt;/a&gt; &lt;/p&gt; &lt;br /&gt;
&lt;p&gt;The download page for &lt;a href=&quot;http://php.net/get/php-5.4.3.tar.gz/from/a/mirror&quot;&gt;PHP 5.4.3 is here&lt;/a&gt;, the download for &lt;a href=&quot;http://php.net/get/php-5.3.13.tar.gz/from/a/mirror&quot;&gt;5.3.13 is over here&lt;/a&gt;.&lt;br /&gt;&lt;/p&gt; 
    </content:encoded>

    <pubDate>Tue, 08 May 2012 21:36:20 +0200</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/281-guid.html</guid>
    <category>bugfix</category>
<category>cgi</category>
<category>CVE-2012-1823</category>
<category>CVE-2012-2311</category>
<category>CVE-2012-2329</category>
<category>exploit</category>
<category>PHP</category>
<category>release announcement</category>
<category>security</category>
<category>vulnerability</category>

</item>
<item>
    <title>Attack against PHP-CGI - DoS, Code disclosure and more...</title>
    <link>http://www.christopher-kunz.de/archives/280-Attack-against-PHP-CGI-DoS,-Code-disclosure-and-more....html</link>
            <category>PHP</category>
    
    <comments>http://www.christopher-kunz.de/archives/280-Attack-against-PHP-CGI-DoS,-Code-disclosure-and-more....html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=280</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=280</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt;There is a new PHP bug that just became public today (leaked accidentially, it seems...). A flaw in the PHP CGI&amp;#8217;s input sanitation process allows attackers to set command-line options via the query string.This behavior seems to be an oversight / misplaced design decision from 2004 and is only exploitable in specific web servers. Apache is one of them...&lt;br /&gt;&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;This opens interesting opportunities. I have blogged about those here: &lt;a href=&quot;http://www.php-security.net/archives/9-New-PHP-CGI-exploit-CVE-2012-1823.html&quot;&gt;New Exploit @ php-security.net&lt;/a&gt;&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;&lt;del&gt;By the way, Suhosin partially mitigates one of the easier remote code execution vectors that are opened through this attack.&lt;/del&gt; Suhosin can be circumvented completely and trivially.&lt;br /&gt;&lt;/p&gt; 
    </content:encoded>

    <pubDate>Thu, 03 May 2012 17:41:20 +0200</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/280-guid.html</guid>
    
</item>
<item>
    <title>Now serving: SPDY </title>
    <link>http://www.christopher-kunz.de/archives/279-Now-serving-SPDY.html</link>
            <category>PHP</category>
    
    <comments>http://www.christopher-kunz.de/archives/279-Now-serving-SPDY.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=279</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=279</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt;(EDIT: mod_spdy seems to cause massive issues with mod_php, so I disabled it again. I am seeing lots of PHP segfaults as soon as I enable mod_spdy - these disappear as soon as it is disabled.) &lt;br /&gt;&lt;/p&gt;&lt;br /&gt;
&lt;p&gt;This website (as long as you access it via &lt;a href=&quot;https://www.christopher-kunz.de&quot;&gt;HTTPS&lt;/a&gt;) is now serving pages with SPDY, Google&amp;#8217;s still-experimental web acceleration protocol. Since SPDY mandates usage of SSL, I am using a CACert certificate to serve up pages. If you want to know why I didn&amp;#8217;t buy a CA-signed certificate, please see this talk for a couple thoughts: &lt;a href=&quot;http://www.christopher-kunz.de/uploads/ckunz_ca_failure.pdf&quot;&gt;SSL and the future of web authentication (PDF)&lt;/a&gt;&lt;br /&gt;&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;The reason this posting lands in the PHP category is that I want to have a playground testing PHP applications with mod_spdy. Currently (and probably also in the future), this machine uses mod_php instead of php_(f)cgi(d) - this is not recommended for interoperation with mod_spdy. To test the real-life impact of the possible thread safety issues, I am using my private pages as a sandbox.&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;&amp;#160;So, please test away. There is a couple of PHP applications here that might or might not work:&lt;/p&gt; &lt;br /&gt;
&lt;ul&gt; &lt;br /&gt;
&lt;li&gt;A recent, PHP 5.4-patched Gallery3 installation is under &lt;a href=&quot;https://gallery.christopher-kunz.de/&quot;&gt;https://gallery.christopher-kunz.de/&lt;/a&gt;&lt;/li&gt; &lt;br /&gt;
&lt;li&gt;A Wordpress installation is here: &lt;a href=&quot;https://absynth.de&quot;&gt;https://absynth.de/&lt;/a&gt;&lt;/li&gt; &lt;br /&gt;
&lt;/ul&gt; &lt;br /&gt;
&lt;p&gt;If you have any comments, especially if you can share success stories about mod_spdy and PHP, or just want to see how SPDY performs, please comment away!&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;Update: You can check if you&amp;#8217;re using SPDY already by looking into the following little page, iframed for your convenience: &lt;a href=&quot;https://www.christopher-kunz.de/pages/spdycheck.html&quot;&gt;SPDY check&lt;/a&gt;&lt;/p&gt; &lt;br /&gt;
&lt;p&gt; &lt;br /&gt;
&lt;iframe src=&quot;http://www.christopher-kunz.de/include/check_spdy.php&quot;&gt;&amp;amp;amp;lt;br /&amp;amp;amp;gt; &amp;amp;amp;lt;/p&amp;amp;amp;gt;&lt;/iframe&gt; &lt;br /&gt;
&lt;/p&gt; &lt;br /&gt;&lt;a href=&quot;http://www.christopher-kunz.de/archives/279-Now-serving-SPDY.html#extended&quot;&gt;Continue reading &quot;Now serving: SPDY &quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Wed, 02 May 2012 16:01:44 +0200</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/279-guid.html</guid>
    <category>apache</category>
<category>certificate</category>
<category>compatibility</category>
<category>google</category>
<category>php</category>
<category>spdy</category>
<category>ssl</category>

</item>
<item>
    <title>Upgrade woes III: Suhosin and PHP 5.4.0</title>
    <link>http://www.christopher-kunz.de/archives/278-Upgrade-woes-III-Suhosin-and-PHP-5.4.0.html</link>
            <category>PHP</category>
    
    <comments>http://www.christopher-kunz.de/archives/278-Upgrade-woes-III-Suhosin-and-PHP-5.4.0.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=278</wfw:comment>

    <slash:comments>4</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=278</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt;&lt;del&gt;To complete the trinity of infamy: There is no Suhosin for PHP 5.4.0 either. &lt;/del&gt;&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;&lt;del&gt;The patch is no longer bundled with distribution PHP. I have fired a mail to i0n1c about this but he seems to be in transit currently. The extension (0.9.33) does not compile with PHP 5.4.0 because of the copious API changes.&amp;#160; &lt;/del&gt;&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;Update: There is now a new version of Suhosin that is compatible with PHP 5.4.0 and 5.4.1. You can download it from &lt;a href=&quot;https://github.com/stefanesser/suhosin&quot;&gt;Stefan Esser&amp;#8217;s Github account&lt;/a&gt; (&lt;a href=&quot;https://github.com/stefanesser/suhosin/tarball/master&quot;&gt;.tar.gz&lt;/a&gt; &lt;a href=&quot;https://github.com/stefanesser/suhosin/zipball/master&quot;&gt;.zip&lt;/a&gt;). It compiles and runs well with PHP 5.4.0-3 (Debian Wheezy).&lt;/p&gt; &lt;br /&gt;
&lt;p&gt; &lt;tt&gt;PHP 5.4.0-3 (cli) (built: Mar 21 2012 20:33:26) &lt;br /&gt;Copyright (c) 1997-2012 The PHP Group&lt;br /&gt;Zend Engine v2.4.0, Copyright (c) 1998-2012 Zend Technologies&lt;br /&gt;&amp;#160;&amp;#160;&amp;#160; with Suhosin v0.9.34-dev, Copyright (c) 2007-2012, by SektionEins GmbH&lt;/tt&gt;&lt;/p&gt;&lt;br /&gt;
Thanks to andro for pointing this out. There is an &lt;a href=&quot;http://php-security.net/archives/8-Suhosin-0.9.34-dev-installation-howto.html&quot;&gt;installation howto over on php-security.net&lt;/a&gt;.&lt;br /&gt; 
    </content:encoded>

    <pubDate>Mon, 02 Apr 2012 15:20:15 +0200</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/278-guid.html</guid>
    <category>php 5.4.0</category>
<category>php-sicherheit</category>
<category>suhosin</category>
<category>wheezy</category>

</item>
<item>
    <title>Upgrade woes II: eAccelerator and PHP 5.4.0</title>
    <link>http://www.christopher-kunz.de/archives/277-Upgrade-woes-II-eAccelerator-and-PHP-5.4.0.html</link>
            <category>PHP</category>
    
    <comments>http://www.christopher-kunz.de/archives/277-Upgrade-woes-II-eAccelerator-and-PHP-5.4.0.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=277</wfw:comment>

    <slash:comments>3</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=277</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt;The &amp;#8220;eAccelerator&amp;#8221; project seems to be in hiatus. There haven&amp;#8217;t been any changes to the downloadable files since 2010 (version 0.9.6.1). With PHP 5.4.0 released and a major bump in the Zend API coming with it, I was not expecting eAccelerator 0.9.6.1 to compile. And sure enough, it fails quite soon into the make process.&amp;#160;&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;eaccelerator.net is an Apache placeholder page, the SF site is not maintained anymore - time to let go.&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;So, no eAccelerator for PHP 5.4.0 (FWIW, anyway...) and onwards.&lt;br /&gt;&lt;/p&gt; &lt;br /&gt;&lt;a href=&quot;http://www.christopher-kunz.de/archives/277-Upgrade-woes-II-eAccelerator-and-PHP-5.4.0.html#extended&quot;&gt;Continue reading &quot;Upgrade woes II: eAccelerator and PHP 5.4.0&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Mon, 02 Apr 2012 15:15:36 +0200</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/277-guid.html</guid>
    <category>eaccelerator</category>
<category>extension</category>
<category>php 5.4.0</category>

</item>
<item>
    <title>Upgrade woes I: Gallery3 and PHP 5.4.0</title>
    <link>http://www.christopher-kunz.de/archives/276-Upgrade-woes-I-Gallery3-and-PHP-5.4.0.html</link>
            <category>PHP</category>
    
    <comments>http://www.christopher-kunz.de/archives/276-Upgrade-woes-I-Gallery3-and-PHP-5.4.0.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=276</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=276</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt;I recently upgraded this machine to Debian Wheezy (mainly to fix odd kernel crash issues that occured a couple times now) and this included a new PHP version. 5.4.0 has been stable for a month now, so I was eager to give it a spin.&amp;#160;&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;&lt;a onclick=&quot;F1 = window.open(&#039;/uploads/Notice-undefined-offset-1-i18n-gallery3-and-php-5.4.0&#039;,&#039;Zoom&#039;,&#039;height=916,width=1049,top=74.5,left=323,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot; href=&quot;http://www.christopher-kunz.de/uploads/Notice-undefined-offset-1-i18n-gallery3-and-php-5.4.0&quot; class=&quot;serendipity_image_link&quot;&gt;&lt;!-- s9ymdb:132 --&gt;&lt;img width=&quot;110&quot; height=&quot;96&quot; src=&quot;http://www.christopher-kunz.de/uploads/Notice-undefined-offset-1-i18n-gallery3-and-php-5.4.serendipityThumb.0&quot; class=&quot;serendipity_image_left&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;Almost all applications worked without any changes, apart from the popular &amp;#8220;Gallery&amp;#8221; script. Gallery3 just stopped working after upgrading to PHP 5.4.0. I maintain a fairly large gallery &lt;a href=&quot;http://gallery.christopher-kunz.de/&quot;&gt;here&lt;/a&gt;, so it was vital for me to keep it running.&lt;/p&gt;&lt;br /&gt;
&lt;p&gt;So, the TL;DR version to fix Gallery3 in Debian Wheezy with PHP 5.4.0: &lt;/p&gt; &lt;br /&gt;
&lt;ul&gt;&lt;br /&gt;
&lt;li&gt;set date.timezone = &amp;lt;your-timezone&amp;gt; in php.ini and restart Apache&lt;br /&gt;&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;comment-out line 530 in gallery3/system/core/Kohana.php&lt;/li&gt;&lt;br /&gt;
&lt;/ul&gt;&lt;br /&gt;
&lt;p&gt;If you see everything twice (all pages are there twice), you have applied the wrong hotfix. Check in the bottom of the long entry for an explanation and a fix.&lt;/p&gt;&lt;br /&gt; &lt;br /&gt;&lt;a href=&quot;http://www.christopher-kunz.de/archives/276-Upgrade-woes-I-Gallery3-and-PHP-5.4.0.html#extended&quot;&gt;Continue reading &quot;Upgrade woes I: Gallery3 and PHP 5.4.0&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Mon, 02 Apr 2012 14:37:25 +0200</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/276-guid.html</guid>
    <category>bugs</category>
<category>debian</category>
<category>gallery</category>
<category>php 5.4.0</category>
<category>upgrade</category>
<category>wheezy</category>

</item>
<item>
    <title>CACert.org Assurance in Gütersloh</title>
    <link>http://www.christopher-kunz.de/archives/275-CACert.org-Assurance-in-Guetersloh.html</link>
    
    <comments>http://www.christopher-kunz.de/archives/275-CACert.org-Assurance-in-Guetersloh.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=275</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=275</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt;&lt;!-- s9ymdb:131 --&gt;&lt;img width=&quot;88&quot; height=&quot;31&quot; class=&quot;serendipity_image_left&quot; src=&quot;http://www.christopher-kunz.de/uploads/cacert1.png&quot; alt=&quot;&quot;  /&gt;Auf Anregung der Kollegen Sebastian Grewing und Philipp Schelkle (die ebenfalls Assurer sind) habe ich mal mein &lt;a href=&quot;http://www.cacert.org/&quot;&gt;CACert&lt;/a&gt;-Konto reaktiviert und mich Assurancemäßig auf den neuesten Stand gebracht. Ich kann nun in Gütersloh mit der vollen Punktzahl assuren. &lt;/p&gt; &lt;br /&gt;
&lt;p&gt;Wer eine Assurance benötigt, kommt einfach zu den üblichen Bürozeiten bei uns vorbei:&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;filoo GmbH&lt;br /&gt;Moltkestraße 25a&lt;br /&gt;33330 Gütersloh&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;Bitte die zwei unterschiedlichen Ausweisdokumente nicht vergessen.&lt;br /&gt;&lt;/p&gt; 
    </content:encoded>

    <pubDate>Mon, 26 Mar 2012 14:04:03 +0200</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/275-guid.html</guid>
    <category>cacert</category>
<category>certificate</category>
<category>ssl</category>
<category>web of trust</category>
<category>x.509</category>

</item>
<item>
    <title>Vortrag auf der Open Source Data Center Conference 2012 (OSDC12)</title>
    <link>http://www.christopher-kunz.de/archives/274-Vortrag-auf-der-Open-Source-Data-Center-Conference-2012-OSDC12.html</link>
            <category>Messen &amp; Events</category>
    
    <comments>http://www.christopher-kunz.de/archives/274-Vortrag-auf-der-Open-Source-Data-Center-Conference-2012-OSDC12.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=274</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=274</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt;&lt;!-- s9ymdb:128 --&gt;&lt;a href=&quot;http://www.netways.de/en/osdc/osdc_2012/program/&quot;&gt;&lt;img width=&quot;238&quot; height=&quot;255&quot; src=&quot;http://www.christopher-kunz.de/uploads/button_speaker.jpg&quot; class=&quot;serendipity_image_left&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;Ich freue mich, an der Open Source Data Center Conference 2012 als Speaker teilnehmen zu dürfen. Den Ausrichter, Bernd Erk von Netways, kenne ich von einer früheren Heise-Konferenz als kompententen und netten Zeitgenossen und das macht es umso angenehmer.&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;Nachdem die SecTXL in Hamburg leider nicht stattfinden konnte, werde ich nun den Vortrag, den ich eigentlich dort angemeldet hatte, auf der OSDC exklusiv halten. Titel und Abstract lauten wie folgt:&lt;/p&gt; &lt;br /&gt;
&lt;blockquote&gt; &lt;br /&gt;
&lt;h2&gt;CA failures and the future of Web authentication  (EN)&lt;/h2&gt; &lt;br /&gt;
&lt;p&gt;In 2011, a number of Certification Authorities suffered catastrophic failures which showed that the SSL CA system, a cornerstone of the secure Web, has been undermined by attackers and corporate greed. These failures and malpractices may well lead to the eventual downfall of SSL certificates as we know them.&lt;/p&gt;&lt;br /&gt;
&lt;p&gt;This talk will summarize the events which transpired last year (and continue to pop up in 2012) and show which alternatives are currently in the making. It will introduce concepts like DANE, Convergence, Sovereign Keys and show some interesting info about SSL certificates &amp;#8220;in the wild&amp;#8221;.&lt;/p&gt; &lt;br /&gt;
&lt;/blockquote&gt; &lt;br /&gt;
&lt;p&gt;&lt;br /&gt;
Im Wesentlichen geht es also zum Einen um eine Retrospektive der letzten Jahre und der Major Fails im CA-Markt, aber auch um die Frage: &amp;#8220;Was machen wir in Zukunft mit SSL?&amp;#8221;. Und die ist ebenso spannend wie ambivalent. Ganz abschaffen kommt nicht in Frage, denn dann macht Amazon pleite. Und alles so zu lassen, ist ebensowenig eine Option. Einige spannende Projekte haben sich auf die Fahne geschrieben, die CAs zu ersetzen oder zumindest etwas weniger zum &amp;#8220;Single Point of Failure&amp;#8221; zu machen - und diese Projekte möchte ich kurz vorstellen.&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;Wichtig ist mir auch, daß diejenigen CA-Alternativen vorgestellt werden, die von freier Software inspiriert und unterstützt werden - also Convergence als Firefox-Plugin, oder die Forschungs- und Entwicklungsarbeiten beim EFF.&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;Die OSDC12 findet am 25. und 26. April in Nürnberg statt. Ein Rundum-Sorglos-Paket inkl. 2 Hotelübernachtungen und Konferenzdinner ist für € 950,- erhältlich. Das ist ein sehr guter Preis für ein hochklassiges Konferenzprogramm, das von Puppet über IPv6 bis zu Cloud-Workshops alle Aspekte des &amp;#8220;State of the Art&amp;#8221; in Opensource-zentrierten Rechenzentren abdeckt.&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;Mein Vortrag ist übrigens am 25. April um 14:00 - ich freue mich auf möglichst viel Publikum und eine ergiebige Diskussion!&lt;br /&gt;&lt;/p&gt; 
    </content:encoded>

    <pubDate>Mon, 05 Mar 2012 16:06:53 +0100</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/274-guid.html</guid>
    <category>ca</category>
<category>chain of trust</category>
<category>osdc</category>
<category>ssl</category>
<category>vortrag</category>

</item>
<item>
    <title>Doktor-Ingenieur</title>
    <link>http://www.christopher-kunz.de/archives/273-Doktor-Ingenieur.html</link>
    
    <comments>http://www.christopher-kunz.de/archives/273-Doktor-Ingenieur.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=273</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=273</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt;Am 13.12. war die Prüfung, jetzt darf ich auch offiziell verkünden: Ich bin nun Dr.-Ing. (Doktor-Ingenieur). Ich habe meine Doktorprüfung mit &amp;#8220;sehr gut&amp;#8221; bestanden (der zweitbesten Note) und seit heute darf ich mit Übergabe der Promotionsurkunde meinen Titel auch führen.&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;Ich werde später noch ausführlich dazu bloggen (insbesondere über den Promotionsprozeß, das Schreiben der Diss etc.), hier vorab schon mal das wichtigste: Die Urkunde.&lt;/p&gt; &lt;br /&gt;
&lt;p&gt; Vielen Dank an alle, die an diesem Erfolg beteiligt waren!&lt;/p&gt;&lt;br /&gt;
&lt;p&gt;&lt;a  onclick=&quot;F1 = window.open(&#039;/uploads/IMG_1930.JPG&#039;,&#039;Zoom&#039;,&#039;height=2607,width=1951,top=-771,left=-128,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;  rel=&quot;lightbox&quot; href=&quot;http://www.christopher-kunz.de/uploads/IMG_1930.JPG&quot; class=&quot;serendipity_image_link&quot;&gt;&lt;!-- s9ymdb:127 --&gt;&lt;img height=&quot;110&quot; width=&quot;108&quot; src=&quot;http://www.christopher-kunz.de/uploads/IMG_1930.serendipityThumb.JPG&quot; class=&quot;serendipity_image_center&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt; &lt;/p&gt; &lt;br /&gt;
&lt;p align=&quot;center&quot;&gt;&lt;a  class=&quot;serendipity_image_link&quot;  rel=&quot;lightbox&quot; href=&quot;http://www.christopher-kunz.de/uploads/IMG_1930.JPG&quot; onclick=&quot;F1 = window.open(&#039;/uploads/IMG_1930.JPG&#039;,&#039;Zoom&#039;,&#039;height=2607,width=1951,top=-771,left=-128,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:127 --&gt;&lt;/a&gt;&lt;br /&gt;&lt;/p&gt;&lt;br clear=&quot;all&quot; /&gt; 
    </content:encoded>

    <pubDate>Mon, 09 Jan 2012 11:19:52 +0100</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/273-guid.html</guid>
    
</item>
<item>
    <title>Voodoo Carrier IQ Detector report für Huawei Ideos X3</title>
    <link>http://www.christopher-kunz.de/archives/272-Voodoo-Carrier-IQ-Detector-report-fuer-Huawei-Ideos-X3.html</link>
            <category>Gadgets</category>
    
    <comments>http://www.christopher-kunz.de/archives/272-Voodoo-Carrier-IQ-Detector-report-fuer-Huawei-Ideos-X3.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=272</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=272</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;pre&gt;Voodoo Carrier IQ Detector report:&lt;br /&gt;
&lt;br /&gt;
Build fingerprint:&lt;br /&gt;
Huawei/U8510/hwu8510:2.3.3/HuaweiU8510/C169B850:user/ota-rel-keys,release-keys&lt;br /&gt;
&lt;br /&gt;
Carrier IQ elements found&lt;br /&gt;
? however it seems inactive&lt;br /&gt;
Detection score: 70&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Test for: Linux kernel interfaces&lt;br /&gt;
(KERNEL_INTERFACES, weight 50)&lt;br /&gt;
&lt;br /&gt;
    nothing found&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Test for: Android logcat debugging log&lt;br /&gt;
(LOGCAT, weight 100)&lt;br /&gt;
&lt;br /&gt;
    nothing found&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Test for: Linux kernel drivers&lt;br /&gt;
(KERNEL_DRIVERS, weight 50)&lt;br /&gt;
&lt;br /&gt;
    nothing found&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Test for: System services&lt;br /&gt;
(SERVICES, weight 70)&lt;br /&gt;
&lt;br /&gt;
    nothing found&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Test for: ROM binaries and daemons&lt;br /&gt;
(SYSTEM_BINARIES, weight 70)&lt;br /&gt;
&lt;br /&gt;
    found:    /system/bin/iqmsd&lt;br /&gt;
    found:    /system/lib/libiq_service.so&lt;br /&gt;
    found:    /system/lib/libiq_client.so&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Test for: ROM configs&lt;br /&gt;
(ETC_CONFIG, weight 0)&lt;br /&gt;
&lt;br /&gt;
    nothing found&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Test for: Packages&lt;br /&gt;
(PACKAGES, weight 70)&lt;br /&gt;
&lt;br /&gt;
    nothing found&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Test for: Running processes&lt;br /&gt;
(RUNNING_PROCESSES, weight 200)&lt;br /&gt;
&lt;br /&gt;
    nothing found&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Test for: Suspicious classes&lt;br /&gt;
(SUSPICIOUS_CLASSES, weight 0)&lt;br /&gt;
&lt;br /&gt;
    found:    com.carrieriq.iqagent.service.receivers.BootCompletedReceiver&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Test for: Linux kernel dmesg log&lt;br /&gt;
(DMESG, weight 100)&lt;br /&gt;
&lt;br /&gt;
    nothing found&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;div class=&quot;moz-txt-sig&quot;&gt;-- &lt;br /&gt;
Voodoo CarrierIQ Detector 2.0.5&lt;/div&gt;&lt;/pre&gt; 
    </content:encoded>

    <pubDate>Thu, 08 Dec 2011 14:27:59 +0100</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/272-guid.html</guid>
    
</item>
<item>
    <title>Lamellenpanzer selbstgebaut 1</title>
    <link>http://www.christopher-kunz.de/archives/271-Lamellenpanzer-selbstgebaut-1.html</link>
            <category>Reenactment</category>
    
    <comments>http://www.christopher-kunz.de/archives/271-Lamellenpanzer-selbstgebaut-1.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=271</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=271</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt;Im Zuge meines Darstellungswechsels (vom Hochmittelalter ins Frühmittelalter, 10. Jahrhundert) wollte ich auch einen neuen Körperpanzer anschaffen, der etwas mehr Funktionalität als das alte Kettenhemd hat. Das ist als Schlagschutz nämlich denkbar ungeeignet und Stiche zum Körper sind im Freikampf keine Gefahr. Neben einem einigermaßen vollständigen vernieteten/gestanzten Kettenhemd, das in Gjermundbu gefunden wurde, existieren aus der Wikingerzeit wohl relativ wenige Belege für Rüstungsteile; am nächsten dran sind noch einige in Schweden (Birka) gefundene Stahllamellen, die wohl Teil eines Lamellenpanzers waren. Diese Panzer sind aus späteren Zeiten und anderen Regionen bekannt - da die Waräger eine rege Reisetätigkeit gen Byzanz unternommen hatten, ist es wohl nicht zu weit hergeholt, daß Lamellenpanzer im 10. Jahrhundert bekannt, wenn auch nicht unbedingt sehr beliebt waren. Sagas berichten wohl davon, daß Krieger ihre Rüstung wegen des zu warmen Wetters vor der Schlacht im Lager ließen und lieber ohne kämpften.&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;&lt;br /&gt;&lt;/p&gt; &lt;br /&gt;&lt;a href=&quot;http://www.christopher-kunz.de/archives/271-Lamellenpanzer-selbstgebaut-1.html#extended&quot;&gt;Continue reading &quot;Lamellenpanzer selbstgebaut 1&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Mon, 29 Aug 2011 10:37:24 +0200</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/271-guid.html</guid>
    
</item>
<item>
    <title>Trekstor i.gear Slider Review</title>
    <link>http://www.christopher-kunz.de/archives/270-Trekstor-i.gear-Slider-Review.html</link>
            <category>Gadgets</category>
    
    <comments>http://www.christopher-kunz.de/archives/270-Trekstor-i.gear-Slider-Review.html#comments</comments>
    <wfw:comment>http://www.christopher-kunz.de/wfwcomment.php?cid=270</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.christopher-kunz.de/rss.php?version=2.0&amp;type=comments&amp;cid=270</wfw:commentRss>
    

    <author>nospam@example.com (Christopher Kunz)</author>
    <content:encoded>
    &lt;p&gt; &lt;/p&gt; &lt;br /&gt;
&lt;div class=&quot;serendipity_imageComment_left&quot; style=&quot;width: 110px;&quot;&gt; &lt;br /&gt;
&lt;div class=&quot;serendipity_imageComment_img&quot;&gt;&lt;a  class=&quot;serendipity_image_link&quot; title=&quot;trekstor i.gear Slider aufgeklappt&quot;  rel=&quot;lightbox&quot; href=&quot;http://www.christopher-kunz.de/uploads/DSCF6006.JPG&quot; onclick=&quot;F1 = window.open(&#039;/uploads/DSCF6006.JPG&#039;,&#039;Zoom&#039;,&#039;height=2379,width=2658,top=-732,left=-601.5,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;!-- s9ymdb:123 --&gt;&lt;img width=&quot;110&quot; height=&quot;98&quot; class=&quot;serendipity_image_left&quot; src=&quot;http://www.christopher-kunz.de/uploads/DSCF6006.serendipityThumb.JPG&quot; title=&quot;trekstor i.gear Slider aufgeklappt&quot; alt=&quot;trekstor i.gear Slider aufgeklappt&quot; /&gt;&lt;/a&gt;&lt;/div&gt; &lt;br /&gt;
&lt;div class=&quot;serendipity_imageComment_txt&quot;&gt;trekstor i.gear Slider aufgeklappt&lt;/div&gt; &lt;br /&gt;
&lt;/div&gt;Einer der großen Nachteile des iPhone ist die Tastatur oder eher das Fehlen derselben. Die Bildschirmtastatur ist im Landscape-Modus zu raumgreifend und im Hochkant-Modus unbrauchbar; Umlaute sind schlecht zu erreichen (was sich mit iOS 5 ändern dürfte) und mir als Vieltipper geht es besonders auf die Nerven, daß man statt der LeertastemgernemmalmdenmBuchstabenm&amp;#8220;m&amp;#8221;merwischt. Besitzer eines Slider-Smartphones frohlocken hier, haben sie doch zumindest einen leichten Vorteil gegenüber uns Apfeljüngern (und den androidigen Kollegen, die ähnliche Probleme haben).&amp;#160;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt; &lt;/p&gt; &lt;br /&gt;
&lt;p&gt;Trekstor hat mit dem &amp;#8220;i.gear Slider&amp;#8221; nun eine pfiffige Alternative vorgestellt, die ich mir gleich angeschafft habe. Es handelt sich bei dem Gerät um ein Hardcase, an das unten eine Bluetooth-Tastatur angeschnallt ist. Diese Tastatur wird von einem LiIon-Akku gespeist, der eine Standbyzeit von bis zu 45 Tagen haben und sich für 8 Stunden Dauerbetrieb eignen soll.&amp;#160;&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;Das Tastenfeld ist etwa 10,5cm breit und 2,4cm hoch - für die einzelne Taste bleibt bei 4 Tastenreihen eine Höhe von etwa 6mm und eine Breite von 8mm. Das ist sicherlich nicht Fullsize, aber eben doch größer als die Fitzelchen auf dem iPhone-Bildschirm.&lt;/p&gt; &lt;br /&gt;
&lt;p&gt;&lt;br /&gt;&lt;/p&gt; &lt;br /&gt;&lt;a href=&quot;http://www.christopher-kunz.de/archives/270-Trekstor-i.gear-Slider-Review.html#extended&quot;&gt;Continue reading &quot;Trekstor i.gear Slider Review&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Thu, 07 Jul 2011 20:45:51 +0200</pubDate>
    <guid isPermaLink="false">http://www.christopher-kunz.de/archives/270-guid.html</guid>
    <category>bluetooth</category>
<category>gadget</category>
<category>iphone</category>
<category>slider</category>
<category>tastatur</category>

</item>

</channel>
</rss>