Contact information to report a serious security vulnerablity
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
Research direction
The issue names no files, tests, or code entry points; it asks for the correct contact to report a serious cryptography vulnerability. First check the repository's existing security-reporting information, if available; done means a maintainer provides a reliable contact point or the repository documents one.
Written by the indexing model from the issue text.
Description
Greetings. Over a week ago I attempted to reach out to [email protected] to report a serious cryptography security issue in this library and I have received no response. Please advise me of the correct contact point.
- Dominant language
- C
- Stars
- 122
- Forks
- 67
- Avg merge
- 6d 8h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from eclipse-tinydtls/tinydtls
-
ECDHE_ECDSA ClientKeyExchange rejected as too short when DTLS_PSK_MAX_CLIENT_IDENTITY_LEN > 64Possibly taken A pull request linked to this issue is open or already merged. Openbug good first issue please retest
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
eclipse-tinydtls/tinydtls#298 · 2 comments ·
Maintainers usually reply within 2 days
-
`dtls_get_cookie`: dereference before the length check (currently masked by `dtls_create_cookie`)Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
eclipse-tinydtls/tinydtls#279 · 2 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
MSVC build is broken (undeclared `DTLS_DEBUG_BUF_SIZE`)Possibly taken @mrdeep1 claimed this 12 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
eclipse-tinydtls/tinydtls#283 · 5 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 57/100
eclipse-tinydtls/tinydtls#278 · 3 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
eclipse-tinydtls/tinydtls#274 · 2 comments ·
Maintainers usually reply within 2 days
All issues in eclipse-tinydtls/tinydtls
Similar issues
-
[BUG] Small issues on iMXRT found by ClaudePossibly taken @Sarthak-Pandey claimed this today. OpenArch: arm Area: Networking OS: Linux Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
area: docs eco: cpp good first issue help wanted lane: free-agent roadmap size: XS type: docs
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
arminazimi/evergreen#475 ·
Maintainers usually reply within 1 day
-
[Issue]: hipsparselt.h C API as shipped now requires C23 -- ONLY because of missing include or guardOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ROCm/rocm-libraries#13736 ·
Maintainers usually reply within 2 days
-
libc
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
llvm/llvm-project#232380 · 1 comment ·
Maintainers usually reply within 1 day
-
level/task module/auth/enrollment platform/linux reporter/qa type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day