<?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: JIRA Standalone &#8211; Major Vulnerability</title>
	<atom:link href="http://www.karlkatzke.com/jira-standalone-major-vulnerability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.karlkatzke.com/jira-standalone-major-vulnerability/</link>
	<description>Geek of the Week</description>
	<lastBuildDate>Wed, 25 Aug 2010 16:17:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Michael Fox</title>
		<link>http://www.karlkatzke.com/jira-standalone-major-vulnerability/comment-page-1/#comment-1537</link>
		<dc:creator>Michael Fox</dc:creator>
		<pubDate>Fri, 20 Mar 2009 10:38:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.karlkatzke.com/jira-standalone-major-vulnerability/#comment-1537</guid>
		<description>If you dig around, you should be able to find some documentation to make it so that your several instances of Jira on a single host can be accessed via your normal webserver.

ie. I installed 2 instances of Jira onto a single host, and bound them to 8080 and 8081.

I then installed apache, and some suitable modules. Then configured apache so that http://host.domain.com/jira-one/ would serve the contents of jira instance one from 8080, then then http://host.domain.com/jira-two/ would serve the contents of jira instance two from 8081.

So all the user has to remember is http://site.../jira-one/ or http://site.../jira-two/

Had hoped to use vhosts to do it, but I will give that another go soon enough, but for the moment. I am happy with the current arrangement.</description>
		<content:encoded><![CDATA[<p>If you dig around, you should be able to find some documentation to make it so that your several instances of Jira on a single host can be accessed via your normal webserver.</p>
<p>ie. I installed 2 instances of Jira onto a single host, and bound them to 8080 and 8081.</p>
<p>I then installed apache, and some suitable modules. Then configured apache so that <a href="http://host.domain.com/jira-one/" rel="nofollow">http://host.domain.com/jira-one/</a> would serve the contents of jira instance one from 8080, then then <a href="http://host.domain.com/jira-two/" rel="nofollow">http://host.domain.com/jira-two/</a> would serve the contents of jira instance two from 8081.</p>
<p>So all the user has to remember is <a href="http://site.../jira-one/" rel="nofollow">http://site&#8230;/jira-one/</a> or <a href="http://site.../jira-two/" rel="nofollow">http://site&#8230;/jira-two/</a></p>
<p>Had hoped to use vhosts to do it, but I will give that another go soon enough, but for the moment. I am happy with the current arrangement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Katzke</title>
		<link>http://www.karlkatzke.com/jira-standalone-major-vulnerability/comment-page-1/#comment-186</link>
		<dc:creator>Karl Katzke</dc:creator>
		<pubDate>Fri, 14 Mar 2008 01:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.karlkatzke.com/jira-standalone-major-vulnerability/#comment-186</guid>
		<description>Tim - There&#039;s two ways to handle this. One is to use the jsvc extension, which would run one thread as Root to open the port, and one thread as TOMCAT_USER (an unprivileged user) to actually handle the requests. I can&#039;t figure out in the tangle of configuration files; they do seem to be using jsvc but passing the --user option in the catalina start shell script does not seem to work.

How *we* handle it is by putting squid in front of it with a port redirect.... but we have a load balancing setup that allows us to do that. You could use Apache for this, you could use your box&#039;s firewall to forward all requests from port 80 to port 8080, etc. so on so forth. It depends on your environment and how detailed you&#039;re willing to get with configuration.

The point still remains -- don&#039;t run JIRA standalone as root. You really, really don&#039;t want Tomcat running with root permissions.</description>
		<content:encoded><![CDATA[<p>Tim &#8211; There&#8217;s two ways to handle this. One is to use the jsvc extension, which would run one thread as Root to open the port, and one thread as TOMCAT_USER (an unprivileged user) to actually handle the requests. I can&#8217;t figure out in the tangle of configuration files; they do seem to be using jsvc but passing the &#8211;user option in the catalina start shell script does not seem to work.</p>
<p>How *we* handle it is by putting squid in front of it with a port redirect&#8230;. but we have a load balancing setup that allows us to do that. You could use Apache for this, you could use your box&#8217;s firewall to forward all requests from port 80 to port 8080, etc. so on so forth. It depends on your environment and how detailed you&#8217;re willing to get with configuration.</p>
<p>The point still remains &#8212; don&#8217;t run JIRA standalone as root. You really, really don&#8217;t want Tomcat running with root permissions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Kientzle</title>
		<link>http://www.karlkatzke.com/jira-standalone-major-vulnerability/comment-page-1/#comment-185</link>
		<dc:creator>Tim Kientzle</dc:creator>
		<pubDate>Fri, 14 Mar 2008 00:26:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.karlkatzke.com/jira-standalone-major-vulnerability/#comment-185</guid>
		<description>But then you can&#039;t run Jira on port 80, can you?</description>
		<content:encoded><![CDATA[<p>But then you can&#8217;t run Jira on port 80, can you?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
