wlan: make hardware keys take peer into account
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- networking, operating-systems
Research direction
Start with the related TODO at kernel-src/io/net/wlan.c:23 to see how WLAN hardware keys are currently handled. The issue says the change also needs handling in the other Wi-Fi repositories, but does not name them; identify those repositories and compare their implementations. Done means hardware keys account for the peer across the relevant repositories.
Written by the indexing model from the issue text.
Description
note: needs handling in the other wifi repositories
- Dominant language
- C
- Stars
- 629
- Forks
- 36
- Avg merge
- 1d 23m
- Merged PRs (30d)
- 8
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 Mathewnd/Astral
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
iovec: add size overflow checkPossibly taken @ian0318git claimed this today. Openenhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Mathewnd/Astral#109 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 3/5 1-2 days Newbie friendliness 57/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
FujiNetWIFI/fujinet-lib#204 ·
Maintainers usually reply within 1 day
-
os:linux
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mpv-player/mpv#18649 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
facebookincubator/muse-gadget-sdk#249 ·
Maintainers usually reply within 1 day
-
docs: nng_dial / nng_dialer_start can return NNG_ECONNSHUT and NNG_ECRYPTO, which are not documentedOpen
Difficulty 1/5 1-3 hours Newbie friendliness 89/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
micropython/micropython#19786 ·
Maintainers usually reply within 1 day