<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Using sigtool in Linux</title>
	<atom:link href="http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/</link>
	<description>Hardware, software, and just general tinkering</description>
	<lastBuildDate>Wed, 24 Feb 2010 00:40:43 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: octo</title>
		<link>http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/comment-page-1/#comment-999</link>
		<dc:creator>octo</dc:creator>
		<pubDate>Sun, 23 Aug 2009 14:53:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/#comment-999</guid>
		<description>For many older JDE tool versions, you also need to modify rapc.jar in a similar way.  The offending backslashes are in the code that processes internationalization resource files, so you might not have noticed if you haven&#039;t tried using those.

As of the gold version of the JDE 4.7 tools, I have some interesting observations to report:

First, you no longer need to modify rapc.jar

Second, you still need to modify a backslash in SignatureTool.jar, in the q.class file.

For normal operations, you may never notice this.  I certainly didn&#039;t.  It never causes a problem most of the time.  But in a weird situation that only happened on my build server, and only with multi-targetted builds, it lead to a temporary directory getting created in a way that confused the crap out of my build process.  It took a lot of invasive debugging to figure this out.</description>
		<content:encoded><![CDATA[<p>For many older JDE tool versions, you also need to modify rapc.jar in a similar way.  The offending backslashes are in the code that processes internationalization resource files, so you might not have noticed if you haven&#8217;t tried using those.</p>
<p>As of the gold version of the JDE 4.7 tools, I have some interesting observations to report:</p>
<p>First, you no longer need to modify rapc.jar</p>
<p>Second, you still need to modify a backslash in SignatureTool.jar, in the q.class file.</p>
<p>For normal operations, you may never notice this.  I certainly didn&#8217;t.  It never causes a problem most of the time.  But in a weird situation that only happened on my build server, and only with multi-targetted builds, it lead to a temporary directory getting created in a way that confused the crap out of my build process.  It took a lot of invasive debugging to figure this out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Travis</title>
		<link>http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/comment-page-1/#comment-966</link>
		<dc:creator>Travis</dc:creator>
		<pubDate>Thu, 04 Jun 2009 18:01:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/#comment-966</guid>
		<description>I can confirm that you no longer need to modify JavaLoader.jar. It appears that the version RIM distributes is now portable across platforms.</description>
		<content:encoded><![CDATA[<p>I can confirm that you no longer need to modify JavaLoader.jar. It appears that the version RIM distributes is now portable across platforms.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Somebody</title>
		<link>http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/comment-page-1/#comment-941</link>
		<dc:creator>Somebody</dc:creator>
		<pubDate>Tue, 21 Apr 2009 17:17:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/#comment-941</guid>
		<description>I don&#039;t know if something has changed in more recent versions, but it does NOT appear to be necessary to make any modifications to the SignatureTool.jar file for it to work in Linux. Just run &quot;java -jar SignatureTool.jar&quot; and it works exactly the same as it does in windoze. Same with rapc.jar.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know if something has changed in more recent versions, but it does NOT appear to be necessary to make any modifications to the SignatureTool.jar file for it to work in Linux. Just run &#8220;java -jar SignatureTool.jar&#8221; and it works exactly the same as it does in windoze. Same with rapc.jar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Kopec</title>
		<link>http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/comment-page-1/#comment-841</link>
		<dc:creator>Mark Kopec</dc:creator>
		<pubDate>Mon, 09 Feb 2009 20:33:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/#comment-841</guid>
		<description>Wow, great post!

I&#039;ve had to get my team to use VMware on top of Linux just to have a stable Windows environment to constantly sign and build each properly without the headache of doing fancy things like this with the sigtool and the rapc compiler.

Now however, to integrate and build this continuously with the rest of our server-side code these suggestions sound like a nice option!

Thanks JiGGak, how did you learn to dive into the HEX of the sigtool to make these changes!?! that&#039;s great stuff!

M.</description>
		<content:encoded><![CDATA[<p>Wow, great post!</p>
<p>I&#8217;ve had to get my team to use VMware on top of Linux just to have a stable Windows environment to constantly sign and build each properly without the headache of doing fancy things like this with the sigtool and the rapc compiler.</p>
<p>Now however, to integrate and build this continuously with the rest of our server-side code these suggestions sound like a nice option!</p>
<p>Thanks JiGGak, how did you learn to dive into the HEX of the sigtool to make these changes!?! that&#8217;s great stuff!</p>
<p>M.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jiGGaK</title>
		<link>http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/comment-page-1/#comment-836</link>
		<dc:creator>jiGGaK</dc:creator>
		<pubDate>Sun, 30 Nov 2008 20:13:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/#comment-836</guid>
		<description>Nice one Kevin!</description>
		<content:encoded><![CDATA[<p>Nice one Kevin!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/comment-page-1/#comment-835</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Sun, 30 Nov 2008 19:59:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/#comment-835</guid>
		<description>I tried the xvfb suggestion and it worked:

sudo apt-get install xvfb

xvfb-run java -jar SignatureTool.jar -a -C -p xxx xxx.cod

Thanks!</description>
		<content:encoded><![CDATA[<p>I tried the xvfb suggestion and it worked:</p>
<p>sudo apt-get install xvfb</p>
<p>xvfb-run java -jar SignatureTool.jar -a -C -p xxx xxx.cod</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/comment-page-1/#comment-834</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Sat, 29 Nov 2008 22:54:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/#comment-834</guid>
		<description>I&#039;m having the same problem as tvb: java.awt.HeadlessException

Did you, or anyone, come up with a solution or workaround?  We don&#039;t have time built into our project for me to reverse engineer the signing app, unfortunately.  :)

Thanks.</description>
		<content:encoded><![CDATA[<p>I&#8217;m having the same problem as tvb: java.awt.HeadlessException</p>
<p>Did you, or anyone, come up with a solution or workaround?  We don&#8217;t have time built into our project for me to reverse engineer the signing app, unfortunately.  <img src='http://www.slashdev.ca/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tvb</title>
		<link>http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/comment-page-1/#comment-833</link>
		<dc:creator>tvb</dc:creator>
		<pubDate>Mon, 24 Nov 2008 21:32:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/#comment-833</guid>
		<description>Drag indeed!  I looked at the method signatures of the tool hoping to find some public &quot;sign&quot; method that I could invoke through a custom wrapper class, but no such luck.  RIMM isn&#039;t all that great with documentation either, so it&#039;s going to be tough to write a signature tool.  I guess Xvfb is the best approach.  Thanks for your help.</description>
		<content:encoded><![CDATA[<p>Drag indeed!  I looked at the method signatures of the tool hoping to find some public &#8220;sign&#8221; method that I could invoke through a custom wrapper class, but no such luck.  RIMM isn&#8217;t all that great with documentation either, so it&#8217;s going to be tough to write a signature tool.  I guess Xvfb is the best approach.  Thanks for your help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jiGGaK</title>
		<link>http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/comment-page-1/#comment-832</link>
		<dc:creator>jiGGaK</dc:creator>
		<pubDate>Mon, 24 Nov 2008 20:45:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/#comment-832</guid>
		<description>Drag...

Well there is always the X windows virtual frame buffer.  This enables X to run without any physical display hardware.  I don&#039;t have any experience with this though.

And if you are REALLY committed to this, you could attempt to reverse engineer the signing process in order to write your own signature tool sans-gui.</description>
		<content:encoded><![CDATA[<p>Drag&#8230;</p>
<p>Well there is always the X windows virtual frame buffer.  This enables X to run without any physical display hardware.  I don&#8217;t have any experience with this though.</p>
<p>And if you are REALLY committed to this, you could attempt to reverse engineer the signing process in order to write your own signature tool sans-gui.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tvb</title>
		<link>http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/comment-page-1/#comment-831</link>
		<dc:creator>tvb</dc:creator>
		<pubDate>Mon, 24 Nov 2008 20:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/#comment-831</guid>
		<description>jiGGaK - thanks for the suggestion.  Unfortunately, it looks like the tool is trying to bring up the GUI when it&#039;s applying the siganture, so it still fails, even though I set the headless property to true:

Exception in thread &quot;main&quot; java.awt.HeadlessException
        at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:159)
        at java.awt.Window.(Window.java:317)
        at java.awt.Frame.(Frame.java:419)
        at javax.swing.JFrame.(JFrame.java:194)
        at net.rim.device.codesigning.signaturetool.v.a(Unknown Source)
        at net.rim.device.codesigning.signaturetool.v.(Unknown Source)
        at net.rim.device.codesigning.signaturetool.SignatureTool.(Unknown Source)
        at net.rim.device.codesigning.signaturetool.SignatureTool.main(Unknown Source)</description>
		<content:encoded><![CDATA[<p>jiGGaK &#8211; thanks for the suggestion.  Unfortunately, it looks like the tool is trying to bring up the GUI when it&#8217;s applying the siganture, so it still fails, even though I set the headless property to true:</p>
<p>Exception in thread &#8220;main&#8221; java.awt.HeadlessException<br />
        at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:159)<br />
        at java.awt.Window.(Window.java:317)<br />
        at java.awt.Frame.(Frame.java:419)<br />
        at javax.swing.JFrame.(JFrame.java:194)<br />
        at net.rim.device.codesigning.signaturetool.v.a(Unknown Source)<br />
        at net.rim.device.codesigning.signaturetool.v.(Unknown Source)<br />
        at net.rim.device.codesigning.signaturetool.SignatureTool.(Unknown Source)<br />
        at net.rim.device.codesigning.signaturetool.SignatureTool.main(Unknown Source)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
