You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add CHANGELOG.md and enhance error handling in DNS resolution
- Created CHANGELOG.md to document project changes and adhere to semantic versioning.
- Updated `resolveAttempts` function to return an error for invalid flag combinations, improving error handling.
- Adjusted main.go to handle errors from `resolveAttempts`, ensuring graceful exits on invalid input.
- Revised README.md to link to the new CHANGELOG.md for better visibility of project updates.
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone.
5
+
6
+
## Our Standards
7
+
Examples of behavior that contributes to a positive environment:
8
+
- Using welcoming and inclusive language
9
+
- Being respectful of differing viewpoints and experiences
10
+
- Gracefully accepting constructive criticism
11
+
- Focusing on what is best for the community
12
+
13
+
Examples of unacceptable behavior:
14
+
- Harassment, trolling, or insulting comments
15
+
- Public or private harassment
16
+
- Publishing others' private information without permission
17
+
- Other conduct which could reasonably be considered inappropriate
18
+
19
+
## Enforcement
20
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening a [Security Advisory](https://github.com/TMHSDigital/subenum/security/advisories/new) or contacting the maintainers privately.
21
+
22
+
## Attribution
23
+
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1.
Copy file name to clipboardExpand all lines: SECURITY.md
+7-15Lines changed: 7 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,22 +2,14 @@
2
2
3
3
## Reporting a Vulnerability
4
4
5
-
If you discover a security vulnerability in `subenum`, please follow these steps to report it responsibly:
5
+
If you discover a security vulnerability in `subenum`, **do not open a public issue.**
6
6
7
-
1.**Do NOT** disclose the vulnerability publicly until it has been addressed.
8
-
2. Send details of the vulnerability to the repository maintainers via GitHub Issues or create a private report through GitHub's Security tab.
9
-
3. Include the following information:
10
-
- A description of the vulnerability
11
-
- Steps to reproduce the issue
12
-
- Potential impact
13
-
- Any suggested fixes (if available)
7
+
Report it privately using GitHub's Security Advisory feature:
8
+
1. Go to the [Security tab](https://github.com/TMHSDigital/subenum/security/advisories/new) of this repository.
9
+
2. Click **"Report a vulnerability"**.
10
+
3. Fill in the description, reproduction steps, and impact.
14
11
15
-
## What to Expect
16
-
17
-
- You'll receive acknowledgment of your report within 48 hours.
18
-
- We'll investigate and provide an estimated timeline for a fix.
19
-
- You'll be kept informed about the progress.
20
-
- After the issue is resolved, you'll be credited for the discovery (unless you prefer anonymity).
12
+
You will receive acknowledgment within 48 hours. We will investigate, provide a fix timeline, keep you informed throughout, and credit you upon resolution (unless you prefer anonymity).
21
13
22
14
## Scope
23
15
@@ -33,4 +25,4 @@ Using this tool against systems without explicit permission is potentially illeg
33
25
34
26
## Thank You
35
27
36
-
Security researchers and responsible disclosure are vital to maintaining secure software. We appreciate your efforts to disclose vulnerabilities responsibly.
28
+
Security researchers and responsible disclosure are vital to maintaining secure software. We appreciate your efforts to disclose vulnerabilities responsibly.
0 commit comments