<?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 for Askarel labs</title>
	<atom:link href="http://www.askarel.be/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.askarel.be</link>
	<description>Technology, death metal and dirty hacks</description>
	<lastBuildDate>Wed, 04 Apr 2012 10:24:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on Wall wart hunting by An update to the wall wart hunting &#171; Askarel labs</title>
		<link>http://www.askarel.be/wall-wart-hunting/comment-page-1#comment-626</link>
		<dc:creator>An update to the wall wart hunting &#171; Askarel labs</dc:creator>
		<pubDate>Wed, 04 Apr 2012 10:24:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.askarel.be/?p=445#comment-626</guid>
		<description>[...] was some evolution since that article. The Power supply: a Velleman PSIN30012 I can has brackets [...]</description>
		<content:encoded><![CDATA[<p>[...] was some evolution since that article. The Power supply: a Velleman PSIN30012 I can has brackets [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Opening the Vasco Digipass 810 by Gov</title>
		<link>http://www.askarel.be/opening-the-vasco-digipass-810/comment-page-1#comment-608</link>
		<dc:creator>Gov</dc:creator>
		<pubDate>Thu, 01 Mar 2012 22:04:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.askarel.be/?p=290#comment-608</guid>
		<description>Damn, so it seems and indeed ridiculous :-\
http://www.vasco.com/support/knowledge_base/20022009/faq_20091013_990014.aspx</description>
		<content:encoded><![CDATA[<p>Damn, so it seems and indeed ridiculous :-\<br />
<a href="http://www.vasco.com/support/knowledge_base/20022009/faq_20091013_990014.aspx" rel="nofollow">http://www.vasco.com/support/knowledge_base/20022009/faq_20091013_990014.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on EPIC FAIL by nicodache</title>
		<link>http://www.askarel.be/epic-fail/comment-page-1#comment-404</link>
		<dc:creator>nicodache</dc:creator>
		<pubDate>Tue, 06 Sep 2011 12:27:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.askarel.be/?p=339#comment-404</guid>
		<description>m&#039;enfin ?!</description>
		<content:encoded><![CDATA[<p>m&#8217;enfin ?!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Opening the Vasco Digipass 810 by SecEng</title>
		<link>http://www.askarel.be/opening-the-vasco-digipass-810/comment-page-1#comment-390</link>
		<dc:creator>SecEng</dc:creator>
		<pubDate>Sun, 21 Aug 2011 14:52:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.askarel.be/?p=290#comment-390</guid>
		<description>If you&#039;d like to know something more on the &quot;algorithm&quot; to calculate your reply-challenge:

First of all, it would be very unsafe to have an amount of challenge codes in a database. These challenges are random generated numbers, and are generated when the client opens the web banking page.

The user (all of us humble home bankers) receives a challenge from his bank and feeds it to the Vasco Digipass, then the Digipass asks for your pin. If this is correct, the device has access to a number stored on the card. This number is unique and unknown to anybody, except the issuer (bank) and the card itself. This is of huge importance as otherwise it would be very easy to hack this system. Suppose that entering the PIN-code correctly would be the only thing to happen to have the correct challenge reply, then the response from every card to the MCU would always be the same (it would be: &quot;Pin code correct&quot;). If it&#039;s always the same, it would imply a very easy to hack system.

Actually this is a nice example of Message Authentication in standard cryptography: everybody (!!) can see the challenge to start communicating to the web banking server, and everybody can enter a challenge, yet only one unique device will be able to give the right answer (and thus to authenticate itself). 

Lastly, the protocol isn&#039;t really a secret. It&#039;s based on known cryptographic protocols (such as AES (aka Rijndael) or ECC or Grain or any other publicly known crypto. The worst choice would have been a &quot;secret&quot; protocol (it&#039;s called having security by obscurity), once the secret has been discovered: all hope is lost. Known (public) protocols have been tested and proofed for years! That is why cryptography is such a nice thing to study! ;-)</description>
		<content:encoded><![CDATA[<p>If you&#8217;d like to know something more on the &#8220;algorithm&#8221; to calculate your reply-challenge:</p>
<p>First of all, it would be very unsafe to have an amount of challenge codes in a database. These challenges are random generated numbers, and are generated when the client opens the web banking page.</p>
<p>The user (all of us humble home bankers) receives a challenge from his bank and feeds it to the Vasco Digipass, then the Digipass asks for your pin. If this is correct, the device has access to a number stored on the card. This number is unique and unknown to anybody, except the issuer (bank) and the card itself. This is of huge importance as otherwise it would be very easy to hack this system. Suppose that entering the PIN-code correctly would be the only thing to happen to have the correct challenge reply, then the response from every card to the MCU would always be the same (it would be: &#8220;Pin code correct&#8221;). If it&#8217;s always the same, it would imply a very easy to hack system.</p>
<p>Actually this is a nice example of Message Authentication in standard cryptography: everybody (!!) can see the challenge to start communicating to the web banking server, and everybody can enter a challenge, yet only one unique device will be able to give the right answer (and thus to authenticate itself). </p>
<p>Lastly, the protocol isn&#8217;t really a secret. It&#8217;s based on known cryptographic protocols (such as AES (aka Rijndael) or ECC or Grain or any other publicly known crypto. The worst choice would have been a &#8220;secret&#8221; protocol (it&#8217;s called having security by obscurity), once the secret has been discovered: all hope is lost. Known (public) protocols have been tested and proofed for years! That is why cryptography is such a nice thing to study! <img src='http://www.askarel.be/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Virement bancaire: communication structurée by Askarel</title>
		<link>http://www.askarel.be/virement-bancaire-communication-structuree/comment-page-1#comment-299</link>
		<dc:creator>Askarel</dc:creator>
		<pubDate>Fri, 10 Jun 2011 15:58:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.askarel.be/?p=347#comment-299</guid>
		<description>Exact.

Tu génère la communication structurée et tu la joint au numéro de facture/numéro de client dans ta base de données.
Un grep de la comm dans tes extraits de compte et tu sais si ton client a payé.

Tu n&#039;as pas besoin de savoir &lt;strong&gt;qui&lt;/strong&gt; paie.</description>
		<content:encoded><![CDATA[<p>Exact.</p>
<p>Tu génère la communication structurée et tu la joint au numéro de facture/numéro de client dans ta base de données.<br />
Un grep de la comm dans tes extraits de compte et tu sais si ton client a payé.</p>
<p>Tu n&#8217;as pas besoin de savoir <strong>qui</strong> paie.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Virement bancaire: communication structurée by Martial</title>
		<link>http://www.askarel.be/virement-bancaire-communication-structuree/comment-page-1#comment-298</link>
		<dc:creator>Martial</dc:creator>
		<pubDate>Fri, 10 Jun 2011 14:03:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.askarel.be/?p=347#comment-298</guid>
		<description>J&#039;ai toujours cru que les communications structurées pour les virements avaient pour but de vérifier le contenu du virement.
Ce n&#039;est donc vraiment pas le cas ?
C&#039;est donc juste pour avoir une sorte d&#039;identifiant pour le virement en lui même ?</description>
		<content:encoded><![CDATA[<p>J&#8217;ai toujours cru que les communications structurées pour les virements avaient pour but de vérifier le contenu du virement.<br />
Ce n&#8217;est donc vraiment pas le cas ?<br />
C&#8217;est donc juste pour avoir une sorte d&#8217;identifiant pour le virement en lui même ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Opening the Vasco Digipass 810 by Askarel</title>
		<link>http://www.askarel.be/opening-the-vasco-digipass-810/comment-page-1#comment-296</link>
		<dc:creator>Askarel</dc:creator>
		<pubDate>Thu, 09 Jun 2011 14:01:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.askarel.be/?p=290#comment-296</guid>
		<description>The batt+ and batt- test points are directly tied to the batteries.
I never tried that trick on such device, but it should work IMHO.

If it work for car batteries, why not on such device ? 

If you fry it in the process, well... At least you tried to save it.
In my case, i just asked for a new digipass from my bank. No question or money asked.</description>
		<content:encoded><![CDATA[<p>The batt+ and batt- test points are directly tied to the batteries.<br />
I never tried that trick on such device, but it should work IMHO.</p>
<p>If it work for car batteries, why not on such device ? </p>
<p>If you fry it in the process, well&#8230; At least you tried to save it.<br />
In my case, i just asked for a new digipass from my bank. No question or money asked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Opening the Vasco Digipass 810 by JeeCee</title>
		<link>http://www.askarel.be/opening-the-vasco-digipass-810/comment-page-1#comment-295</link>
		<dc:creator>JeeCee</dc:creator>
		<pubDate>Thu, 09 Jun 2011 11:27:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.askarel.be/?p=290#comment-295</guid>
		<description>I see there is a batt+ and batt- test point. So if I solder 2 wires to it, it can be connected to a power supply?

Let&#039;s say that the almost empty batteries provide a voltage of 5V instead of 6V (as fully charged). Then I must set my power supply to 5V or less. In this case the 2 CR2032 will not be charged hence will not explode. Correct? Then they could be removed and replaced by new ones...

Or am I overlooking something? :)</description>
		<content:encoded><![CDATA[<p>I see there is a batt+ and batt- test point. So if I solder 2 wires to it, it can be connected to a power supply?</p>
<p>Let&#8217;s say that the almost empty batteries provide a voltage of 5V instead of 6V (as fully charged). Then I must set my power supply to 5V or less. In this case the 2 CR2032 will not be charged hence will not explode. Correct? Then they could be removed and replaced by new ones&#8230;</p>
<p>Or am I overlooking something? <img src='http://www.askarel.be/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Opening the Vasco Digipass 810 by Askarel</title>
		<link>http://www.askarel.be/opening-the-vasco-digipass-810/comment-page-1#comment-274</link>
		<dc:creator>Askarel</dc:creator>
		<pubDate>Tue, 24 May 2011 22:18:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.askarel.be/?p=290#comment-274</guid>
		<description>That&#039;s an option.

If you keep the device powered, it will not notice the battery exchange, thus the RAM will keep it&#039;s content.

Something to test, but watch the power supply voltage carefully to avoid charging full batteries. Lithium cells are unforgiving and may blow up in your face.

Hope you have a steady hand. :-)</description>
		<content:encoded><![CDATA[<p>That&#8217;s an option.</p>
<p>If you keep the device powered, it will not notice the battery exchange, thus the RAM will keep it&#8217;s content.</p>
<p>Something to test, but watch the power supply voltage carefully to avoid charging full batteries. Lithium cells are unforgiving and may blow up in your face.</p>
<p>Hope you have a steady hand. <img src='http://www.askarel.be/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Opening the Vasco Digipass 810 by Zorro</title>
		<link>http://www.askarel.be/opening-the-vasco-digipass-810/comment-page-1#comment-273</link>
		<dc:creator>Zorro</dc:creator>
		<pubDate>Tue, 24 May 2011 21:17:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.askarel.be/?p=290#comment-273</guid>
		<description>Hey 
and if want to change the batteries and before doing that , you put another power source of the same voltage in parrallel? will the firmware  than also be wiped?</description>
		<content:encoded><![CDATA[<p>Hey<br />
and if want to change the batteries and before doing that , you put another power source of the same voltage in parrallel? will the firmware  than also be wiped?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

