Browse Source

forum security

pull/487/head
lee 5 years ago
parent
commit
fef99ec392
  1. 38
      subjects/forum/forum-security.audit.en.md
  2. 42
      subjects/forum/forum-security.en.md

38
subjects/forum/forum-security.audit.en.md

@ -0,0 +1,38 @@
#### Functional
##### Try opening the forum.
###### Does the URL contain HTTPS?
###### Is the Go TLS structure well configured?
###### Is the database encrypt?
##### Try creating a user. Go to the database using the command `"sqlite3 <database-name>"` and run `"SELECT * FROM <user-table>;"` to select all users.
###### Are the passwords encrypted?
##### Try to login into the forum and open the inspector(CTRL+SHIFT+i) and go to the storage to see the cookies(this can be different depending on the [browser](https://developer.mozilla.org/en-US/docs/Learn/Common_questions/What_are_browser_developer_tools)).
###### Does the session cookie present a unique identifier?
#### General
###### +Does the project implement their own certificates for the HTTPS protocol?
###### +Does the project implement UUI(Universal Unique Identifier) for the user session?
###### +Does the project implement [environment variables](https://en.wikipedia.org/wiki/Environment_variable) (.env file), for the TLS certificates?
#### Basic
###### +Does the project runs quickly and effectively? (no unnecessary data requests, etc)
###### +Does the code obey the [good practices](https://public.01-edu.org/subjects/good-practices.en)?
###### +Is there a test file for this code?
#### Social
###### +Did you learn anything from this project?
###### +Can it be open-sourced / be used for other sources?
###### +Would you recommend/nominate this program as an example for the rest of the school?

42
subjects/forum/forum-security.en.md

@ -0,0 +1,42 @@
## forum-security
### Objectives
You must follow the same [principles](https://public.01-edu.org/subjects/forum/forum.en) as the first subject.
For this project you must take into account the security of your forum.
- You should implement a Hypertext Transfer Protocol Secure ([HTTPS](https://www.globalsign.com/en/blog/the-difference-between-http-and-https)) protocol :
- Encrypted connection : for this you will have to generate an SSL certificate, you can think of this like a identity card for your website. You can create your certificates or use "Certificate Authorities"(CA's)
- You should encrypt :
- Clients passwords
- Database
- Clients session cookies should be unique. For instance, the session state is stored on the server and the session should present an unique identifier. This way the client has no direct access to it. Therefore, there is no way for attackers to read or tamper with session state.
This project will help you learn about :
- HTTPS
- Encryption
- Database
- password
- session/cookies
- Universal Unique Identifier (UUI)
### Hints
- You can take a look at the `openssl` manual.
- For the session cookies you can take a look at the [Universal Unique Identifier (UUI)](https://en.wikipedia.org/wiki/Universally_unique_identifier)
### Instructions
- You must handle website errors, HTTPS status.
- You must handle all sort of technical errors.
- The code must respect the [**good practices**](https://public.01-edu.org/subjects/good-practices.en).
- It is recommend that the code should present a **test file**.
### Allowed packages
- All [standard go](https://golang.org/pkg/) packages are allowed.
- golang.org/x/crypto/bcrypt
- github.com/satori/go.uuid
Loading…
Cancel
Save