We actively maintain and provide security updates for the DevopsLab Git Mastery repository:
| Version | Supported |
|---|---|
| Latest | β Yes |
| < 1.0 | β No |
We take security seriously in our Git learning scenarios. If you discover a security issue, please follow these steps:
- DO NOT create a public GitHub issue
- Send an email to: [shubhadeep010@gmail.com]
- Include "SECURITY - DevopsLab" in the subject line
- Description of the security concern
- Which Git scenario or day it affects
- Potential impact on learners
- Suggested fix (if you have one)
- Initial Response: Within 48 hours
- Status Update: Within 7 days
- Fix Timeline: 30 days (depending on severity)
- Practice in isolated environments - Don't use production repositories
- Understand commands before executing them
- Use proper authentication - SSH keys, not passwords
- Keep Git updated - Use recent versions
- Be cautious with hooks - Review before enabling
Our scenarios teach secure practices:
- Proper authentication setup
- Safe remote repository handling
- Hook validation before execution
- Commit signing best practices
- Sensitive data handling in repositories
This repository is designed for learning purposes:
- All scenarios are safe for educational use
- No production data should be used
- Practice repositories are disposable
- Remote simulations use local bare repositories
For security-related questions:
- π§ Email: [shubhadeep010@gmail.com]
- π¬ GitHub Discussions: [Security Category]
Note: While learning Git, always prioritize security best practices in real-world applications.