<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://davejarvis.ulitzer.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Dave Jarvis</title>
 <link>http://davejarvis.ulitzer.com/</link>
 <description>Latest News from Dave Jarvis</description>
 <language>en</language>
 <copyright>Copyright 2012 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Thu, 17 May 2012 17:23:15 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Indispensable - JasperReports,  iReport, and R</title>
 <link>http://davejarvis.ulitzer.com/node/1796129</link>
 <description>A problem has come to my attention over the last few years and I thought Java.net would be a good place to talk about it.

I have noticed that many reporting integrations use vendor-supplied examples verbatim. This is an issue.

With JasperReports (the Java-based reporting tool), the reports contain SQL code. That SQL code can tell a hacker a lot about the database (type, version, table names, column names, and such). This opens up an attack vector, and many people host their report files in the same directory as the web files.
Worse still, some people write JSPs with the database connection information (login, password, host name, database name) in plain text - inside the JSP files!&lt;p&gt;&lt;a href=&quot;http://davejarvis.ulitzer.com/node/1796129&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 17 Apr 2011 16:31:00 EDT</pubDate>
 <guid isPermaLink="true">http://davejarvis.ulitzer.com/node/1796129</guid>
 <comments>http://davejarvis.ulitzer.com/node/1796129#feedback</comments>
</item>
</channel>
</rss>

