[GH-ISSUE #609] File openssl_tests.rs has executable permission #247

Closed
opened 2026-03-07 23:00:28 +03:00 by kerem · 1 comment
Owner

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.rs has 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.rs in 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:

  • OS: Debian Buster
  • Architecture: x86_64
  • Version trust-dns-openssl 0.4.0
  • rustc version: 1.30

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.

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.rs` has 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.rs` in 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:** - OS: Debian Buster - Architecture: x86_64 - Version trust-dns-openssl 0.4.0 - rustc version: 1.30 **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.
kerem 2026-03-07 23:00:28 +03:00
Author
Owner

@bluejekyll commented on GitHub (Nov 9, 2018):

That's strange, don't know how that would have been set, even accidentally.

<!-- gh-comment-id:437439455 --> @bluejekyll commented on GitHub (Nov 9, 2018): That's strange, don't know how that would have been set, even accidentally.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#247
No description provided.