Skip to content

Commit a4495a4

Browse files
dronefreakdronefreak
authored
Merge pull request #20 from dronefreak/dji-tello-object-detection-segmentation-v2
Add sec and code
2 parents 43993e0 + f7bcd17 commit a4495a4

File tree

2 files changed

+197
-0
lines changed

2 files changed

+197
-0
lines changed

‎.github/CODE_OF_CONDUCT.md‎

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
# Code of Conduct
2+
3+
## Our Pledge
4+
5+
We are committed to providing a welcoming and inclusive environment for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
6+
7+
## Our Standards
8+
9+
### Positive Behavior
10+
11+
- Using welcoming and inclusive language
12+
- Being respectful of differing viewpoints and experiences
13+
- Gracefully accepting constructive criticism
14+
- Focusing on what is best for the community
15+
- Showing empathy towards other community members
16+
- Helping newcomers and sharing knowledge
17+
18+
### Unacceptable Behavior
19+
20+
- Trolling, insulting/derogatory comments, and personal or political attacks
21+
- Public or private harassment
22+
- Publishing others' private information without explicit permission
23+
- Any conduct which could reasonably be considered inappropriate in a professional setting
24+
- Advocating for or encouraging any of the above behaviors
25+
26+
## Our Responsibilities
27+
28+
Project maintainers are responsible for clarifying standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
29+
30+
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct.
31+
32+
## Scope
33+
34+
This Code of Conduct applies to all project spaces, including the repository, issue tracker, discussions, and any other forums created by the project team. It also applies when an individual is representing the project or its community in public spaces.
35+
36+
## Enforcement
37+
38+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team through GitHub issues. All complaints will be reviewed and investigated promptly and fairly.
39+
40+
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
41+
42+
## Attribution
43+
44+
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
45+
46+
## Questions?
47+
48+
If you have questions about this Code of Conduct, please open an issue or discussion.

‎.github/SECURITY.md‎

Lines changed: 149 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,149 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
| Version | Supported |
6+
| ------- | ------------------ |
7+
| 2.0.x | :white_check_mark: |
8+
| < 2.0 | :x: |
9+
10+
## Reporting a Vulnerability
11+
12+
We take the security of Tello Vision seriously. If you discover a security vulnerability, please follow these steps:
13+
14+
### How to Report
15+
16+
1. **Do NOT create a public GitHub issue** for security vulnerabilities
17+
2. **Email the maintainers directly** or use GitHub's private vulnerability reporting feature
18+
3. **Open a private security advisory** at: `Security` → `Advisories` → `New draft security advisory`
19+
20+
### What to Include
21+
22+
When reporting a vulnerability, please include:
23+
24+
- Description of the vulnerability
25+
- Steps to reproduce the issue
26+
- Potential impact
27+
- Suggested fix (if you have one)
28+
- Your contact information
29+
30+
### Response Timeline
31+
32+
- **Initial Response**: Within 48 hours
33+
- **Status Update**: Within 7 days
34+
- **Fix Timeline**: Depends on severity
35+
- Critical: 1-7 days
36+
- High: 7-30 days
37+
- Medium: 30-90 days
38+
- Low: Best effort
39+
40+
## Security Considerations
41+
42+
### Drone Operations
43+
44+
⚠️ **This software controls physical drones. Use responsibly.**
45+
46+
- Always maintain visual line of sight
47+
- Test in safe, open environments
48+
- Keep firmware updated
49+
- Follow local aviation regulations
50+
- Never fly near people, airports, or restricted areas
51+
52+
### Network Security
53+
54+
- The DJI Tello creates an **unencrypted WiFi network**
55+
- Video stream is **not encrypted**
56+
- Control commands are sent over **UDP without authentication**
57+
- Assume anyone in range can intercept communications
58+
59+
**Mitigation:**
60+
61+
- Use in controlled environments only
62+
- Don't transmit sensitive information
63+
- Be aware of your surroundings
64+
65+
### Code Execution
66+
67+
This project:
68+
69+
- Downloads and executes ML models from external sources
70+
- Processes video streams (potential for adversarial attacks)
71+
- Uses third-party dependencies with their own security considerations
72+
73+
**Best Practices:**
74+
75+
- Only use models from trusted sources
76+
- Keep dependencies updated: `pip install --upgrade -r requirements.txt`
77+
- Review code before running in production environments
78+
- Use virtual environments to isolate dependencies
79+
80+
### Model Weights
81+
82+
Pre-trained models are downloaded from:
83+
84+
- Ultralytics (YOLOv8): https://github.com/ultralytics/assets/releases
85+
- Detectron2: https://dl.fbaipublicfiles.com/detectron2/
86+
87+
**Verify checksums** if using in security-sensitive applications.
88+
89+
## Known Limitations
90+
91+
### Not Production-Hardened For
92+
93+
- ❌ Mission-critical applications
94+
- ❌ Safety-critical systems
95+
- ❌ Environments requiring formal verification
96+
- ❌ Applications requiring encrypted communications
97+
98+
### Suitable For
99+
100+
- ✅ Research and development
101+
- ✅ Educational purposes
102+
- ✅ Prototyping and experimentation
103+
- ✅ Hobbyist projects
104+
105+
## Dependencies
106+
107+
We rely on several third-party packages. Security issues in dependencies should be reported to:
108+
109+
- **PyTorch**: https://github.com/pytorch/pytorch/security
110+
- **OpenCV**: https://github.com/opencv/opencv/security
111+
- **Ultralytics**: https://github.com/ultralytics/ultralytics/security
112+
- **djitellopy**: https://github.com/damiafuentes/DJITelloPy/security
113+
114+
## Security Updates
115+
116+
Security updates will be:
117+
118+
- Released as patch versions (2.0.x)
119+
- Announced in release notes
120+
- Tagged with `security` label in issues
121+
122+
## Responsible Disclosure
123+
124+
We follow a coordinated disclosure policy:
125+
126+
1. Vulnerability reported privately
127+
2. Issue confirmed and assessed
128+
3. Fix developed and tested
129+
4. Security advisory published
130+
5. Fix released
131+
6. Public disclosure after users have time to update
132+
133+
## Legal
134+
135+
This software is provided "AS IS" without warranty of any kind. Users are responsible for:
136+
137+
- Safe operation of drones
138+
- Compliance with local laws and regulations
139+
- Any damage or injury resulting from use
140+
141+
## Questions?
142+
143+
For non-security questions, use GitHub Discussions or Issues.
144+
145+
For security concerns, contact maintainers privately.
146+
147+
---
148+
149+
**Remember: Safety first. This controls a physical device that can cause injury or property damage if misused.**

0 commit comments

Comments
 (0)