This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "OWASP Go Secure Coding Practices Guide"

From OWASP
Jump to: navigation, search
(Created page with "<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">link=</div> {| style="padding: 0;margin:0;margin-top:10px;text-alig...")
 
(project description)
Line 4: Line 4:
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
  
−
<span style="color:#ff0000">
 
−
Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.
 
−
</span>
 
 
==Project About==
 
==Project About==
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
Line 15: Line 12:
 
}}
 
}}
  
 +
==OWASP Go Secure Coding Practices Guide==
  
−
==OWASP Documentation Project Template==
+
Go Language - Web Application Secure Coding Practices is a guide written for anyone who is using the Go Programming Language and aims to use it for web
−
<span style="color:#ff0000">
+
development.
−
This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.
 
−
</span>
 
  
−
The OWASP Documentation Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects.  By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.
+
The main goal of this book is to help developers avoid common mistakes while at the same time, learning a new programming language through a "hands-on approach".
  
 
==Description==
 
==Description==
−
<span style="color:#ff0000">
 
−
This is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, so project leaders should ensure that the description is meaningful. 
 
−
</span>
 
  
−
The Documentation Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Documentation project. After copying this template to your new project, all you have to do is follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red. Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category. The information requested is also intended to help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort.
+
According to Stack Overflow’s annual Developer Survey, Go has made the top 5 most Loved and Wanted programming languages list for the second year in a row.
 +
With its surge in popularity, it is critical that applications developed in Go are designed with security in mind.
 +
 
 +
The primary audience of the Go Secure Coding Practices Guide is developers, particularly the ones with previous experience with other programming languages.
 +
 
 +
The book is also a great reference to those learning programming for the first time, who have already finish the [https://tour.golang.org/list Go tour].
  
−
Creating a new set of project pages from scratch can be a challenging task.  By providing a sample layout, with instructional text and examples, the OWASP Documentation Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security.
+
This book covers the [[OWASP_Secure_Coding_Practices_-_Quick_Reference_Guide|OWASP Secure Coding Practices Quick Reference Guide]] topic-by-topic, providing examples and recommendations using Go, to help developers avoid common mistakes and pitfalls.
  
−
Contextual custom dictionary builder with character substitution and word variations for pen-testers
+
After reading this book, you'll be more confident you're developing secure Go applications.
  
 
==Licensing==
 
==Licensing==
−
<span style="color:#ff0000">
 
−
A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses OWASP Licenses]. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects.  This example assumes that you want to use the AGPL 3.0 license.
 
−
</span>
 
  
−
This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html link GNU Affero General Public License 3.0] as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. OWASP XXX and any contributions are Copyright &copy; by {the Project Leader(s) or OWASP} {Year(s)}.
+
This document is released under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0)]. For any reuse or distribution, you must make clear to others the license terms of this work.
  
 
==Roadmap==
 
==Roadmap==
−
<span style="color:#ff0000">
 
−
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
 
−
<strong>
 
−
* Complete the first draft of the Documentation Project Template
 
−
* Get other people to review the Documentation Project Template and provide feedback
 
−
* Incorporate feedback into changes in the Documentation Project Template
 
−
* Finalize the Documentation Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
 
−
</strong>
 
  
−
Subsequent Releases will add
+
TBA
−
<strong>
 
−
* Internationalization Support
 
−
* Additional Unit Tests
 
−
* Automated Regression tests
 
−
</strong>
 
  
 
==Getting Involved==
 
==Getting Involved==
−
<span style="color:#ff0000">
+
 
−
Involvement in the development and promotion of <strong>Documentation Project Template</strong> is actively encouraged!
+
Involvement in the development and promotion of <strong>Go Secure Coding Practices</strong> is actively encouraged!
 
You do not have to be a security expert or a programmer to contribute.
 
You do not have to be a security expert or a programmer to contribute.
−
Some of the ways you can help are as follows:
+
 
 +
Please refer to the [https://github.com/OWASP/Go-SCP/blob/master/CONTRIBUTING.md CONTRIBUTING.md] for details on how to contribute to OWASP Go Secure Coding Practices Guide.
  
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
  
 
== Project Resources ==
 
== Project Resources ==
−
<span style="color:#ff0000">
 
−
This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc.
 
−
</span>
 
  
−
[https://github.com/SamanthaGroves Installation Package]
+
Last release download
 +
[https://github.com/OWASP/Go-SCP/blob/master/dist/go-webapp-scp.pdf PDF], [https://github.com/OWASP/Go-SCP/blob/master/dist/go-webapp-scp.mobi MOBI],
 +
[https://github.com/OWASP/Go-SCP/blob/master/dist/go-webapp-scp.epub ePub]
  
−
[https://github.com/SamanthaGroves Source Code]
+
[https://github.com/OWASP/Go-SCP Repository]
  
−
[https://github.com/SamanthaGroves What's New (Revision History)]
+
[https://github.com/OWASP/Go-SCP/issues Issue Tracker]
−
 
 
−
[https://github.com/SamanthaGroves Documentation]
 
−
 
 
−
[https://github.com/SamanthaGroves Wiki Home Page]
 
−
 
 
−
[https://github.com/SamanthaGroves Issue Tracker]
 
−
 
 
−
[https://github.com/SamanthaGroves Slide Presentation]
 
−
 
 
−
[https://github.com/SamanthaGroves Video]
 
  
 
== Project Leader ==
 
== Project Leader ==
−
<span style="color:#ff0000">
 
−
A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members.
 
−
</span>
 
  
 
[mailto://[email protected] Erez Yalon]
 
[mailto://[email protected] Erez Yalon]
  
 
== Related Projects ==
 
== Related Projects ==
−
<span style="color:#ff0000">
+
 
−
This is where you can link to other OWASP Projects that are similar to yours.
+
* [[OWASP_Secure_Coding_Practices_-_Quick_Reference_Guide|OWASP Secure Coding Practices Quick Reference Guide]]
−
</span>
 
−
* [[OWASP_Code_Project_Template]]
 
−
* [[OWASP_Tool_Project_Template]]
 
  
 
==Classifications==
 
==Classifications==

Revision as of 10:03, 29 July 2019

OWASP Project Header.jpg

Project About

PROJECT INFO
What does this OWASP project offer you? 		RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: Go Secure Coding Practices Guide
Purpose: N/A
License: N/A
who is working on this project?
Project Leader(s):
  • Erez Yalon @
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: N/A
Project Roadmap: Not Yet Created
Key Contacts
  • Contact Erez Yalon @ to contribute to this project
  • Contact Erez Yalon @ to review or sponsor this project
current release
last reviewed release


other releases

OWASP Go Secure Coding Practices Guide

Go Language - Web Application Secure Coding Practices is a guide written for anyone who is using the Go Programming Language and aims to use it for web development.

The main goal of this book is to help developers avoid common mistakes while at the same time, learning a new programming language through a "hands-on approach".

Description

According to Stack Overflow’s annual Developer Survey, Go has made the top 5 most Loved and Wanted programming languages list for the second year in a row. With its surge in popularity, it is critical that applications developed in Go are designed with security in mind.

The primary audience of the Go Secure Coding Practices Guide is developers, particularly the ones with previous experience with other programming languages.

The book is also a great reference to those learning programming for the first time, who have already finish the Go tour.

This book covers the OWASP Secure Coding Practices Quick Reference Guide topic-by-topic, providing examples and recommendations using Go, to help developers avoid common mistakes and pitfalls.

After reading this book, you'll be more confident you're developing secure Go applications.

Licensing

This document is released under the Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0). For any reuse or distribution, you must make clear to others the license terms of this work.

Roadmap

TBA

Getting Involved

Involvement in the development and promotion of Go Secure Coding Practices is actively encouraged! You do not have to be a security expert or a programmer to contribute.

Please refer to the CONTRIBUTING.md for details on how to contribute to OWASP Go Secure Coding Practices Guide.

Project Resources

Last release download PDF, MOBI, ePub

Repository

Issue Tracker

Project Leader

Erez Yalon

Related Projects

Classifications

Project Type Files DOC.jpg
Incubator Project Owasp-builders-small.png
Owasp-defenders-small.png
Creative Commons Attribution ShareAlike 3.0 License

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Go_Secure_Coding_Practices_Guide&oldid=253368"