<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">
	<channel>
<title>moller hansen&#x27;s blog</title><link>http://www.mollerhansen.com/index.html</link><description>Davids ideas and experience in his life</description><dc:language>en</dc:language><dc:creator>david@mollerhansen.com</dc:creator><dc:rights>Copyright 2008 David Hansen</dc:rights><dc:date>2010-01-12T22:53:30+01:00</dc:date><admin:generatorAgent rdf:resource="http://www.realmacsoftware.com/" />
<admin:errorReportsTo rdf:resource="mailto:david@mollerhansen.com" /><sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
<lastBuildDate>Tue, 12 Jan 2010 23:09:07 +0100</lastBuildDate><item><title>Assisted eyewitnessing</title><dc:creator>david@mollerhansen.com</dc:creator><category>@surveillance</category><category>@random</category><dc:date>2010-01-12T22:53:30+01:00</dc:date><link>http://www.mollerhansen.com/Blog/files/5867b4c040b5c3fd784e5852d6c426c0-14.php#unique-entry-id-14</link><guid isPermaLink="true">http://www.mollerhansen.com/Blog/files/5867b4c040b5c3fd784e5852d6c426c0-14.php#unique-entry-id-14</guid><content:encoded><![CDATA[Assisted eye witnessing is crowd sourced surveillance.   Imagine everyone had the possibility to acquire a magical little camera with compass an gps receiver.   Lets say it is in their eyes, so always seeing what the person wearing it sees.


Now let us look at the crowd sourced surveillance aspect.   Imagine a criminals face were released as a small file by the police that  then could be used in face recognition software.   Now every one would have the possibility to run their recordings against the face file. 


If you found a face you would simply notify the authorities and handover your recording with the face part.


Now let us look at some of the problems in this system:


1) Protecting the witness (anonymity) 


How do we protect the witness from not being revealed to the criminal if not wanting to? 


2) Ensuring authenticity of the face file and the sender.


How do we make sure that the police send the face file and that it is indeed the criminals face?


3) Technology


Putting stuff in peoples eye... probably not, but in their sunglasses.. maybe..


Conclusion: Technology is the least problem of the above mentioned three. ]]></content:encoded></item><item><title>Thesis is handed in</title><dc:creator>david@mollerhansen.com</dc:creator><category>@dtu</category><category>@cryptography</category><category>@math</category><category>@code</category><dc:date>2009-03-02T21:04:24+01:00</dc:date><link>http://www.mollerhansen.com/Blog/files/b8dde11467724168f64c3b0e81345dbd-13.php#unique-entry-id-13</link><guid isPermaLink="true">http://www.mollerhansen.com/Blog/files/b8dde11467724168f64c3b0e81345dbd-13.php#unique-entry-id-13</guid><content:encoded><![CDATA[So I finally handed in my thesis on Pairing-based Cryptography.


I have put up my thesis under files as a pdf file.


And I&rsquo;ve bundled


	▪	BLS_instances.


	▪	Code.


	▪	Report.


	▪	Report_LaTeX_source.


	▪	Sage_Examples.


	▪	Sage_interacts.


	▪	Sage_BLS_Patch.


on my files page as well in a zipped file.


It ended rather well I think, but I didn&rsquo;t get as much blogged as I wanted to. 


There will in the coming weeks be a blog post on developing for the sage project and I will of course put up the slides from my defence which by the way is in building 306, room 038.
]]></content:encoded></item><item><title>Pairing based crypto III: The Weil pairing</title><dc:creator>david@mollerhansen.com</dc:creator><category>@code</category><category>@cryptography</category><category>@dtu</category><category>@math</category><dc:date>2008-12-14T13:16:53+01:00</dc:date><link>http://www.mollerhansen.com/Blog/files/dae4a52f93b417ebbc55b621f4c2a18c-11.php#unique-entry-id-11</link><guid isPermaLink="true">http://www.mollerhansen.com/Blog/files/dae4a52f93b417ebbc55b621f4c2a18c-11.php#unique-entry-id-11</guid><content:encoded><![CDATA[In this third blog post on my master thesis on Pairing Based Cryptography I will discuss the Weil pairing and how to implement it efficiently using  Victor Millers algorithm.


Let us start by quickly defining the Weil pairing.   I actually go a step back and construct in my thesis, a little technical but worth the work, even though we&rsquo;ll just skip that part. 


Definition:


Let E be an elliptic curve defined over a field K and let n be a positive integer then the Weil pairing is defined as:


<center>


</center>


where   is the set of n&rsquo;th roots of unity. 


The pairing have the following properties (and more):


	i	 is billinear in each variable


	ii	 is non-degenerate in each variable


	iii	 is alternating


	iv	 preserves skew symmetry


From the billinearity we get that linear depending points  will always have the pairing value .   Also remember that it was the property billinearity we needed to make our short signature scheme possible.


The Weil pairing can be computed as


Let  and  be divisors of degree 0 such that


<center>


,	


</center>


and  and  share no points.   Let   and  be functions s.t.


<center>


  and .


</center>


Then the Weil pairing can be written on the form


<center>


	


</center>


Suppose further that a point  is given. 


Then  (divisors share class),  and  do not have any points in common and


<center>


	.


</center>


Let , Miller realised that the function f can be constructed using an double-and-add in n algorithm by values of straight lines in points.


Let  be the value of the equation for the straight line intersecting in P and Q taking in the point S.   Note that it S will not lie on the line and therefore not give the value zero.


Then Millers algorithm for computing the value of  :


Taking advantage of the representation of n.


In the article Refinements of Miller's algorithm for computing the Weil/Tate pairing Blake et al. describe algorithms for the case of low or average Hamming weight of n.   The Hamming weight of n clearly have some impact on the running time of the above algorithm.


To give a picture of the algorithm choice I made a SAGE interact that writes out in latex the unevaluated expression generated in the algorithm for computing f.   This will in some way let us see the &ldquo;length&rdquo; of the expression and theirby provide us a loose measure of the time to compute f.   The interact is included in the still very early release of my digital signature implementation in SAGE.  


Tripling in base 3


The reason for including the base three algorithms is that I look at curves over finite fields of characteristic three in my thesis.   In these fields tripling a value is faster than doubling, and if in a normal base in the field then the tripling operation becomes just a shift operation.
]]></content:encoded></item><item><title>Sage BLS signature scheme </title><dc:creator>david@mollerhansen.com</dc:creator><category>@code</category><category>@cryptography</category><category>@dtu</category><dc:date>2008-11-16T19:20:38+01:00</dc:date><link>http://www.mollerhansen.com/Blog/files/053c9a949df022172b66d72a28b3a688-10.php#unique-entry-id-10</link><guid isPermaLink="true">http://www.mollerhansen.com/Blog/files/053c9a949df022172b66d72a28b3a688-10.php#unique-entry-id-10</guid><content:encoded><![CDATA[So I finally got my sage implementation of the BLS short signature scheme uploaded.   I have placed it on my files page. 


Please feel free to download it and modify it in any way.


A small disclaimer: I take absolutely no responsibility of what you might do with the code.  ]]></content:encoded></item><item><title>Pairing based crypto II: Shorter signatures</title><dc:creator>david@mollerhansen.com</dc:creator><category>@dtu</category><category>@cryptography</category><category>@math</category><dc:date>2008-11-14T22:20:31+01:00</dc:date><link>http://www.mollerhansen.com/Blog/files/ac1918115af9566d0dcb72c2c3946a59-9.php#unique-entry-id-9</link><guid isPermaLink="true">http://www.mollerhansen.com/Blog/files/ac1918115af9566d0dcb72c2c3946a59-9.php#unique-entry-id-9</guid><content:encoded><![CDATA[In this second blog post on my master thesis on Pairing Based Cryptography I will talk about the application of PBC to get short digital signatures.


So in general a digital signature is consisting of the secret key in an assymetric cryptographic scheme.   The key length therefore will dictate the signature length, in DSA the current length considered being secure is 1024 bits.   Using elliptic curve cryptography the recommended ECDSA length is 320 bits.   With pairings we can actually get the same security for only 170 bits - that&rsquo;s almost half!   This was what Boneh, Lynn and Shacham published an article on in 2004.


Why should the signatures be shorter then?   Static space constraints - we simply want as much bang for the buck we can get on a fixed number of bits.   Let it be barcoded signatures or legacy protocols with fixed length fields for signatures.


The way to shave half the bits of is by using pairings!    More precisely using parings to get a gap Diffie-Hellman (GDH) group pair, better start of by defining this.


A group pair (G1,G2) is a GDH group pair if the following properties holds:


	▪	Computations in each groups can be done efficiently.


	▪	The Decision co-Diffie-Hellman problem (DDH) is easy.


	▪	The Computational co-Diffie-Hellman problem (CDH) is hard.


The idea of the signature scheme is that from the above latter two properties we are able to decide wether the signature is valid or not but we are not able to compute a forgery of the signature.  


The way we get the second property is by having a bilinear mapping available of the two groups (G1,G2) onto a third group, the pairing function is exactly the bilinear map we need.   Using Victor Millers formula, we can efficiently compute the pairing and this way solve the DDH problem efficiently.


So how did we save those bits anyway? - Well without getting into detail on the ECDSA scheme (please read up on it yourself) that scheme requires two values of approximately 160 bits each and we only need one value in the PBC scheme namely a single point coordinate of size 160 bits.


I will try to outline the BLS short signature scheme.


Key generation:


Choose a random number as the private key and multiply the generator point in G2 with this to get the public key.


Signing:


Hash your message to a point in G1 and multiply with the private key.


Note that the hardness of the CDH problem protects our signature from forgeries, since we&rsquo;re not able to  


Verifying:


As mentioned before the idea is now to decide if (generator of G2, public key, point hash, signature) is a Diffie-Hellman tuple.


I have implemented a proof of concept in Sage.   I am currently trying to get it packaged with some sample parameters and hope to get the code up on the homepage ASAP.   When this happens please feel free to comment on it. 


This naturally also leads me to my next blog post coming up (hopefully soon) on Sage and doing discrete mathematics with sage. 
]]></content:encoded></item><item><title>Top 5 LaTeX thesis tips</title><dc:creator>david@mollerhansen.com</dc:creator><category>@code</category><category>@dtu</category><category>@math</category><dc:date>2008-11-05T22:13:56+01:00</dc:date><link>http://www.mollerhansen.com/Blog/files/7709621350b38782cb70c65e0aa923a5-8.php#unique-entry-id-8</link><guid isPermaLink="true">http://www.mollerhansen.com/Blog/files/7709621350b38782cb70c65e0aa923a5-8.php#unique-entry-id-8</guid><content:encoded><![CDATA[I am currently writing my master thesis and I have found the following 5 things very usefull to know so far...   I have tried to rate the tips and you will probably not agree unless your in the middle of the thesis like me.


1. todonotes package


The top of my list will be taken by the todo.sty file by Henrik Skov Midtiby.   This is a great tool for keeping track of the stuff you need to correct or be reminded of in your LaTeX document later on.   It simply puts a box with a todo on the right hand side of the text or make the box inline with the text if you wish.   I&rsquo;ve used it for of cause my own todo&rsquo;s but also as a place to put small questions on the side for my professors to notice when they read up on what I&rsquo;m doing in my draft papers.


2. hyperref package


Clickable pdf&rsquo;s are good pdf&rsquo;s.   The hyperref package by Heiko Oberdiek and Sebastian Rahtz makes your document references clickable and in all the colours you want.   What you basically get is a hyperlink as the reference instead of using \ref{} that &ldquo;just&rdquo; gives prints the reference.   I like to write what i&rsquo;m referencing, e.g. a lemma or a theorem, and for this I usually call hyperref in the following way \hyperref[label]{lemma \ref{label}}.


3. attachfiles2 package


The attachfile2 package by Heiko Oberdiek is really cool.   Especially when your writing scripts that goes with your thesis, e.g. a magma or SAGE script that you otherwise would include as text and as a seperate file on the disc when you hand in your thesis.   It basically makes a link in the pdf document like the hyperref package and when pressed your are asked if you want to save a file to disc.   Apparently the pdf standard supports attached files, who would have known.   Thanks to Martin Edwards for bringing this to my attention.  


4.   Master thesis templates


Just before you hand in I want you not to have another LaTeX package, just a good advice.   Often some one at your University have all ready written his or her thesis work in LaTeX and probably been with more time on the hand than you are now.   He or she have maybe evene produced a university themed LaTeX template in a way that made the professors at your department make the person put it up on the official webpage.   And even if no one at your department have done anything then maybe some one at another department have.   Let me remind you I&rsquo;m writing a thesis at the mathematics department at DTU but I&rsquo;m considering using this LaTeX template.  


5. beamer package


When you get to the point where you have to do a thesis defense it is usually nice to bring somekind of presentation but you would rather don&rsquo;t have to  convert all your equations to .png format only to realize a typo in the last hour before the defense.   All this is solved by the beamer package  by Till Tantau which magically makes it possible to do the whole presentation using only LaTeX!   I&rsquo;m so looking forward to my defense now.
]]></content:encoded></item><item><title>The Code Book</title><dc:creator>david@mollerhansen.com</dc:creator><category>@home</category><category>@math</category><category>@cryptography</category><dc:date>2008-11-03T20:14:29+01:00</dc:date><link>http://www.mollerhansen.com/Blog/files/e64ec13a26870c9be6cbc06b2aefe8df-6.php#unique-entry-id-6</link><guid isPermaLink="true">http://www.mollerhansen.com/Blog/files/e64ec13a26870c9be6cbc06b2aefe8df-6.php#unique-entry-id-6</guid><content:encoded><![CDATA[So I finally finished reading The Code Book by Simon Singh. 


I read the danish publication of the book and here&rsquo;s what I think...


It is certanly a well written book, and I do not believe that many people can wrap substitution or Vigenere ciphers in a more interesting blanket of cryptographic history.    I may have read the book with the wrong pair of glasses.   I expected more theoretical cryptography.   I&rsquo;m sorry to say that the explanations is not that interesting and hard to read over since they are filtered in with the otherwise interesting historical perspective.   I think I would have been more satisfied if I were spared from the longish explanations of the theory in the somewhat to superficial way and then just in stead finished the first chapters of the book earlier.


Now if you skip the first half of the book and go straight for the Enigma part then it gets interesting!   This is the place where I think we get more history and less of the superficial theory.   Really great stuff and written again in a fantastic interesting way!   Now the reason for the exclamation mark comes from the fact that I never really where interested in history surrounding the world wars but the author certainly flipped that on the head. 


The latter part of the book continue following the people whom had played a big part of deciphering the Enigma code and wasn&rsquo;t allowed to tell anyone about the work they did at Bletchley Park before the 1970&rsquo;s.   The transition into public key cryptography there after is also very good and the last chapters on PGP and future of cryptography is a fair ending.   But the crown juwel of this book is definetly the chapters on Enigma and they alone kept me from discarding the book before its end.


So my recommendation is to indeed borrow this book and read the chapters on the Enigma machine and if you are intrigued then read on!  


I think that the author have made a large enough impression to make me want to read his othe book on Fermat's Last Theorem.      ]]></content:encoded></item><item><title>Twitter integration</title><dc:creator>david@mollerhansen.com</dc:creator><category>@code</category><category>@home</category><dc:date>2008-10-24T14:34:08+02:00</dc:date><link>http://www.mollerhansen.com/Blog/files/e19a3fe840ba56480a2a85eba590ca28-3.php#unique-entry-id-3</link><guid isPermaLink="true">http://www.mollerhansen.com/Blog/files/e19a3fe840ba56480a2a85eba590ca28-3.php#unique-entry-id-3</guid><content:encoded><![CDATA[So I&rsquo;m on Twitter if you haven&rsquo;t guessed it yet.   You can follow me at twitter.com/mollerhansen.   The thing I&rsquo;m most interested in after redesigning and restarting my webpage is to make it more interesting to use for myself.   I&rsquo;m editing the webpage in a WYSIWYG editor and this is mainly to make it easier to just throw something up here.   I was doing this before but in a more half assed I-want-control-over-the-code-way so I spend more time editing the code the editor produced than actually blogging about the stuff I wanted to get out here.


Another thing I wanted to revise was the availability of the site and the knowledge of it&rsquo;s existence.   For this I&rsquo;ve chosen to integrate it with the Twitter service such that my latest twitters will appear on the right side of the page.   This do not really solve the problem of publishing the page to a larger audience, but actually just makes the small existing audience awear of my micro-blogging on twitter - not that this is bad in any way - unless they all prefer the short form.   So to additionally get the reverse effect I&rsquo;ve set up an RSS feed from this blog page and then pass it on to twitter with a tinylink to the blog posts.


How did I do it.   When I set out to embark on this Twitter integration then I discovered how easy this integration was!   That&rsquo;s not an everyday thing - and this is why I want to tell you about it - just spreading a little sunshine...


So to set up my twitters on the right I just went to twitter.com/badges and chose other/ HTML/javascript version badge.   Then my editor just got the the code snippet and ate it in the costumize sidebar field and even formatted the text to the theme i use.


Next the other way around.   The RSS feed is again just an automatic part of the blog page I crated in the WYSIWYG editor so no problem here.   If you go to twitterfeed.com you can sign up using openID (get one if you haven&rsquo;t one yet - it&rsquo;s going to be the next big thing..   ;-).   Here you can set up a service which listens to what-ever RSS feed you select (including your own) and updates within the hour on twitter when a new feed item is posted.


Couldn&rsquo;t be mouch easier!   Or could it? 


I&rsquo;m actully not keen on the idea of having a 3rd party service in between mollerhansen.com and twitter.com. 


But you can&rsquo;t get everything you want and I&rsquo;m still satisfied.ip


 


 
]]></content:encoded></item><item><title>Pairing based crypto I: History</title><dc:creator>david@mollerhansen.com</dc:creator><category>@math</category><category>@dtu</category><dc:date>2008-10-22T22:53:55+02:00</dc:date><link>http://www.mollerhansen.com/Blog/files/e924db0b21bc53d9eee323a5517c9729-2.php#unique-entry-id-2</link><guid isPermaLink="true">http://www.mollerhansen.com/Blog/files/e924db0b21bc53d9eee323a5517c9729-2.php#unique-entry-id-2</guid><content:encoded><![CDATA[This is my first blog post in a series on the subject my masters thesis; Pairing Based Cryptography.


Naturally I will have to start by introducing my masters thesis.   My thesis is on an applied math field called Pairing Based Cryptography (PBC).   This is a fairly new field of assymetric cryptography (&asymp;10 years) and as the name preludes it is using something called pairings.   I will not at this time explain what a pairing is, but instead outline the history of pairing based cryptography.   I will try to link extensively throughout my posts in the series so if you are curious you yourself can explore the field of PBC on your own hand. 


The pairing I use in my project is a bilinear mapping from an elliptitc curve group into a finite field called the Weil pairing.   There exist several different mappings falling into the definition of a pairing: Tate pairing, Ate pairing, Eta pairing etc.   These are all important pairings like the Weil pairing with different advantages and disadvantages when using them in PBC.


The map I use have been around since Karl Wilhelm Theodor Weierstrass (1815-1897) introduced it as the sigma function on elliptic curves.   Andr&eacute; Weil (1906-1998) gave a more abstract definition of this mapping in his first proof of the Riemann hypothesis for arbitrary genus curves over finite fields [Sur les fonctions alg&eacute;briques &agrave; corps de constantes finis, C.R.   Academie des Sciences, 1940].   For those like me that do not read french yet, he references and restates his pairing definition in the article [On the Riemann hypothesis in function-fields, New School for social research, 1941] (pdf).


In 1984 Adi Shamir (1952- )proves that Identity-based cryptographic schemes exists.   [Identity-based cryptosystems and signature schemes, proc.   Crypto 84 on advances in cryptology,1984]


In 1986 Victor S.   Miller writes an article on effecient computations of function on abelian varieties.[  Short Programs for functions on Curves, IBM, Thomas J.   Watson Research Center, 1986] (pdf).


In 1991 Menezes, Okamoto and Vanstone shows that some supersingular curves should be avoided.   They have found a way to use the Weil pairing to reduce the security of the discrete logarithm problem in the elliptic curve groups to the discrete logarithm problem in a finite field of small embedding degree.   [Reducing elliptic curve logarithms to logarithms in a finite field, ACM, 1991]


In 1994 Gerhard Frey and Hans-Georg R&uuml;ck showed a similar result using the Tate pairing.   [A remark concerning m-divisibility and the discrete logarithm in the divisor class group of curves, 1994]


In 2000 Antoine Joux uses pairings to create a One-round-key  scheme.   The year after Verheul gave a self-blinable credential certificate scheme using the Weil pairing.   Some argue Joux was the first to give a pairing based cryptographic cheme, but in fact Mitsunari,Sakai and Kasahara  in 1999 and Sakai, Oghishi and Kashara in 2000 presented work on the subject prior of Joux.   These schemes were though first reckognised in the west 2002.


Dan Boneh and Matt Franklin gives an identity based scheme using the Weil pairing in 2001.   [Identity-Based Encryption from the Weil Pairing,proc.   Crypto 2001 on advances in cryptology, 2001 ]


A lot of pairing based cryptographic schemes have since been defined but I want to mention another PBC scheme by Boneh, since this is what I am working on in my thesis at the moment this blog post was written; the BLS signature scheme that was proposed by Boneh, Lynn and Schacham [Short Signatures from the Weil Pairing, Journal of cryptology, 2004].


The current development in PBC seem to be focused on hyperelliptic curves (genus >1).   These curves was proposed to be used for cryptography early on but had inefficient methods of doing arithemetic, this have since changed.   Maybe I will get back to this when I myself know more about it. 


   ]]></content:encoded></item><item><title>Redesign</title><dc:creator>david@mollerhansen.com</dc:creator><category>@home</category><category>@code</category><dc:date>2008-10-17T02:24:48+02:00</dc:date><link>http://www.mollerhansen.com/Blog/files/96357eb73af994183557fd32118e125e-1.php#unique-entry-id-1</link><guid isPermaLink="true">http://www.mollerhansen.com/Blog/files/96357eb73af994183557fd32118e125e-1.php#unique-entry-id-1</guid><content:encoded><![CDATA[I am currently rebooting my homepage, so some fluctuations will occur in content, page design etc. in the comming time]]></content:encoded></item></channel>
</rss>