"
Team:SYSU-Software/saft
From 2013.igem.org
(Difference between revisions)
| (46 intermediate revisions not shown) | |||
| Line 9: | Line 9: | ||
<link href="https://2012.igem.org/Team:SYSU-Software/flatui.css?action=raw&ctype=text/css" rel="stylesheet" type="text/css" /> | <link href="https://2012.igem.org/Team:SYSU-Software/flatui.css?action=raw&ctype=text/css" rel="stylesheet" type="text/css" /> | ||
<link href="https://2013.igem.org/Team:SYSU-Software/safety.css?action=raw&ctype=text/css" rel="stylesheet" type="text/css" /> | <link href="https://2013.igem.org/Team:SYSU-Software/safety.css?action=raw&ctype=text/css" rel="stylesheet" type="text/css" /> | ||
| + | <!-- <link href="safety/css/safety.css" rel="stylesheet" type="text/css" /> --> | ||
<link href="https://2013.igem.org/Team:SYSU-Software/header.css?action=raw&ctype=text/css" rel="stylesheet" type="text/css" /> | <link href="https://2013.igem.org/Team:SYSU-Software/header.css?action=raw&ctype=text/css" rel="stylesheet" type="text/css" /> | ||
| Line 24: | Line 25: | ||
<div id="navigation"></div> | <div id="navigation"></div> | ||
| - | + | <div class="wrapper colored-wrapper-ddf4ef"> | |
<div id="safety-container" > | <div id="safety-container" > | ||
<div id="safety-header"> | <div id="safety-header"> | ||
| - | |||
<img id="safety-font" src="https://static.igem.org/mediawiki/2013/4/4d/Safety-font.png"> | <img id="safety-font" src="https://static.igem.org/mediawiki/2013/4/4d/Safety-font.png"> | ||
| - | |||
</div> | </div> | ||
| + | <div class="safety-q" id="safety-q1"> | ||
| + | <span class="q-text" id="q2-text" style="color:orange"> | ||
| + | <span class="q-light" id="q2-light"> | ||
| + | <!-- <img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"> --> | ||
| + | </span><p style="display:inline-block">Safety forms were approved on September 17 2013,by Kelly Drinkwater<br><a href="https://static.igem.org/mediawiki/2013/0/07/IGEM_2013_Basic_Safety_Form%28SYSU-software%29-rev.pdf">IGEM_2013_Basic_Safety_Form.pdf</a><br><a href="https://static.igem.org/mediawiki/2013/5/5c/IGEM_2013_Software_form%28SYSU-software%29-rev.pdf">IGEM_2013_Software_form.pdf</a></p> | ||
| + | </span> | ||
| + | <span class="q-text" id="q2-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q1: Are you using the iGEM Software repository at github.com/igemsoftware?If you have instead stored your code elsewhere, please explain where and why you have put it there.If your code is not in the iGEM repository, are you using any version control | ||
| + | system such as Git, CVS, or SVN?</p></span> | ||
| - | + | <span class="q-pen" id="q1-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> | |
| - | <span | + | <span class="q-answer" id="q1-answer"> |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | <span | + | |
| - | + | ||
We will push our code to github.com/igemsoftware in time. However, the network connection between an overseas server and us is not satisfactory. So our code is stored at https://git.oschina.net/guoskyhero/igem2013_sysu/, and we use Git as the version control system. If there is any demand for our code, please feel free to contact us. | We will push our code to github.com/igemsoftware in time. However, the network connection between an overseas server and us is not satisfactory. So our code is stored at https://git.oschina.net/guoskyhero/igem2013_sysu/, and we use Git as the version control system. If there is any demand for our code, please feel free to contact us. | ||
</span> | </span> | ||
</div> | </div> | ||
| - | <div id="safety-q2"> | + | <div class="safety-q" id="safety-q2"> |
| - | <span id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span> | + | <span class="q-text" id="q2-text"> |
| - | + | <span class="q-light" id="q2-light"> | |
| + | <img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"> | ||
| + | </span> | ||
| + | <p>Q2: a. Does your software store any private data supplied by the user? (For example: | ||
the user's name and email address, passwords, DNA sequences, circuit designs, | the user's name and email address, passwords, DNA sequences, circuit designs, | ||
etc.) If yes, please describe what kind of data is stored. If no, skip the rest of this | etc.) If yes, please describe what kind of data is stored. If no, skip the rest of this | ||
| - | question and move on to question 3. </ | + | question and move on to question 3.</p> |
| - | + | </span> | |
| - | <span id="q2-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> | + | <span class="q-pen" id="q2-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> |
| - | <span id="q2-answer"> | + | <span class="q-answer" id="q2-answer"> |
Yes, our software stores user's name, gender, password, DNA sequences, circuit designs. | Yes, our software stores user's name, gender, password, DNA sequences, circuit designs. | ||
</span> | </span> | ||
| - | <span id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span> | + | </div> |
| - | + | <div class="safety-q" id="safety-q2"> | |
| - | the physical computer or hard drive that contains the user's private data?</span> | + | <span class="q-text" id="q2-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q2: b. What is the URL or IP address where the user's private data is stored? Where is |
| + | the physical computer or hard drive that contains the user's private data?</p></span> | ||
| - | <span id="q2-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> | + | <span class="q-pen" id="q2-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> |
| - | <span id="q2-answer"> | + | <span class="q-answer" id="q2-answer"> |
User's private data is stored on user's own PC or server. | User's private data is stored on user's own PC or server. | ||
</span> | </span> | ||
| - | <span id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span> | + | </div> |
| - | + | <div class="safety-q" id="safety-q2"> | |
| + | <span class="q-text" id="q2-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q2: c. Please describe any encryption, password protection, etc. that you use to protect | ||
the user's data. (It is not mandatory to have such protections, but if you do, | the user's data. (It is not mandatory to have such protections, but if you do, | ||
| - | describe them.)</span> | + | describe them.)</p></span> |
| - | <span id="q2-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> | + | <span class="q-pen" id="q2-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> |
| - | <span id="q2-answer"> | + | <span class="q-answer" id="q2-answer"> |
User's password is encrypted by Message-Digest Algorithm 5 (MD5). | User's password is encrypted by Message-Digest Algorithm 5 (MD5). | ||
</span> | </span> | ||
</div> | </div> | ||
| - | <div id="safety-q3"> | + | <div class="safety-q" id="safety-q3"> |
| - | <span id="q3-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span> | + | <span class="q-text" id="q3-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q3: Does your software include any other security features? Please describe them here.</p></span> |
| - | + | ||
| - | <span id="q3-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> | + | <span class="q-pen" id="q3-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> |
| - | <span id="q3-answer"> | + | <span class="q-answer" id="q3-answer"> |
The users are required to log in before using the software, and their designs are stored in their own account. We use a cryptographic algorithm to encrypt the user name and password when it is thansfered between the client and server. What's more, we create a different session key each time before the user login, which can resist the replay attack. | The users are required to log in before using the software, and their designs are stored in their own account. We use a cryptographic algorithm to encrypt the user name and password when it is thansfered between the client and server. What's more, we create a different session key each time before the user login, which can resist the replay attack. | ||
</span> | </span> | ||
</div> | </div> | ||
| - | <div id="safety-q4"> | + | <div class="safety-q" id="safety-q4"> |
| - | <span id="q4-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span> | + | <span class="q-text" id="q4-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q4: Does your software let the user create a design by choosing parts/genes from a |
| - | + | ||
list/database, such as the Registry? If so, which lists/databases are included? Is there any | list/database, such as the Registry? If so, which lists/databases are included? Is there any | ||
restriction on which parts/genes the user can choose? | restriction on which parts/genes the user can choose? | ||
| - | </span> | + | <p></span> |
| - | <span id="q4-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> | + | <span class="q-pen" id="q4-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> |
| - | <span id="q4-answer"> | + | <span class="q-answer" id="q4-answer"> |
Yes, our software let the users create a design by choosing parts/gene from the Registry. We didn't set restriction on which parts the user can choose, as the parts in the Registry is believed safe. | Yes, our software let the users create a design by choosing parts/gene from the Registry. We didn't set restriction on which parts the user can choose, as the parts in the Registry is believed safe. | ||
</span> | </span> | ||
</div> | </div> | ||
| - | <div id="safety-q5"> | + | <div class="safety-q" id="safety-q5"> |
| - | <span id="q5-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span> | + | <span class="q-text" id="q5-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q5: Does your software allow users to write new data into any public lists or databases? If so, |
| - | + | do you check the new data for errors before allowing it to be written?</p></span> | |
| - | do you check the new data for errors before allowing it to be written? | + | |
| - | </span> | + | |
| - | <span id="q5-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> | + | <span class="q-pen" id="q5-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> |
| - | <span id="q5-answer"> | + | <span class="q-answer" id="q5-answer"> |
No, our software doesn't allow users to write new data into public lists or database. | No, our software doesn't allow users to write new data into public lists or database. | ||
</span> | </span> | ||
</div> | </div> | ||
| - | <div id="safety-q6"> | + | <div class="safety-q" id="safety-q6"> |
| - | <span id="q6-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span> | + | <span class="q-text" id="q6-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q6: Does your software include any other features that encourage the user to create safe |
| - | + | designs? Please describe them here.</p></span> | |
| - | designs? Please describe them here.</span> | + | |
| - | <span id="q6-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> | + | <span class="q-pen" id="q6-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> |
| - | <span id="q6-answer"> | + | <span class="q-answer" id="q6-answer"> |
We set some reminders in the software, which encourage the user to create safe designs. | We set some reminders in the software, which encourage the user to create safe designs. | ||
</span> | </span> | ||
</div> | </div> | ||
| - | <div id="safety-q7"> | + | <div class="safety-q" id="safety-q7"> |
| - | <span id="q7-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span> | + | <span class="q-text" id="q7-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q7: Is your team also doing biological work in a wet lab?If so, you need to complete the iGEM Biosafety form on 2013.igem.org/Safety.</p></span> |
| - | + | <span class="q-pen" id="q7-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> | |
| - | + | <span class="q-answer" id="q7-answer"> | |
| - | <span id="q7-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span> | + | Yes. |
| - | <span id="q7-answer"> | + | </span> |
| - | + | ||
| - | </span> | + | </div> |
| - | </div> | + | |
</div> | </div> | ||
| - | |||
<!--page footer--> | <!--page footer--> | ||
<div id="sysu-footer"> | <div id="sysu-footer"> | ||
<img id="bottom-image" src="https://static.igem.org/mediawiki/2013/d/d9/Sysu-footer.png"> | <img id="bottom-image" src="https://static.igem.org/mediawiki/2013/d/d9/Sysu-footer.png"> | ||
</div> | </div> | ||
| + | </div> | ||
| + | |||
</body> | </body> | ||
</html> | </html> | ||
Latest revision as of 18:05, 27 September 2013
Safety forms were approved on September 17 2013,by Kelly Drinkwater
IGEM_2013_Basic_Safety_Form.pdf
IGEM_2013_Software_form.pdf
Q1: Are you using the iGEM Software repository at github.com/igemsoftware?If you have instead stored your code elsewhere, please explain where and why you have put it there.If your code is not in the iGEM repository, are you using any version control system such as Git, CVS, or SVN?
We will push our code to github.com/igemsoftware in time. However, the network connection between an overseas server and us is not satisfactory. So our code is stored at https://git.oschina.net/guoskyhero/igem2013_sysu/, and we use Git as the version control system. If there is any demand for our code, please feel free to contact us.
Q2: a. Does your software store any private data supplied by the user? (For example: the user's name and email address, passwords, DNA sequences, circuit designs, etc.) If yes, please describe what kind of data is stored. If no, skip the rest of this question and move on to question 3.
Yes, our software stores user's name, gender, password, DNA sequences, circuit designs.
Q2: b. What is the URL or IP address where the user's private data is stored? Where is the physical computer or hard drive that contains the user's private data?
User's private data is stored on user's own PC or server.
Q2: c. Please describe any encryption, password protection, etc. that you use to protect the user's data. (It is not mandatory to have such protections, but if you do, describe them.)
User's password is encrypted by Message-Digest Algorithm 5 (MD5).
Q3: Does your software include any other security features? Please describe them here.
The users are required to log in before using the software, and their designs are stored in their own account. We use a cryptographic algorithm to encrypt the user name and password when it is thansfered between the client and server. What's more, we create a different session key each time before the user login, which can resist the replay attack.
Q4: Does your software let the user create a design by choosing parts/genes from a list/database, such as the Registry? If so, which lists/databases are included? Is there any restriction on which parts/genes the user can choose?
Yes, our software let the users create a design by choosing parts/gene from the Registry. We didn't set restriction on which parts the user can choose, as the parts in the Registry is believed safe.
Q5: Does your software allow users to write new data into any public lists or databases? If so, do you check the new data for errors before allowing it to be written?
No, our software doesn't allow users to write new data into public lists or database.
Q6: Does your software include any other features that encourage the user to create safe designs? Please describe them here.
We set some reminders in the software, which encourage the user to create safe designs.
Q7: Is your team also doing biological work in a wet lab?If so, you need to complete the iGEM Biosafety form on 2013.igem.org/Safety.
Yes.
