mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 19:25:56 +03:00
[GH-ISSUE #609] File openssl_tests.rs has executable permission #247
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#247
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @silwol on GitHub (Nov 9, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/609
Describe the bug
The file
crates/openssl/tests/openssl_tests.rshas executable permission. This is a potential security problem if it gets included into distribution packages. I found the problem because the Debian lintian tool warns about it.To Reproduce
Steps to reproduce the behavior:
Run
ls -l crates/openssl/tests/openssl_tests.rsin the project root, you'll see the -rwxr-xr-x permissions.Expected behavior
Source files should not have executable permissions, they can't be run directly anyway.
System:
Additional context:
I assume it's not possible to update the distributed crate, but it helps to have the permission fixed on the next release.
@bluejekyll commented on GitHub (Nov 9, 2018):
That's strange, don't know how that would have been set, even accidentally.
unused_mutwarnings in resolver examples. #1321