<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Network Data Encryption and Integrity for Thin JDBC Clients</title>
	<atom:link href="http://javasight.wordpress.com/2008/08/29/network-data-encryption-and-integrity-for-thin-jdbc-clients/feed/" rel="self" type="application/rss+xml" />
	<link>http://javasight.wordpress.com/2008/08/29/network-data-encryption-and-integrity-for-thin-jdbc-clients/</link>
	<description>Technology across minds.....</description>
	<lastBuildDate>Sat, 07 Nov 2009 05:16:49 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Frank</title>
		<link>http://javasight.wordpress.com/2008/08/29/network-data-encryption-and-integrity-for-thin-jdbc-clients/#comment-52</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Wed, 12 Nov 2008 12:15:17 +0000</pubDate>
		<guid isPermaLink="false">http://javasight.wordpress.com/?p=76#comment-52</guid>
		<description>Thanks Asim.
  Although its recommended to use the JNDI datasource over Spring managed datasource, I have got contrary opinion/recommendations from the Spring Forum (http://forum.springframework.org/showthread.php?t=60418). Either ways if you were using a Spring manged bean in Spring context you can still encrypt your passwords with API JASYPT[http://www.jasypt.org/]. If it were a JNDI managed resource ,security will be taken care by the Application/Web server(your right on that).


Regards,
Franklin.</description>
		<content:encoded><![CDATA[<p>Thanks Asim.<br />
  Although its recommended to use the JNDI datasource over Spring managed datasource, I have got contrary opinion/recommendations from the Spring Forum (<a href="http://forum.springframework.org/showthread.php?t=60418)" rel="nofollow">http://forum.springframework.org/showthread.php?t=60418)</a>. Either ways if you were using a Spring manged bean in Spring context you can still encrypt your passwords with API JASYPT[http://www.jasypt.org/]. If it were a JNDI managed resource ,security will be taken care by the Application/Web server(your right on that).</p>
<p>Regards,<br />
Franklin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aasimsaleem</title>
		<link>http://javasight.wordpress.com/2008/08/29/network-data-encryption-and-integrity-for-thin-jdbc-clients/#comment-51</link>
		<dc:creator>aasimsaleem</dc:creator>
		<pubDate>Tue, 11 Nov 2008 10:18:48 +0000</pubDate>
		<guid isPermaLink="false">http://javasight.wordpress.com/?p=76#comment-51</guid>
		<description>Excellent article Frank.

As a standard in an App. Server environment, you get the datasource from JNDI, even in Spring, beans can be populated through JNDI. 
Securing the datasource (or any other object), in this case, is the responsiblity of the JNDI architecture. 

But Frank&#039;s article is very true for applications working out of an app. server, inside an App. server, the JNDI approach is preferred.</description>
		<content:encoded><![CDATA[<p>Excellent article Frank.</p>
<p>As a standard in an App. Server environment, you get the datasource from JNDI, even in Spring, beans can be populated through JNDI.<br />
Securing the datasource (or any other object), in this case, is the responsiblity of the JNDI architecture. </p>
<p>But Frank&#8217;s article is very true for applications working out of an app. server, inside an App. server, the JNDI approach is preferred.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank</title>
		<link>http://javasight.wordpress.com/2008/08/29/network-data-encryption-and-integrity-for-thin-jdbc-clients/#comment-45</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Sun, 26 Oct 2008 07:26:06 +0000</pubDate>
		<guid isPermaLink="false">http://javasight.wordpress.com/?p=76#comment-45</guid>
		<description>Hey Rookie,
   Well its very much possible to encrypt the datasource. You have multiple options. 

I remember on Oracle AS when you define you JNDI datasource you can keep clear text password as well as encrypted password. Again this is dependent on the vendor.

However if you were using datasources like Spring managed beans then you could use the API  JASYPT[http://www.jasypt.org/] like follows

datasource.driver=com.mysql.jdbc.Driver
datasource.url=jdbc:mysql://localhost/mydb
datasource.username=user
datasource.password=ENC(G6N718UKyuLQSm02auQPUtm)</description>
		<content:encoded><![CDATA[<p>Hey Rookie,<br />
   Well its very much possible to encrypt the datasource. You have multiple options. </p>
<p>I remember on Oracle AS when you define you JNDI datasource you can keep clear text password as well as encrypted password. Again this is dependent on the vendor.</p>
<p>However if you were using datasources like Spring managed beans then you could use the API  JASYPT[http://www.jasypt.org/] like follows</p>
<p>datasource.driver=com.mysql.jdbc.Driver<br />
datasource.url=jdbc:mysql://localhost/mydb<br />
datasource.username=user<br />
datasource.password=ENC(G6N718UKyuLQSm02auQPUtm)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JAVA_ROOKIE</title>
		<link>http://javasight.wordpress.com/2008/08/29/network-data-encryption-and-integrity-for-thin-jdbc-clients/#comment-44</link>
		<dc:creator>JAVA_ROOKIE</dc:creator>
		<pubDate>Fri, 24 Oct 2008 09:00:30 +0000</pubDate>
		<guid isPermaLink="false">http://javasight.wordpress.com/?p=76#comment-44</guid>
		<description>Hi,
Can we encrypt the data sources in similar way in app servers ?  if yes how ?</description>
		<content:encoded><![CDATA[<p>Hi,<br />
Can we encrypt the data sources in similar way in app servers ?  if yes how ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Network Data Encryption and Integrity for Thin JDBC Clients : Dtv 2009</title>
		<link>http://javasight.wordpress.com/2008/08/29/network-data-encryption-and-integrity-for-thin-jdbc-clients/#comment-10</link>
		<dc:creator>Network Data Encryption and Integrity for Thin JDBC Clients : Dtv 2009</dc:creator>
		<pubDate>Fri, 29 Aug 2008 20:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://javasight.wordpress.com/?p=76#comment-10</guid>
		<description>[...] Original post by Frank [...]</description>
		<content:encoded><![CDATA[<p>[...] Original post by Frank [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Network Data Encryption and Integrity for Thin JDBC Clients : Dtv 2009</title>
		<link>http://javasight.wordpress.com/2008/08/29/network-data-encryption-and-integrity-for-thin-jdbc-clients/#comment-11</link>
		<dc:creator>Network Data Encryption and Integrity for Thin JDBC Clients : Dtv 2009</dc:creator>
		<pubDate>Fri, 29 Aug 2008 20:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://javasight.wordpress.com/?p=76#comment-11</guid>
		<description>[...] Original post by Frank [...]</description>
		<content:encoded><![CDATA[<p>[...] Original post by Frank [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
