<?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"
	>
<channel>
	<title>Comments on: Smart cards should have keypads and beepers</title>
	<atom:link href="http://ursecta.com/wp/2005/07/smart-cards-should-have-keypads-and-beepers/feed/" rel="self" type="application/rss+xml" />
	<link>http://ursecta.com/wp/2005/07/smart-cards-should-have-keypads-and-beepers/</link>
	<description>J. Martin Wehlou on Security, Software Development, and Medicine</description>
	<pubDate>Tue, 06 Jan 2009 22:33:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: TorbjÃ¶rn Hedberg</title>
		<link>http://ursecta.com/wp/2005/07/smart-cards-should-have-keypads-and-beepers/#comment-14</link>
		<dc:creator>TorbjÃ¶rn Hedberg</dc:creator>
		<pubDate>Mon, 01 Aug 2005 21:08:43 +0000</pubDate>
		<guid isPermaLink="false">http://ursecta.com/wp/?p=11#comment-14</guid>
		<description>Thanks for your reply. 

I just want to clarify that by "PKI mafia" I mean people-that-whatever-the-cost-claim-that-user-to-user-encryption-and-signing-is-the-only-thinkable-way-to-send-electronic-prescriptions. So that doesn't include you.

And yes, I know that it doesn't need to be a lot of work to use PKI encryption if standard libraries can be used. 

And no, I don't thing that user-to-user is worth a lot market-wise. But I could be wrong. 
</description>
		<content:encoded><![CDATA[<p>Thanks for your reply. </p>
<p>I just want to clarify that by &#8220;PKI mafia&#8221; I mean people-that-whatever-the-cost-claim-that-user-to-user-encryption-and-signing-is-the-only-thinkable-way-to-send-electronic-prescriptions. So that doesn&#8217;t include you.</p>
<p>And yes, I know that it doesn&#8217;t need to be a lot of work to use PKI encryption if standard libraries can be used. </p>
<p>And no, I don&#8217;t thing that user-to-user is worth a lot market-wise. But I could be wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Wehlou</title>
		<link>http://ursecta.com/wp/2005/07/smart-cards-should-have-keypads-and-beepers/#comment-13</link>
		<dc:creator>Martin Wehlou</dc:creator>
		<pubDate>Mon, 01 Aug 2005 13:08:19 +0000</pubDate>
		<guid isPermaLink="false">http://ursecta.com/wp/?p=11#comment-13</guid>
		<description>&gt; You are, to the best my understanding, absolutely right.

Thank you.

But before diving into the detailed replies, I want to emphasize that my article wasn't about introducing smart cards and PKI, but how to avoid a couple of important problems once you do. And the problems I pointed to were trust of the workstation, which to a large part eliminates the security advantages of smart cards in the first place. But, no problem, your points are valid anyway.

&gt; But does that automatically mean that I, being responsible for the
&gt; development of one of the most used electronic health care record
&gt; application in Sweden (Profdoc Journal III), should strive for the
&gt; adoption these super-smart smart cards? Or even, as some PKI
&gt; fundementalists in this country would have it, prohibit the sending
&gt; of unsigned prescriptions?

Yes, it does, theoretically and morally speaking. Not that I think you will, since you've got a business perspective that is more important to your employer. But the expedient idea, popular in business and very understandable, to only implement things when the pain of not doing it becomes unbearable, is what has brought the Internet to the miserable state it is today. In other words, you and all the other producers of software really should be more proactive, but I have no illusion whatsoever that any one of you will be. History tells us that. Just look at the most used operating system that has gotten away with an abysmal design for a very long time. Good business, but poor technology. And you are, after all, a business. I would (maybe) do the same thing in your place.

So, as a business person, I'd say you're doing fine. You're not going to lose any business by not implementing good security, since nobody else does it either. Not right now, anyway.

&gt; Of course not. Sending unsigned prescriptions electronically is a big
&gt; safety improvement over paper based prescriptions. The way things
&gt; look right now, we should gladly keep promoting our current, not
&gt; really really safe, way of doing things.

No, sending unsigned prescriptions is a disaster waiting for a trigger; it's much worse than paper. 

But you don't do that, you do send encrypted and signed prescriptions using state-of-the-art cryptographic technology. I know that, because I designed and developed that application for you. So your solution is much better than what you'll find elsewhere. It would be even better if the entire process, from the source user to the destination user was covered, but that is the next stage. I'm sure you'll get there, too. At the very minimum, I'm sure you'll provide for the ability to do that, since it would make great business sense. Your communication system, by the way, is designed to easily adapt in this direction, since it's such an obvious future road.

&gt; The difficult question for me is therefore not technical (I'm not a
&gt; deep technician) but timing. When is the right time for me to join
&gt; the ranks of the PKI mafia and say "let's stop this unsafe electronic
&gt; handling of medical information and start doing it right"?

Well, if you call them/us a "mafia", I figure it won't be anytime soon, will it? But if I were you, I'd start figuring out how you will allow it into your records applications, once disaster strikes and it becomes a requirement. If you're a little proactive, it would be a great sales argument, too. I'm sure you'd win clients by telling them that you're working to achieve better security than your competitors. Trying to tell clients that PKI is only high-faluting theory will not enhance credibility. Especially since Profdoc is practically the only company today in its speciality that actually does use state-of-the-art PKI, albeit for only some applications.

Let me make another observation here: most people seem to think that using decent crypto, like PKC's, is somehow very complicated, expensive or resource demanding. That is simply not true. It does require some knowledge on the part of the developers and project leads, but nothing you can't learn. For the users, if correctly implemented, it's practically invisible. In short, it is not rocket science. It also does not require everyone to agree on a system beforehand, as too many people seem to think. You can do it, in your end-user apps, on your own, in a decent timeframe and without loss of user-friendliness. But someone has to show you how.

&gt; I feel that the time is probably quite distant. There are hardly any
&gt; smart cards out there in the hands of my current users and the few
&gt; pilot installations that use personal smart card often get into
&gt; trouble.

It's a chicken-and-egg problem. Also, we need a serious incident with really embarrassing data compromise to make this happen. We need a medical Enron or Card Systems event. Let's just hope it doesn't involve Profdoc. 

The pilot installations I have seen that got into trouble did it wrong. You really have to have someone design it that understands it. You can't run it politically, for instance.

&gt; Or is this attitude just me being lazy and backwords, unwilling to
&gt; adapt to the future? I dont't know.

No, it's missing a great business opportunity. Users really do want better security and they'll flock to the first vendor that takes it seriously. To the first vendor that actually begins doing something, even if it's incomplete.

Again, I don't understand you entirely, since you are doing something, but don't seem to exploit that fact very much in your marketing (but I may be wrong, though).</description>
		<content:encoded><![CDATA[<p>> You are, to the best my understanding, absolutely right.</p>
<p>Thank you.</p>
<p>But before diving into the detailed replies, I want to emphasize that my article wasn&#8217;t about introducing smart cards and PKI, but how to avoid a couple of important problems once you do. And the problems I pointed to were trust of the workstation, which to a large part eliminates the security advantages of smart cards in the first place. But, no problem, your points are valid anyway.</p>
<p>> But does that automatically mean that I, being responsible for the<br />
> development of one of the most used electronic health care record<br />
> application in Sweden (Profdoc Journal III), should strive for the<br />
> adoption these super-smart smart cards? Or even, as some PKI<br />
> fundementalists in this country would have it, prohibit the sending<br />
> of unsigned prescriptions?</p>
<p>Yes, it does, theoretically and morally speaking. Not that I think you will, since you&#8217;ve got a business perspective that is more important to your employer. But the expedient idea, popular in business and very understandable, to only implement things when the pain of not doing it becomes unbearable, is what has brought the Internet to the miserable state it is today. In other words, you and all the other producers of software really should be more proactive, but I have no illusion whatsoever that any one of you will be. History tells us that. Just look at the most used operating system that has gotten away with an abysmal design for a very long time. Good business, but poor technology. And you are, after all, a business. I would (maybe) do the same thing in your place.</p>
<p>So, as a business person, I&#8217;d say you&#8217;re doing fine. You&#8217;re not going to lose any business by not implementing good security, since nobody else does it either. Not right now, anyway.</p>
<p>> Of course not. Sending unsigned prescriptions electronically is a big<br />
> safety improvement over paper based prescriptions. The way things<br />
> look right now, we should gladly keep promoting our current, not<br />
> really really safe, way of doing things.</p>
<p>No, sending unsigned prescriptions is a disaster waiting for a trigger; it&#8217;s much worse than paper. </p>
<p>But you don&#8217;t do that, you do send encrypted and signed prescriptions using state-of-the-art cryptographic technology. I know that, because I designed and developed that application for you. So your solution is much better than what you&#8217;ll find elsewhere. It would be even better if the entire process, from the source user to the destination user was covered, but that is the next stage. I&#8217;m sure you&#8217;ll get there, too. At the very minimum, I&#8217;m sure you&#8217;ll provide for the ability to do that, since it would make great business sense. Your communication system, by the way, is designed to easily adapt in this direction, since it&#8217;s such an obvious future road.</p>
<p>> The difficult question for me is therefore not technical (I&#8217;m not a<br />
> deep technician) but timing. When is the right time for me to join<br />
> the ranks of the PKI mafia and say &#8220;let&#8217;s stop this unsafe electronic<br />
> handling of medical information and start doing it right&#8221;?</p>
<p>Well, if you call them/us a &#8220;mafia&#8221;, I figure it won&#8217;t be anytime soon, will it? But if I were you, I&#8217;d start figuring out how you will allow it into your records applications, once disaster strikes and it becomes a requirement. If you&#8217;re a little proactive, it would be a great sales argument, too. I&#8217;m sure you&#8217;d win clients by telling them that you&#8217;re working to achieve better security than your competitors. Trying to tell clients that PKI is only high-faluting theory will not enhance credibility. Especially since Profdoc is practically the only company today in its speciality that actually does use state-of-the-art PKI, albeit for only some applications.</p>
<p>Let me make another observation here: most people seem to think that using decent crypto, like PKC&#8217;s, is somehow very complicated, expensive or resource demanding. That is simply not true. It does require some knowledge on the part of the developers and project leads, but nothing you can&#8217;t learn. For the users, if correctly implemented, it&#8217;s practically invisible. In short, it is not rocket science. It also does not require everyone to agree on a system beforehand, as too many people seem to think. You can do it, in your end-user apps, on your own, in a decent timeframe and without loss of user-friendliness. But someone has to show you how.</p>
<p>> I feel that the time is probably quite distant. There are hardly any<br />
> smart cards out there in the hands of my current users and the few<br />
> pilot installations that use personal smart card often get into<br />
> trouble.</p>
<p>It&#8217;s a chicken-and-egg problem. Also, we need a serious incident with really embarrassing data compromise to make this happen. We need a medical Enron or Card Systems event. Let&#8217;s just hope it doesn&#8217;t involve Profdoc. </p>
<p>The pilot installations I have seen that got into trouble did it wrong. You really have to have someone design it that understands it. You can&#8217;t run it politically, for instance.</p>
<p>> Or is this attitude just me being lazy and backwords, unwilling to<br />
> adapt to the future? I dont&#8217;t know.</p>
<p>No, it&#8217;s missing a great business opportunity. Users really do want better security and they&#8217;ll flock to the first vendor that takes it seriously. To the first vendor that actually begins doing something, even if it&#8217;s incomplete.</p>
<p>Again, I don&#8217;t understand you entirely, since you are doing something, but don&#8217;t seem to exploit that fact very much in your marketing (but I may be wrong, though).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TorbjÃ¶rn Hedberg</title>
		<link>http://ursecta.com/wp/2005/07/smart-cards-should-have-keypads-and-beepers/#comment-12</link>
		<dc:creator>TorbjÃ¶rn Hedberg</dc:creator>
		<pubDate>Mon, 01 Aug 2005 10:17:37 +0000</pubDate>
		<guid isPermaLink="false">http://ursecta.com/wp/?p=11#comment-12</guid>
		<description>You are, to the best my understanding, absolutely right. 

But does that automatically mean that I, being responsible for the development of one of the most used electronic health care record application in Sweden (Profdoc Journal III), should strive for the adoption these super-smart smart cards? Or even, as some PKI fundementalists in this country would have it, prohibit the sending of unsigned prescriptions?

Of course not. Sending unsigned prescriptions electronically is a big safety improvement over paper based prescriptions. The way things look right now, we should gladly keep promoting our current, not really really safe, way of doing things.  

The difficult question for me is therefore not technical (I'm not a deep technician) but timing. When is the right time for me to join the ranks of the PKI mafia and say "let's stop this unsafe electronic handling of medical information and start doing it right"? 

I feel that the time is probably quite distant. There are hardly any smart cards out there in the hands of my current users and the few pilot installations that use personal smart card often get into trouble. 

Or is this attitude just me being lazy and backwords, unwilling to adapt to the future? I dont't know.</description>
		<content:encoded><![CDATA[<p>You are, to the best my understanding, absolutely right. </p>
<p>But does that automatically mean that I, being responsible for the development of one of the most used electronic health care record application in Sweden (Profdoc Journal III), should strive for the adoption these super-smart smart cards? Or even, as some PKI fundementalists in this country would have it, prohibit the sending of unsigned prescriptions?</p>
<p>Of course not. Sending unsigned prescriptions electronically is a big safety improvement over paper based prescriptions. The way things look right now, we should gladly keep promoting our current, not really really safe, way of doing things.  </p>
<p>The difficult question for me is therefore not technical (I&#8217;m not a deep technician) but timing. When is the right time for me to join the ranks of the PKI mafia and say &#8220;let&#8217;s stop this unsafe electronic handling of medical information and start doing it right&#8221;? </p>
<p>I feel that the time is probably quite distant. There are hardly any smart cards out there in the hands of my current users and the few pilot installations that use personal smart card often get into trouble. </p>
<p>Or is this attitude just me being lazy and backwords, unwilling to adapt to the future? I dont&#8217;t know.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
