<?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: How not to do secure online credit transactions</title>
	<atom:link href="http://www.cafaro.net/2006/09/25/how-not-to-do-secure-online-credit-transactions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cafaro.net/2006/09/25/how-not-to-do-secure-online-credit-transactions/</link>
	<description>A site to collect thoughts and figures of the moment.</description>
	<lastBuildDate>Wed, 13 Aug 2008 04:03:54 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: psmay</title>
		<link>http://www.cafaro.net/2006/09/25/how-not-to-do-secure-online-credit-transactions/comment-page-1/#comment-122</link>
		<dc:creator>psmay</dc:creator>
		<pubDate>Wed, 18 Oct 2006 20:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.cafaro.net/2006/09/25/how-not-to-do-secure-online-credit-transactions/#comment-122</guid>
		<description>In terms of egregiousness, that probably beats what I have.  The parties responsible should be forced to...er...do something that would improve security.  (That could have gotten more violent.)

I&#039;m aggravated by a couple of Dreamhost&#039;s policies.  Dreamhost is an excellent place to have a homepage, host about a zillion domain names, and basically mess around, and they do some very interesting things technically, but I would definitely be leery of recommending it to anyone considering e-commerce.

If this were to change, I might reconsider:  When setting up new user accounts, the new user&#039;s password is sent to the user via e-mail, regardless of whether it was set manually or chosen by the user.  Fortunately, access to their IMAP server can optionally be over SSL, so I mitigate this by setting my only access address to the mailbox I access via SSL&#8212;and remove (not just trash) the offending e-mail from the remote folder as soon as possible.  I figure since Dreamhost is both the source and the destination of the mail, it can&#039;t have been exposed to the public &lt;em&gt;too much&lt;/em&gt;.  But it&#039;s messy.  They should at least make it an &lt;em&gt;option&lt;/em&gt; not to send passwords.

Another gripe I have is that you cannot access phpMyAdmin through their SSLed panel server; you must access it through a special subdomain of your own domain which isn&#039;t SSLed (even if you bought SSL for your domain).  I&#039;ve worked around this by purchasing the static IP option and adding a CAcert.org-signed certificate, then installing my own copy of PMA.

All of this would be a lot more fun if it were more straightforwardly secure, though!</description>
		<content:encoded><![CDATA[<p>In terms of egregiousness, that probably beats what I have.  The parties responsible should be forced to&#8230;er&#8230;do something that would improve security.  (That could have gotten more violent.)</p>
<p>I&#8217;m aggravated by a couple of Dreamhost&#8217;s policies.  Dreamhost is an excellent place to have a homepage, host about a zillion domain names, and basically mess around, and they do some very interesting things technically, but I would definitely be leery of recommending it to anyone considering e-commerce.</p>
<p>If this were to change, I might reconsider:  When setting up new user accounts, the new user&#8217;s password is sent to the user via e-mail, regardless of whether it was set manually or chosen by the user.  Fortunately, access to their IMAP server can optionally be over SSL, so I mitigate this by setting my only access address to the mailbox I access via SSL&mdash;and remove (not just trash) the offending e-mail from the remote folder as soon as possible.  I figure since Dreamhost is both the source and the destination of the mail, it can&#8217;t have been exposed to the public <em>too much</em>.  But it&#8217;s messy.  They should at least make it an <em>option</em> not to send passwords.</p>
<p>Another gripe I have is that you cannot access phpMyAdmin through their SSLed panel server; you must access it through a special subdomain of your own domain which isn&#8217;t SSLed (even if you bought SSL for your domain).  I&#8217;ve worked around this by purchasing the static IP option and adding a CAcert.org-signed certificate, then installing my own copy of PMA.</p>
<p>All of this would be a lot more fun if it were more straightforwardly secure, though!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
