<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>WorqSmart &#187; encryption</title>
	<atom:link href="http://www.worqsmart.com/tag/encryption/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.worqsmart.com</link>
	<description>Smart Solutions for Smart People</description>
	<lastBuildDate>Tue, 20 Sep 2011 19:54:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>eAuthorize SSL 3.0 Support</title>
		<link>http://www.worqsmart.com/2009/02/eauthorize-ssl-30-support/</link>
		<comments>http://www.worqsmart.com/2009/02/eauthorize-ssl-30-support/#comments</comments>
		<pubDate>Wed, 25 Feb 2009 05:56:39 +0000</pubDate>
		<dc:creator>msilving</dc:creator>
				<category><![CDATA[eAuthorize 3.5]]></category>
		<category><![CDATA[eAuthorize 5.0]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[ssl]]></category>

		<guid isPermaLink="false">http://web.worqsmart.com/?p=1194</guid>
		<description><![CDATA[The operating system services for communication are being used for SSL support. When a URL type of https:// is used by the eAuthorize plugin, it requests this connection from the operating system, so if the operating system has SSL 3.0 support, then eAuthorize should continue to work.
]]></description>
			<content:encoded><![CDATA[<p id="top" />The operating system services for communication are being used for SSL support. When a URL type of https:// is used by the eAuthorize plugin, it requests this connection from the operating system, so if the operating system has SSL 3.0 support, then eAuthorize should continue to work.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.worqsmart.com/2009/02/eauthorize-ssl-30-support/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>eAuthorize Security</title>
		<link>http://www.worqsmart.com/2009/01/eauthorize-security/</link>
		<comments>http://www.worqsmart.com/2009/01/eauthorize-security/#comments</comments>
		<pubDate>Thu, 22 Jan 2009 15:35:13 +0000</pubDate>
		<dc:creator>worqsmart</dc:creator>
				<category><![CDATA[eAuthorize 5.0]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[ssl]]></category>

		<guid isPermaLink="false">http://web.worqsmart.com/?p=1100</guid>
		<description><![CDATA[The eAuthorize plugin supports SSL. The plugin encrypts the data, sends it to the gateway, waits for a response to be sent back using SSL. PCI compliance is provided by the gateway providers, but you will need to build PCI compliance into your FileMaker solution. The plugin supports different levels of authentication, but it doesn&#8217;t provide built-in PCI compliance measures.
]]></description>
			<content:encoded><![CDATA[<p id="top" />The eAuthorize plugin supports SSL. The plugin encrypts the data, sends it to the gateway, waits for a response to be sent back using SSL. PCI compliance is provided by the gateway providers, but you will need to build PCI compliance into your FileMaker solution. The plugin supports different levels of authentication, but it doesn&#8217;t provide built-in PCI compliance measures.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.worqsmart.com/2009/01/eauthorize-security/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

