<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://www.baszerr.eu/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>BaSzErr - blog:2013:02:10</title>
        <description></description>
        <link>https://www.baszerr.eu/</link>
        <lastBuildDate>Wed, 06 May 2026 09:37:50 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>https://www.baszerr.eu/lib/exe/fetch.php?media=wiki:dokuwiki.svg</url>
            <title>BaSzErr</title>
            <link>https://www.baszerr.eu/</link>
        </image>
        <item>
            <title>password_cracking_vs_time</title>
            <link>https://www.baszerr.eu/doku.php?id=blog:2013:02:10:password_cracking_vs_time</link>
            <description>
&lt;h1 class=&quot;sectionedit1&quot; id=&quot;password_cracking_vs_time&quot;&gt;2013.02.10 - password cracking vs. time&lt;/h1&gt;
&lt;div class=&quot;level1&quot;&gt;

&lt;p&gt;
when talking about passwords or passwords&amp;#039; (salted) hashes and time required to break them, we assume that passwords that will take significant amount of years to be break are secure. for instance say you have 10 digits password, with lower and upper case characters, digits and special characters. assuming no extra knowledge about the password, this gives about 82 possible characters at each position. having 10 characters means 13744803133596058624 (~10^19) possible passwords.
&lt;/p&gt;

&lt;p&gt;
now assume that you can check 2 millions passwords per second, which gives 63072000000000 attempts per year (~10^14). btw: note that 2 millions attempts per second is not that much – in fact &lt;a href=&quot;https://en.wikipedia.org/wiki/MD5&quot; class=&quot;interwiki iw_wp&quot; title=&quot;https://en.wikipedia.org/wiki/MD5&quot;&gt;MD5&lt;/a&gt; can be &lt;a href=&quot;https://en.wikipedia.org/wiki/MD5#Security&quot; class=&quot;urlextern&quot; title=&quot;https://en.wikipedia.org/wiki/MD5#Security&quot; rel=&quot;ugc nofollow&quot;&gt;cracked at a speed of about 200 million passwords per second, on a modern GPU&lt;/a&gt;).
&lt;/p&gt;

&lt;p&gt;
using the usual approach, this means that we need:
&lt;/p&gt;
&lt;pre class=&quot;code&quot;&gt;13744803133596058624 / 63072000000000 = 217922&lt;/pre&gt;

&lt;p&gt;
wow – 217922 years to break it. sounds serious? well… there is “a little” flaw in this approach – we assume the same computer will do the calculations thought all that period. although &lt;a href=&quot;https://en.wikipedia.org/wiki/Moore&#039;s law&quot; class=&quot;interwiki iw_wp&quot; title=&quot;https://en.wikipedia.org/wiki/Moore&amp;#039;s law&quot;&gt;Moore&amp;#039;s law&lt;/a&gt; is no longer valid, &lt;a href=&quot;http://www.drdobbs.com/parallel/welcome-to-the-parallel-jungle/232400273&quot; class=&quot;urlextern&quot; title=&quot;http://www.drdobbs.com/parallel/welcome-to-the-parallel-jungle/232400273&quot; rel=&quot;ugc nofollow&quot;&gt;since few years now&lt;/a&gt;, and is expected to end for good &lt;a href=&quot;http://www.drdobbs.com/parallel/welcome-to-the-parallel-jungle/232400273?pgno=3&quot; class=&quot;urlextern&quot; title=&quot;http://www.drdobbs.com/parallel/welcome-to-the-parallel-jungle/232400273?pgno=3&quot; rel=&quot;ugc nofollow&quot;&gt;in a foreseeable future&lt;/a&gt;, due to the physical size limits of the transistor, computing power is not doomed. it is just more networked and more parallel over a time. derived from the Moore&amp;#039;s law we could expect roughly 2x speedup over 18 months&lt;sup&gt;&lt;a href=&quot;#fn__1&quot; id=&quot;fnt__1&quot; class=&quot;fn_top&quot;&gt;1)&lt;/a&gt;&lt;/sup&gt;. this gives about 1.33 speedup a year. what is happening is &lt;a href=&quot;http://www.drdobbs.com/parallel/welcome-to-the-parallel-jungle/232400273?pgno=3&quot; class=&quot;urlextern&quot; title=&quot;http://www.drdobbs.com/parallel/welcome-to-the-parallel-jungle/232400273?pgno=3&quot; rel=&quot;ugc nofollow&quot;&gt;we have more than that with the could computing&lt;/a&gt; taking over.
&lt;/p&gt;

&lt;p&gt;
even assuming we have &lt;em&gt;pps=1.33&lt;/em&gt; (processing power) speedup a year, and are starting with &lt;em&gt;apy~=10^14&lt;/em&gt; attempts per year for &lt;em&gt;N&lt;/em&gt; years we compute a following number of passwords:
&lt;/p&gt;
&lt;pre class=&quot;code&quot;&gt;pps*apy^0 + pps*apy^1 + pps*apy^2 + ... + pps*apy^(N-1)&lt;/pre&gt;

&lt;p&gt;
this is of course geometric sequence sum, which is:
&lt;/p&gt;
&lt;pre class=&quot;code&quot;&gt;apy*(1-pps^N)/(1-pps)&lt;/pre&gt;

&lt;p&gt;
to see how many years will it actually take we need to solve the equation:
&lt;/p&gt;
&lt;pre class=&quot;code&quot;&gt;apy*(1-pps^N)/(1-pps) = ctt&lt;/pre&gt;

&lt;p&gt;
whre &lt;em&gt;ctt&lt;/em&gt; is combinations to test (in our example ~10^19). a little maths and we come up with:
&lt;/p&gt;
&lt;pre class=&quot;code&quot;&gt;N = ln((apy-ctt*(1-pps))/apy) / ln(pps)&lt;/pre&gt;

&lt;p&gt;
which in our example gives… &lt;strong&gt;38 years&lt;/strong&gt;! though this is a long time, comparing it to the original results of 217922 years, this gives a significant error! to make things worse, we assumed full search, while on average you are expected to find the result after doing just half of all computations (here: after 36 years). this is hell a lot of time, but definitely within ones lifetime. if you add more computational power, say 1000 machines, we can narrow it to 14 years, and if hash happened to be MD5… on average we&amp;#039;re expected to find answer in just over a year!
&lt;/p&gt;

&lt;p&gt;
if you&amp;#039;d like to toy around with with parameters here is the &lt;a href=&quot;https://en.wikipedia.org/wiki/bc programming language&quot; class=&quot;interwiki iw_wp&quot; title=&quot;https://en.wikipedia.org/wiki/bc programming language&quot;&gt;BC&lt;/a&gt; script for &lt;a href=&quot;https://www.baszerr.eu/lib/exe/fetch.php?media=blog:2013:02:10:expected_password_crack_time.txt&quot; class=&quot;media mediafile mf_txt&quot; title=&quot;blog:2013:02:10:expected_password_crack_time.txt (903 B)&quot;&gt;calculating expected time to crack a password&lt;/a&gt;.
&lt;/p&gt;

&lt;/div&gt;
&lt;div class=&quot;footnotes&quot;&gt;
&lt;div class=&quot;fn&quot;&gt;&lt;sup&gt;&lt;a href=&quot;#fnt__1&quot; id=&quot;fn__1&quot; class=&quot;fn_bot&quot;&gt;1)&lt;/a&gt;&lt;/sup&gt; 
&lt;div class=&quot;content&quot;&gt;though Moore says about transistors, not the computational power, but the correlation is strong enough here&lt;/div&gt;&lt;/div&gt;
&lt;/div&gt;
</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Tue, 15 Jun 2021 20:09:07 +0000</pubDate>
        </item>
        <item>
            <title>via_neural_interface</title>
            <link>https://www.baszerr.eu/doku.php?id=blog:2013:02:10:via_neural_interface</link>
            <description>
&lt;h1 class=&quot;sectionedit1&quot; id=&quot;via_neural_interface&quot;&gt;2013.02.10 - via neural interface&lt;/h1&gt;
&lt;div class=&quot;level1&quot;&gt;

&lt;p&gt;
&lt;a href=&quot;https://www.baszerr.eu/lib/exe/detail.php?id=blog%3A2013%3A02%3A10%3Avia_neural_interface&amp;amp;media=blog:2013:02:10:on_iss.jpg&quot; class=&quot;media&quot; title=&quot;blog:2013:02:10:on_iss.jpg&quot;&gt;&lt;img src=&quot;https://www.baszerr.eu/lib/exe/fetch.php?w=400&amp;amp;tok=0854a6&amp;amp;media=blog:2013:02:10:on_iss.jpg&quot; class=&quot;mediaright&quot; align=&quot;right&quot; loading=&quot;lazy&quot; title=&quot;work in zero gravity (picture taken from http://www.unifiedrepublicofstars.com/wp-content/uploads/2012/02/DanBurbank.jpg)&quot; alt=&quot;work in zero gravity (picture taken from http://www.unifiedrepublicofstars.com/wp-content/uploads/2012/02/DanBurbank.jpg)&quot; width=&quot;400&quot; /&gt;&lt;/a&gt;
yesterday at night, wile &lt;a href=&quot;https://www.baszerr.eu/doku.php?id=blog:2013:02:09:programming_wat&quot; class=&quot;wikilink1&quot; title=&quot;blog:2013:02:09:programming_wat&quot; data-wiki-id=&quot;blog:2013:02:09:programming_wat&quot;&gt;doing some scripting&lt;/a&gt;, i had a chat with a friend, who&amp;#039;s about to visit an oculist, due to spending too much time in front of computer(s). since my eyes were already tired i just though how nice would it be to have a neural-computer interface operational, so that you could I/O with any machine w/o a need to use eyes nor any muscle. you could just plug yourself in, close eyes, lay down and enjoy the pure information stream. even if your tired for this, you can still disconnect and have eyes not tired and fully operational to do other things. and what if lying is not convenient enough? well – imagine doing the same, but in a zero gravity…
&lt;/p&gt;

&lt;p&gt;
ps&lt;br/&gt;

just for the record – there are &lt;a href=&quot;https://www.youtube.com/watch?&amp;amp;v=OW2pBLQLHj0&quot; class=&quot;urlextern&quot; title=&quot;https://www.youtube.com/watch?&amp;amp;v=OW2pBLQLHj0&quot; rel=&quot;ugc nofollow&quot;&gt;solutions that do muscle impulses reading&lt;/a&gt; or even &lt;a href=&quot;https://www.youtube.com/watch?v=m57GnaJ-_oE&quot; class=&quot;urlextern&quot; title=&quot;https://www.youtube.com/watch?v=m57GnaJ-_oE&quot; rel=&quot;ugc nofollow&quot;&gt;brain wave readings&lt;/a&gt;, to perform certain tasks. muscle reading already works fine, if you like to move. :) it&amp;#039;s a bit worse when talking about the brainwaves. though you can even &lt;a href=&quot;http://www.inc.com/magazine/20081201/reality-bites.html&quot; class=&quot;urlextern&quot; title=&quot;http://www.inc.com/magazine/20081201/reality-bites.html&quot; rel=&quot;ugc nofollow&quot;&gt;buy some basic devices to do that&lt;/a&gt;, its still more of a research quality, than the real alternative for screen and keyboard. we still need to wait – hopefully not to long… :)
&lt;/p&gt;

&lt;/div&gt;
</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Tue, 15 Jun 2021 20:09:07 +0000</pubDate>
        </item>
    </channel>
</rss>
