Build failure in iperf 3.22: undefined `errreturn` label in `decrypt_rsa_message()` if using openssl < 3
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- c
- Domain
- build-system, networking
Research direction
Start in iperf_auth.c at decrypt_rsa_message() and inspect the conditional compilation around the errreturn label and goto. Reproduce the build with an OpenSSL version below 3, then check the build with OpenSSL 3 as well. Done means both builds compile without the undefined-label error.
Written by the indexing model from the issue text.
Description
if using legacy openssl version, iperf 3.22 fails to compile with the following error:
iperf_auth.c: In function 'decrypt_rsa_message': iperf_auth.c:343:9: error: label 'errreturn' used but not defined
The goto errreturn statement is outside the conditional compilation block, while the corresponding errreturn: label is only defined under:
#if OPENSSL_VERSION_MAJOR >= 3
- Dominant language
- C
- Stars
- 8.9k
- Forks
- 1.5k
- Avg merge
- 5d 11h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 esnet/iperf
-
Cannot use more than 128 parallel streamsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
esnet/iperf#2079 · 3 comments ·
Maintainers usually reply within 2 days
-
Build failure on platforms without `<stdatomic.h>` due to use of non-standard `u_int64_t`Possibly taken @lgoettgens claimed this 114 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
esnet/iperf#2060 · 1 comment ·
Maintainers usually reply within 2 days
-
JSON output (-J) emits two top-level "error" keys on server-relayed errorsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
esnet/iperf#2051 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
esnet/iperf#2086 · 10 comments ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
esnet/iperf#2076 · 4 comments ·
Maintainers usually reply within 2 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
containers/bubblewrap#826 ·
Maintainers usually reply within 1 day
-
[compiler-rt] Rtsan-aarch64-NoInstTest: error: no such file or directory: 'NOTFOUND' (libatomic)Openbuild-problem compiler-rt:rtsan platform:linux
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
llvm/llvm-project#239039 ·
Maintainers usually reply within 1 day
-
component:obi contribfest go test
Difficulty 2/5 Under an hour Newbie friendliness 83/100
open-telemetry/opentelemetry-ebpf-instrumentation#4143 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
checkpoint-restore/criu#3304 ·
Maintainers usually reply within 1 day
-
Separate Installation Commands into Individual Code BlocksPossibly taken @andrySD claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
colbymchenry/codegraph#3241 ·
Maintainers usually reply within 1 day