Difference between revisions of "Team:Edinburgh UG/Encryption"

 
(18 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
<head>
 
<head>
 
<meta charset="UTF-8" />
 
<meta charset="UTF-8" />
−
<title>Team:Edinburgh/Part Collection - 2015.igem.org</title>
 
 
<meta name="generator" content="MediaWiki 1.24.1" />
 
<meta name="generator" content="MediaWiki 1.24.1" />
 
<link rel="shortcut icon" href="/favicon.ico" />
 
<link rel="shortcut icon" href="/favicon.ico" />
Line 40: Line 39:
 
    {  t:"Team%3AEdinburgh%2FPart%20Collection",
 
    {  t:"Team%3AEdinburgh%2FPart%20Collection",
 
a:"View+%2FTeam%3AEdinburgh%2FPart_Collection++View source+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AEdinburgh%2FPart_Collection%26action%3Dedit++History+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AEdinburgh%2FPart_Collection%26action%3Dhistory++Move+%2FSpecial%3AMovePage%2FTeam%3AEdinburgh%2FPart_Collection++Watch+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AEdinburgh%2FPart_Collection%26action%3Dwatch%26token%3D98e620bce4d959b9b5d87d4afa3f1310%252B%255C++Page+%2FTeam%3AEdinburgh%2FPart_Collection++Discussion+%2Fwiki%2Findex.php%3Ftitle%3DTalk%3ATeam%3AEdinburgh%2FPart_Collection%26action%3Dedit%26redlink%3D1++" });
 
a:"View+%2FTeam%3AEdinburgh%2FPart_Collection++View source+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AEdinburgh%2FPart_Collection%26action%3Dedit++History+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AEdinburgh%2FPart_Collection%26action%3Dhistory++Move+%2FSpecial%3AMovePage%2FTeam%3AEdinburgh%2FPart_Collection++Watch+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AEdinburgh%2FPart_Collection%26action%3Dwatch%26token%3D98e620bce4d959b9b5d87d4afa3f1310%252B%255C++Page+%2FTeam%3AEdinburgh%2FPart_Collection++Discussion+%2Fwiki%2Findex.php%3Ftitle%3DTalk%3ATeam%3AEdinburgh%2FPart_Collection%26action%3Dedit%26redlink%3D1++" });
−
+
 
 
</script>
 
</script>
 
<div id="content" class="mw-body" role="main">
 
<div id="content" class="mw-body" role="main">
Line 73: Line 72:
 
}
 
}
 
   #globalWrapper
 
   #globalWrapper
−
     {
+
     {
 
width: 100%;
 
width: 100%;
 
height: 100%;
 
height: 100%;
Line 98: Line 97:
  
 
*/
 
*/
−
width: 100%;  
+
width: 100%;
−
height: 100%;  
+
height: 100%;
 
         margin: 0px;
 
         margin: 0px;
 
         padding: 0px;
 
         padding: 0px;
Line 161: Line 160:
 
     color: #fff;
 
     color: #fff;
 
     background-color: #000;
 
     background-color: #000;
−
     background: url("https://static.igem.org/mediawiki/2015/c/c7/Edigem15_collection_ferrylights.jpeg") no-repeat bottom center scroll;  
+
     background: url("https://static.igem.org/mediawiki/2016/3/3f/Rsz_encryption.jpg") no-repeat bottom center scroll;
 
     -webkit-background-size: cover;
 
     -webkit-background-size: cover;
 
     -moz-background-size: cover;
 
     -moz-background-size: cover;
Line 180: Line 179:
 
}
 
}
  
−
.intro .intro-body .intro-text {  
+
.intro .intro-body .intro-text {
 
     display: block;
 
     display: block;
 
     width: 100%;
 
     width: 100%;
Line 257: Line 256:
 
}
 
}
  
−
section h2.section-heading  
+
section h2.section-heading
 
{
 
{
 
     margin-top: 0;
 
     margin-top: 0;
Line 324: Line 323:
 
     text-transform: uppercase;
 
     text-transform: uppercase;
 
}
 
}
−
+
 
 
.btn:focus, .btn:active:focus, .btn.active:focus {
 
.btn:focus, .btn:active:focus, .btn.active:focus {
 
     outline: 0 none;
 
     outline: 0 none;
 
}
 
}
−
+
 
 
.btn-primary {
 
.btn-primary {
 
     background: #0099cc;
 
     background: #0099cc;
 
     color: #ffffff;
 
     color: #ffffff;
 
}
 
}
−
+
 
 
.btn-primary:hover, .btn-primary:focus, .btn-primary:active, .btn-primary.active, .open > .dropdown-toggle.btn-primary {
 
.btn-primary:hover, .btn-primary:focus, .btn-primary:active, .btn-primary.active, .open > .dropdown-toggle.btn-primary {
 
     background: #33a6cc;
 
     background: #33a6cc;
 
}
 
}
−
+
 
 
.btn-primary:active, .btn-primary.active {
 
.btn-primary:active, .btn-primary.active {
 
     background: #007299;
 
     background: #007299;
Line 375: Line 374:
 
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js"></script>
 
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js"></script>
 
     </head>
 
     </head>
−
   <!-- menu -->  
+
   <!-- menu -->
 
   <div id="custom-bootstrap-menu" class="navbar navbar-default navbar-fixed-top" role="navigation">
 
   <div id="custom-bootstrap-menu" class="navbar navbar-default navbar-fixed-top" role="navigation">
−
       <div class="container-fluid">
+
       <div class= "container-fluid">
−
          <div class="navbar-header">
+
        <!-- Navigation -->
−
              <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-menubuilder"><span class="sr-only">Toggle navigation</span><span class="icon-bar"></span><span class="icon-bar"></span><span class="icon-bar"></span>
+
        <nav class="navbar navbar-inverse navbar-fixed-top" role="navigation">
−
              </button>
+
            <div class="container">
−
          </div>
+
                <!-- Brand and toggle get grouped for better mobile display -->
−
          <div class="collapse navbar-collapse navbar-menubuilder">
+
                <div class="navbar-header">
−
              <ul class="nav navbar-nav navbar-right">
+
                    <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
−
                <li class="active">
+
                        <span class="sr-only">Toggle navigation</span>
−
                    <a href="https://2016.igem.org/Team:Edinburgh_UG">Home</a></li>
+
                        <span class="icon-bar"></span>
−
                    <li class="dropdown">
+
                        <span class="icon-bar"></span>
−
                      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Team<span class="caret"></span></a>
+
                        <span class="icon-bar"></span>
−
                      <ul class="dropdown-menu" role="menu">
+
                    </button>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Team">Team</a></li>
+
                    <a class="navbar-brand" href="https://2016.igem.org/Team:Edinburgh_UG">
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Collaborations">Collaboration</a></li>
+
                        <img src="https://static.igem.org/mediawiki/2016/9/92/Edinburgh_logo2_MINI.png" alt="">
−
                      </ul>
+
                    </a>
−
                    </li>
+
                </div>
−
                    <li class="dropdown">
+
 
−
                      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Project<span class="caret"></span></a>
+
                <!-- Collect the nav links, forms, and other content for toggling -->
−
                      <ul class="dropdown-menu" role="menu">
+
                <div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Description">Project</a></li>
+
                    <ul class="nav navbar-nav">
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Description">Description</a></li>
+
                        <li>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Design">Design</a></li>
+
                            <a href="https://2016.igem.org/Team:Edinburgh_UG">Home</a>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Experiments">Experiments</a></li>
+
                        </li>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Proof">Proof of Concept</a></li>
+
                        <li class="dropdown">
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Demonstrate">Demonstrate</a></li>
+
                          <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Team<span class="caret"></span></a>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Results">Results</a></li>
+
                          <ul class="dropdown-menu" role="menu">
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Notebook">Notebook</a></li>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Team">Team</a></li>
−
                      </ul>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Attribution">Attribution</a></li>
−
                    </li>
+
                          </ul>
−
                    <li class="dropdown">
+
                        </li>
−
                      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Parts<span class="caret"></span></a>
+
                        <li class="dropdown">
−
                      <ul class="dropdown-menu" role="menu">
+
                          <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Human Practices<span class="caret"></span></a>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Parts">Team Parts</a></li>
+
                          <ul class="dropdown-menu" role="menu">
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Basic_Part">Basic Parts</a></li>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Overview">Overview</a> </li>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Composite_Part">Composite Parts</a></li>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/HP/Silver">Silver</a> </li>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Part_Collection">Part Collection</a> </li>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/HP/Gold">Gold</a> </li>
−
                      </ul>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Medal_Criteria">Medal Criteria</a> </li>
−
                    </li>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Integrated_Practices">Integrated Practices</a> </li>
−
                    <li class="dropdown">
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Engagement">Engagement</a> </li>
−
                      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Dry Lab<span class="caret"></span></a>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Ethics">Ethics</a> </li>
−
                      <ul class="dropdown-menu" role="menu">
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Mary_Queen_of _Scots">Mary Queen of Scots</a> </li>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Lexicon_Encoding">Lexicon Encoding</a></li>
+
                          </ul>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Error_Correction">Error Correction</a></li>
+
                        </li>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Files">Files</a></li>
+
                        <li class="dropdown">
−
                      </ul>
+
                          <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Project<span class="caret"></span></a>
−
                    </li>
+
                          <ul class="dropdown-menu" role="menu">
−
                    <li class="dropdown">
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Description">Description</a></li>
−
                      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Safety<span class="caret"></span></a>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Design">Design</a></li>
−
                      <ul class="dropdown-menu" role="menu">
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Proof">Proof of Concept</a></li>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Safety">Safety</a></li>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Demonstrate">Demonstrate</a></li>
−
                      </ul>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Notebook">Notebook</a></li>
−
                    </li>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Protocols">Protocols</a></li>
−
                    <li class="dropdown">
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Limitations">Advantages and Limitations</a></li>
−
                      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Human Practices<span class="caret"></span></a>
+
                          </ul>
−
                      <ul class="dropdown-menu" role="menu">
+
                        </li>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Human_Practices">Human Practices</a></li>
+
                        <li class="dropdown">
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Silver">Silver</a> </li>
+
                          <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Informatics<span class="caret"></span></a>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Gold">Gold</a> </li>
+
                          <ul class="dropdown-menu" role="menu">
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Integrated_Practices">Integrated Practices</a> </li>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Lexicon_Encoding">Lexicon Encoding</a></li>
−
                         <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Engagement">Engagement</a> </li>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Error_Correction">Error Correction</a></li>
−
                      </ul>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Encryption">Encryption</a></li>
−
                    </li>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Files">Files</a></li>
−
                    <li class="dropdown">
+
                          </ul>
−
                      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Awards<span class="caret"></span></a>
+
                        </li>
−
                      <ul class="dropdown-menu" role="menu">
+
                        <li class="dropdown">
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Entrepreneurship">Entrepreneurship</a></li>
+
                          <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Parts<span class="caret"></span></a>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Hardware">Hardware</a> </li>
+
                          <ul class="dropdown-menu" role="menu">
−
                         <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Software">Software</a> </li>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Basic_Part">Basic Parts</a></li>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Measurement">Measurement</a> </li>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Composite_Part">Composite Parts</a></li>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Model">Model</a> </li>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Part_Collection">Part Collection</a> </li>
−
                      </ul>
+
                          </ul>
−
                    </li>
+
                        </li>
−
                    <li class="dropdown">
+
                         <li>
−
                      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Interlab<span class="caret"></span></a>
+
                            <a href="https://2016.igem.org/Team:Edinburgh_UG/Collaboration">Collaboration</a>
−
                      <ul class="dropdown-menu" role="menu">
+
                        </li>
−
                        <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Plate_Reader">Plate Reader</a></li>
+
                        <li class="dropdown">
−
                      </ul>
+
                          <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Awards<span class="caret"></span></a>
−
                    </li>
+
                          <ul class="dropdown-menu" role="menu">
−
              </ul>
+
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Software">Software</a> </li>
−
          </div>
+
                          </ul>
 +
                        </li>
 +
                         <li class="dropdown">
 +
                          <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Safety<span class="caret"></span></a>
 +
                          <ul class="dropdown-menu" role="menu">
 +
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Safety/Biological Safety">Biological Safety</a></li>
 +
                          </ul>
 +
                        </li>
 +
                        <li class="dropdown">
 +
                          <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Interlab<span class="caret"></span></a>
 +
                          <ul class="dropdown-menu" role="menu">
 +
                            <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Plate_Reader">Plate Reader</a></li>
 +
                          </ul>
 +
                        </li>
 +
                    </ul>
 +
                </div>
 +
                <!-- /.navbar-collapse -->
 +
            </div>
 +
            <!-- /.container -->
 +
        </nav>
 
       </div>
 
       </div>
 
   </div>
 
   </div>
 +
 +
  <!-- End of menu  -->
  
  
Line 491: Line 511:
 
                           <h2 class="section-heading">Introduction</h2>
 
                           <h2 class="section-heading">Introduction</h2>
 
                           <h11 class="section-subheading text-muted">
 
                           <h11 class="section-subheading text-muted">
−
                            Nowadays, security constitues a very big issue and need for all your devices, app, computers and so on. Also, for our system.The reason behind why we want to encrypt our data is that on a large scale, meaning a lot of people are using our system and algorithms to encode and decode text, the information might get stolen. The algorithms and procedure will be open source, so everyone can have access to it. In this case, if you send a DNA message to a friend, someone can steal it, decode it and visualize the information provided. In the case of shipping information in DNA, it is quite risky if another party finds out about it.
+
                          <p>Storing information isn’t as simple as finding a place to put it until you need it. The growth of digital information storage and transfer has also come with an increased demand for security and encryption. When we set out to design our modular DNA data storage system, we immediately thought of the question; is it possible to encrypt our DNA?</p>
−
    Our main usages of storing text into DNA are: storing data as archive and sending DNA messages. We consider that in both cases if the DNA is stolen most people with a biology lab can decrypt the message.
+
 
−
   
+
 
       <br>
 
       <br>
 
       <br>
 
       <br>
 
       <br>
 
       <br>
 
       <br>
 
       <br>
−
       Another threat can be discovered at the stage when the user wants to decode the DNA sequence into text. Because at this stage your DNA is into a computer which is linked to a network, the risk is quite high of being stolen. We indeed see that the system requests some security measures in order to keep data safe.
+
       </h11>
−
      In conclusion, the ‘threat’ is someone stealing the information when the DNA is sent to a different person or the archive data. In this way, the value of the data might be of high importance, so we need to find a way of protecting it, because our stored data needs to be secure.</h11>
+
                      </div>
 +
                      <br>
 +
                      <br>
 +
                      <div align="center">
 +
                          <a href="#accordion">
 +
                              <span class="arrowtext">Scroll down to read more</span>
 +
                              <img src="https://static.igem.org/mediawiki/2014/3/3e/Aalto_Helsinki_Nuoli.png" class="arrow">
 +
                          </a>
 
                       </div>
 
                       </div>
 
                   </div>
 
                   </div>
  
−
          <div class="panel panel-default">
 
  
−
              <div class="panel-heading">
 
  
−
                  <h4 class="panel-title">
+
                  <section id="about">
 +
                    <div class="container">
 +
                        <div class="row">
 +
                            <div class="col-lg-12 text-center">
 +
                                <h2 class="section-heading">Why encrypt?</h2>
 +
                                <h11 class="section-subheading text-muted">
 +
                              <p>Imagine you have just used our software to encode your data into BabbleBlocks….</p>
  
−
                      <a data-toggle="collapse" data-parent="#accordion" href="#collapseTwo">What does it used?</a>
+
            <br>
 +
            <br>
 +
            <br>
 +
            <br>
 +
            <p><strong>Scenario #1:</strong> When you decode your DNA, you are hacked and the data is stolen…</p>
 +
            <p>After retrieving your DNA sequencing results, you will input this back into our software for decoding. As your computer will most likely be connected to the internet, it is entirely possible for someone to steal your data during decode. </p>
 +
            <p><strong>Scenario #2:</strong> You have sequenced your DNA. Before you manage to decode the sequence, someone else gets a hold of it…</p>
 +
            <p>Similar to the situation above, it is possible that if your sequencing results are being sent to you online they could be intercepted or the file on your computer may be hacked. Our encryption system ensures that only those with the correct key will be able to decode the DNA sequence to the original data. </p>
 +
            <p><strong>Scenario #3:</strong> You want to send confidential data to someone, how can you prevent the message from being intercepted?</p>
 +
            <p>In the spirit of iGEM, our software and procedures will be open source. This means that if you were to send a DNA message to a friend, it would be possible to intercept the message and decode it using our systems.</p>
 +
            <p> A conversation with FBI Special Agent Edward You pointed out to us the importance of security in modern information transfer; in order for our method to be utilised by both private individuals and large scale companies, we need to incorporate a method of encryption that restricts decoding. Even archival data that is stored for long periods of time should have some level of encryption.</p>
  
−
                  </h4>
 
  
−
              </div>
 
  
−
              <div id="collapseTwo" class="panel-collapse collapse">
 
  
−
                  <div class="panel-body">
+
                </h11>
 +
                            </div>
 +
                            <div align="center">
 +
                                <a href="#accordion">
 +
                                      <span class="arrowtext">Scroll down to read more</span>
 +
                                      <img src="https://static.igem.org/mediawiki/2014/3/3e/Aalto_Helsinki_Nuoli.png" class="arrow">
 +
                                </a>
 +
                            </div>
 +
                            <br>
 +
                            <br>
 +
                        </div>
 +
              <section id="about">
 +
                    <div class="container">
 +
                        <div class="row">
 +
                            <div class="col-lg-12 text-center">
 +
                                <h2 class="section-heading">Overview of Encryption</h2>
 +
                                <h11 class="section-subheading text-muted">
 +
                                <p> We are using two methods for encrypting our DNA: Stream Cipher and RSA. RSA is a form of public-private key encryption, and ensures that when transferring information, only the intended party is capable of decoding the DNA. The public key from RSA is used to encrypt the DNA using a stream cipher; meaning that each BabbleBlock will be encrypted differently, based on the public key. The message can then only be decoded with the public key’s corresponding private key.</p>
 +
            <br>
 +
            <br>
 +
                                <div class="col-lg-12">
 +
                                <div class="featurette" id="contact">
 +
                                <img class="featurette-image img-responsive img-center" src="https://static.igem.org/mediawiki/2016/c/cb/Security_good.png">
 +
                                </div>
 +
            </h11>
 +
            <br>
 +
            <br>
 +
            <br>
 +
                            </div>
 +
                            <div align="center">
 +
                                <a href="#accordion">
 +
                                    <span class="arrowtext">Scroll down to read more</span>
 +
                                    <img src="https://static.igem.org/mediawiki/2014/3/3e/Aalto_Helsinki_Nuoli.png" class="arrow">
 +
                                </a>
 +
                            </div>
 +
                            <br>
 +
                            <br>
 +
                        </div>
 +
                <section id="about">
 +
                      <div class="container">
 +
                          <div class="row">
 +
                              <div class="col-lg-12 text-center">
 +
                                  <h2 class="section-heading">Other considerations</h2>
 +
                                  <h11 class="section-subheading text-muted">
  
−
                      <p>What we are using is:
+
              <br>
−
  <br>
+
              <br>
−
  Suggestion of using a cryptographic library or function, not building one.
+
                                  <p>Not all data needs to be encrypted. Additionally, developing a system that requires extensive network or computational stress goes against one of the main tenets of our system; sustainability. As such, we have designed this system as an optional bonus to our DNA Typewriter.</p>
−
  After a few meetings with computer security professors, all of them suggested to apply a Stream cipher. We adapted this Stream Cipher to base 4, in order to apply a key on DNA sequences. The only thing that we must take into account is that we need a different key for each sentence in order to make it harder to be cracked.
+
 
−
  Use RSA in order to encrypt and decrypt the key used as a seed.
+
            </h11>
−
  Use the seed in the random generating function in order to have the exact range of numbers as keys which you will going to use to encrypt the text.  
+
                              </div>
−
</p>
+
                            <div align="center">
 +
                                <a href="#accordion">
 +
                                    <span class="arrowtext">Scroll down to read more</span>
 +
                                    <img src="https://static.igem.org/mediawiki/2014/3/3e/Aalto_Helsinki_Nuoli.png" class="arrow">
 +
                                </a>
 +
                            </div>
 +
                            <br>
 +
                            <br>
 +
                          </div>
 +
              <section id="about">
 +
                    <div class="container">
 +
                        <div class="row">
 +
                            <div class="col-lg-12 text-center">
 +
                                <h2 class="section-heading">References</h2>
 +
                                <h11 class="section-subheading text-muted">
 +
                                <p>http://uk.emc.com/emc-plus/rsa-labs/standards-initiatives/advantages-and-disadvantages.htm</p>
 +
                                <p>For the page design, we used some features from the Edinburgh iGem Team 2015: https://2015.igem.org/Team:Edinburgh/InterLab</p>
 +
            <br>
 +
            <br>
  
−
                  </div>
+
            </h11>
 +
                            </div>
 +
                            <br>
 +
                            <br>
 +
                        </div>
  
−
              </div>
 
  
−
          </div>
 
−
   
 
  
  
Line 538: Line 637:
  
 
</p>
 
</p>
−
<!--  
+
<!--
 
NewPP limit report
 
NewPP limit report
 
CPU time usage: 0.006 seconds
 
CPU time usage: 0.006 seconds

Latest revision as of 00:04, 20 October 2016

Loading menubar.....

Team:Edinburgh/Part Collection

Encryption

Introduction

Storing information isn’t as simple as finding a place to put it until you need it. The growth of digital information storage and transfer has also come with an increased demand for security and encryption. When we set out to design our modular DNA data storage system, we immediately thought of the question; is it possible to encrypt our DNA?


Why encrypt?

Imagine you have just used our software to encode your data into BabbleBlocks….





Scenario #1: When you decode your DNA, you are hacked and the data is stolen…

After retrieving your DNA sequencing results, you will input this back into our software for decoding. As your computer will most likely be connected to the internet, it is entirely possible for someone to steal your data during decode.

Scenario #2: You have sequenced your DNA. Before you manage to decode the sequence, someone else gets a hold of it…

Similar to the situation above, it is possible that if your sequencing results are being sent to you online they could be intercepted or the file on your computer may be hacked. Our encryption system ensures that only those with the correct key will be able to decode the DNA sequence to the original data.

Scenario #3: You want to send confidential data to someone, how can you prevent the message from being intercepted?

In the spirit of iGEM, our software and procedures will be open source. This means that if you were to send a DNA message to a friend, it would be possible to intercept the message and decode it using our systems.

A conversation with FBI Special Agent Edward You pointed out to us the importance of security in modern information transfer; in order for our method to be utilised by both private individuals and large scale companies, we need to incorporate a method of encryption that restricts decoding. Even archival data that is stored for long periods of time should have some level of encryption.


Overview of Encryption

We are using two methods for encrypting our DNA: Stream Cipher and RSA. RSA is a form of public-private key encryption, and ensures that when transferring information, only the intended party is capable of decoding the DNA. The public key from RSA is used to encrypt the DNA using a stream cipher; meaning that each BabbleBlock will be encrypted differently, based on the public key. The message can then only be decoded with the public key’s corresponding private key.








Other considerations



Not all data needs to be encrypted. Additionally, developing a system that requires extensive network or computational stress goes against one of the main tenets of our system; sustainability. As such, we have designed this system as an optional bonus to our DNA Typewriter.


References

http://uk.emc.com/emc-plus/rsa-labs/standards-initiatives/advantages-and-disadvantages.htm

For the page design, we used some features from the Edinburgh iGem Team 2015: https://2015.igem.org/Team:Edinburgh/InterLab