drogonframework/drogon

Security

Open

#646 opened on Dec 8, 2020

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C++ (1,014 forks)batch import
enhancementgood first issue

Repository metrics

Stars
 (10,462 stars)
PR merge metrics
 (Avg merge 5d 16h) (3 merged PRs in 30d)

Description

How is security preparation for both of maintainers and drogon users ? Here are something I hope in drogon's roadmap : some security advice with drogon specific code in the documentation , default security tightening in starter projects (example, authentication and authorization in default state of starter projects) and security enhancement in default state of drogon .

In PHP world, here is some notable security advice of yii2 framework maintainers with yii2 specific codes : https://www.yiiframework.com/doc/guide/2.0/en/security-overview

Thank you for your awesome library.

Contributor guide

Research direction
Examine the existing security documentation in Drogon's repository, compare with best practices (e.g., OWASP), and propose concrete changes for default security settings and starter project templates. Consider adding middleware for common security headers and input validation.
Tech stack
cpp
Domain
backendsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40